Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from DokuWiki to Obsidian

kaeruct.github.io

Post reply on HN
Print view View original

61–70 of 81 posts

Re: Migrating from DokuWiki to Obsidian

#61

Post by zappchance »

itsjustjoe wrote: post #55
apitman wrote: post #31

Obsidian's business model might be genius. Open file formats; closed source. By making a great product, they attract users. Usually the main argument against software like this is vendor lock-in. But by using open formats, there's always an escape hatch. If they decided to squeeze their users, I suspect a decent open source alternative would pop up very quickly. In the meantime, casual open source alternatives are ve…

The third party plugin community is fantastic as well, I use it for GMing TTRPG sessions and I have a pretty powerful workflow built out.

Care to share which plugins you use? I'm interested in GMing some lesser known RPGs.

Re: Migrating from DokuWiki to Obsidian

#62

Post by CWuestefeld »

Multicomp wrote: post #2

Nice! I've been resisting Obsidian because I prefer the multimedia capabilities of OneNote, but since I have an old dokuwiki install that has floated around for a long time, I may just use this to finally kick the obsidian tires.

I've been a OneNote user for years, but a few months ago MS sabotaged the clipper extension for Firefox - and for no apparent reason except, apparently, to force people toward Edge.

If they're going to maliciously break my workflow, then who needs 'em?

So I've switched to Obsidian, although I'm finding it a little clunky and I've also been playing Zoot.

Re: Migrating from DokuWiki to Obsidian

#63

Post by tannhaeuser »

entrepy123 wrote: post #54

It's possible to basically avoid the second step ("Convert all text files from DokuWiki Syntax to proper Markdown") by only ever writing Markdown in Dokuwiki to begin with. To write Markdown in DokuWiki, the "DokuWiki Commonmark Plugin" [0] is pretty great. To use it, tips are: - REQUIRED: On the top line of each page, put ` ` (using the new toolbar button or typing it in). So that Dokuwiki knows the page is in markd…

Interesting, didn't know about . Though as an SGML pedant, I have to say using this doctype declaration in this way just tells an SGML or XML parser about the base ("root") element and is thus simply incorrect since there is no "markdown" element. The proper way would be to use just "html", and adding SGML shortref declarations in the "internal subset" for markdown-to-HTML mapping, like sgmljs is doing.

Re: Migrating from DokuWiki to Obsidian

#64

Post by throwbmw »

itsjustjoe wrote: post #55
apitman wrote: post #31

Obsidian's business model might be genius. Open file formats; closed source. By making a great product, they attract users. Usually the main argument against software like this is vendor lock-in. But by using open formats, there's always an escape hatch. If they decided to squeeze their users, I suspect a decent open source alternative would pop up very quickly. In the meantime, casual open source alternatives are ve…

The third party plugin community is fantastic as well, I use it for GMing TTRPG sessions and I have a pretty powerful workflow built out.

Please write a blog about it

Re: Migrating from DokuWiki to Obsidian

#65

Post by suprjami »

nfriedly wrote: post #21

I haven't tried Obsidian, but I'm pretty happy with NextCloud Notes which saves all my notes as either plain text or markdown and keeps them in sync across my phone, and various computers.

I recently spun up a self-hosted Nextcloud and was pleased to see my existing directory of Markdown notes just worked.

Re: Migrating from DokuWiki to Obsidian

#66

Post by chrisweekly »

slightwinder wrote: post #60
chrisweekly wrote: post #58

Earlier quoted context omitted.

> Development is already slowing down and focusing on fixing bugs Yes - because it's stable and powerful. So grateful they care about quality and are not becoming bloatware / chasing random features. As for the plugin ecosystem, it was always inevitable that a significant portion of them wouldn't be well-maintained and wld become obsolete. As an Obsidian early adopter and heavy daily user, I have only good things to…

> Yes - because it's stable and powerful. So grateful they care about quality and are not becoming bloatware / chasing random features. Yes, but this is only good for the satisfied users. Users who wait for certain "promised" features, might slowly become unhappy over time. Other will simply not find what they need. I guess a bit of the problem is that Obsidian exploded in interests far beyond what the devs imaged, a…

There's a bright-line distinction between core plugins (official) and community plugins. It's not the core team's responsibility to determine whether someone might be getting value out of a community plugin. TBH it seems like you're trying to find things to complain about, but have yet to raise anything substantive.

Re: Migrating from DokuWiki to Obsidian

#67

Post by egberts1 »

richardwhiuk wrote: post #49
egberts1 wrote: post #45

Earlier quoted context omitted.

Now why would someone blindly download an executable from a security and privacy point of view?

Curious how you installed Linux.

Linux from Scratch.

None of that systemd and its PID 1 doing network socket opened.

Re: Migrating from DokuWiki to Obsidian

#68

Post by abhinavk »

itsjustjoe wrote: post #55
apitman wrote: post #31

Obsidian's business model might be genius. Open file formats; closed source. By making a great product, they attract users. Usually the main argument against software like this is vendor lock-in. But by using open formats, there's always an escape hatch. If they decided to squeeze their users, I suspect a decent open source alternative would pop up very quickly. In the meantime, casual open source alternatives are ve…

The third party plugin community is fantastic as well, I use it for GMing TTRPG sessions and I have a pretty powerful workflow built out.

I only wish they be sandboxed or audited before release. It would be perfect.

Re: Migrating from DokuWiki to Obsidian

#69

Post by yibbix »

I use obsidian daily and while I love it, I do feel it’s got lots of flaws. Mostly I feel the development team is pretty opinionated with some of its choices, especially regarding its tab management. I find myself annoyed by a lot of the basic functionality and am constantly having to add custom css or plugins. I’m grateful that the plugin community is pretty large, but it sucks needing so many plugins just to make the program useable in the way I want to use it, rather than obsidian having more options and toggles built in.

Re: Migrating from DokuWiki to Obsidian

#70

Post by slightwinder »

chrisweekly wrote: post #66
slightwinder wrote: post #60

Earlier quoted context omitted.

> Yes - because it's stable and powerful. So grateful they care about quality and are not becoming bloatware / chasing random features. Yes, but this is only good for the satisfied users. Users who wait for certain "promised" features, might slowly become unhappy over time. Other will simply not find what they need. I guess a bit of the problem is that Obsidian exploded in interests far beyond what the devs imaged, a…

There's a bright-line distinction between core plugins (official) and community plugins. It's not the core team's responsibility to determine whether someone might be getting value out of a community plugin. TBH it seems like you're trying to find things to complain about, but have yet to raise anything substantive.

Community-Plugins are also offered and managed through the app itself, so they do have some sort of responsibility for what they make available.
Post reply on HN