Digital Gardening in Obsidian • Hacker News Board

Re: Digital Gardening in Obsidian

#51

Post by mpalmer » Tue, Dec 27, 2022, 3:29 PM UTC

dunham wrote: post #37

mpalmer wrote: post #34

Earlier quoted context omitted.

Obsidian has been around for years at this point. It's completely free to use without limitations on functionality. They make money by charging for sync, but are happy to point out that there are free options to sync data. So where are these anti-user features? Why does the business model lead to them? "Not open source" doesn't count.

I have no idea what features are "anti-user", but I would note that it is not free for commercial use. I'm paying for Obsidian sync and still can't use Obsidian for work. (At the moment, I'm using logseq there.) https://obsidian.md/eula

I'm not sure I'd agree that pricing is ipso facto anti-user, but I grant that it's a limitation that can be out of the end user's direct control.

Re: Digital Gardening in Obsidian

#52

Post by wrikl » Wed, Dec 28, 2022, 7:20 PM UTC

number6 wrote: post #2

My problem with obsidian is that I need a license to use it if I add something work related. I can not realy disentangle both. If Ilearn something new here on HN Iwm will propably use it later at work.

Same here, and honestly I suspect a lot of people probably don't know this and use Obsidian for work or include work-related notes in their free plan without realizing that it technically violates the license.

Re: Digital Gardening in Obsidian

#53

Post by nivertech » Mon, Jan 02, 2023, 5:41 AM UTC

rcarr wrote: post #17

whichdan wrote: post #5

Tiny suggestion - instead of .map(g => { return { key: g.key, rows: g.rows.map(r => r[1]) }}) you can write .map(g => ({ key: g.key, rows: g.rows.map(r => r[1]) }))

You could also destructure g to end up with: .map(({ key, rows }) => ({ key, rows: rows.map(r => r[1]) }))

also:

  .map(({ key, rows }) => ({ key, rows: rows.map(([page, link]) => link) }))

and

  .groupBy(p => p[0])

to

  .groupBy(([link, file]) => link)