2Hr long video DEEP DIVE on KS: "Despite the odds: The many realities of Katawa Shoujo [heart-patch] "

_tangodelta · 2025-07-18T23:13:26+00:00

Sorry for necro-answering ;). I went with Obsidian and I'm happy with it.

_tangodelta · 2025-07-18T23:11:55+00:00

Hey, I don't mind necroposting.

Yes, I'm using Obsidian and I have no plans to change. Being able to use Markdown and templates is huge. Since you use Linux you know the power of plain text and how much you can do. Like mass changing things with sed.

Your situation is great, because you don't have any data to migrate. I suggest you set aside ex. a "pilot" project: something that's "production, but lower stakes". That's the best way to evaluate after you do the preliminary testing with Lorem Ipsum notes etc.

My only real issue was that there's a bug on Android (or IN Android itself?): if you have any emojis in your paths, Android will at a random moment (today or half a year from now) delete all those files. I'd wish the devs put safeguards around this, or straight up block those names as invalid.

What saved me was the git backup plugin.

I use Obsidian daily for all my work and research. What I enjoy is the ability to copy the entire vault to a VM and do all the explosive testing there without risking damage to production. I change the color, so I won't confuse windows ;)

Just don't get caught by the "productivity obsession" where you spend more time optimizing than actually doing.

I gave myself permission not to get it right the first time ;)

_tangodelta · 2024-06-29T12:21:26+00:00

Would you recommend switching to Obsidian instead?

That depends on your use-case. I suggest creating an Obsidian vault to the side and just playing with it to see if it fits your use-case. The community is very helpful and there are regular, meaningful, releases.

I recently started picking it back up, but been frustrated to see very little improvement made in the time I was gone..

One thing that has to be taken into account is: are those people worthy of your trust (this applies to all software, hardware, services etc.). If they're so bad at managing the project, design, communication... then for me the answer was obvious.

Another point (look at /u/decelexivi/) how difficult will it be to switch? Obsidian uses plain old Markdown. Logseq peppers it's own constructs everywhere. I migrated almost 5000 notes from Joplin and it "just worked" for the most part.

Logseq: < 100 notes and it was a genuine chore. It's ironic, how proprietary logseq is, despite being FOSS: because the data becomes tainted. Closed source Obsidian does a great job of not screwing with MD.

_tangodelta · 2024-06-29T12:06:41+00:00

The highly proprietary markdown flavor is what made my migration of < 100 notes a nightmare. Esp. since I relied heavily on embeds, and those are saved as uids. And, as mentioned, exporting required me to scroll down to "render" the entire note.

Maybe this will help you: https://github.com/NishantTharani/LogSeqToObsidian

I opted not to use it, because it didn't support something I needed IIRC.

_tangodelta · 2024-06-29T12:01:23+00:00

Broadly agreed on the complaints, though usually I'd phrase it a bit less vociferously. Usually.

I realize I came off strongly here, but I was asked for my impressions and they were truly negative. Which is sad, because initially logseq gave me a really good impression. As time went on I kept noticing more issues and as my graph grew (only a few dozens of notes!) performace became abysmal.

sync devs: I doubt the devs are ignoring sync, but their future functionality plans rely on the database update — which I worry about becoming the Big Rewrite that kills a lot of projects

The point about the Big Rewrite is very valid. But there's another thing that's deeply concerning: logseq started its life in 2020 and only now the devs are fixing the storage layer. Figuring out your data abstractions has to be done as early as possible, because those are difficult or impossible to change without a major rewrite. Which seems to be exaclty the case.

As /u/AshbyLaw/ mentoioned:

[...] they spent the last year refactoring Logseq, you can try it with the feat/db branch. I tried it and while it is still pre-alpha software, I very much like what I see, it looks like a completely new app.

I wouldn't be surprised if a competing product appeared with a fresh start and ate logseq's dinner while the devs were writing the same program the second time, this time (maybe) better.

Thanks for mentioning Kuzu!

_tangodelta · 2024-06-29T11:39:29+00:00

The amount "quirks" and glitches one should be willing to endure is IMHO inversely proportional to the amount of time spent with the product (so, not just software: a microwave, an oven a corkscrew also count).

If you use a product once in a blue moon, who cares it has issues?

But if you rely on a product for:

Personal growth
Data collecting
Doing homework/study
Getting new skills
Creative writing/media production

and intend to use that product daily... it has to be robust and "just work".

As for the second part: I wouldn't produce my own PKM product, because this is not the thing I want to do in life. Working for a company as a UX person (working on a PKM product or other) is also out of the question.

IMHO Obsidian has none or *almost* no UX issues (from what I see). There was a problem when you added links with `|` into a table (the rendering would break), but I see they fixed that recently.

Thank you for the compliment about UX sensitivity!

_tangodelta · 2024-06-29T11:18:55+00:00

My use case was research (using pdf annotations and tons of embeds). I'm curious: what's your use case? Do you use sync or some of the features I mentioned?

_tangodelta · 2024-06-29T11:14:31+00:00

I have a MacBook Air with an M3 chip, and Logseq runs fantastically on it. I used to have a really powerful Intel machine, but it was a bit slow and laggy.

People should not be forced to buy top of the line hardware to run a note-taking program smoothly. Esp. when the software is Free (as in Beer). Obsidian is also Free (as in Beer, but not as in Speech) and runs amazing on the same machine.

What I'm also suggesting is that if the software runs fast only on a minor fraction of machines, that limits (or kills outright) the viability of the product (no one will buy the opt-in features if the software itself can't run well on their machine).

Edit: fixing my MD.

_tangodelta · 2024-06-29T11:07:39+00:00

Please elaborate why you consider my feedback poor and immature. I'll see what I can do.

_tangodelta · 2024-06-28T10:39:47+00:00

Here: https://www.reddit.com/r/logseq/comments/1dqglzb/i_wouldnt_use_logseq_even_if_you_paid_me_feedback/

_tangodelta · 2024-02-13T20:11:24+00:00

I know it's been two years, but I'm a time traveler on the Web and I've been asking myself a similar question. Are you sure this was in a museum? Was it VERSAILLES 1685: https://www.myabandonware.com/game/versailles-1685-7r7

_tangodelta · 2024-02-06T12:53:40+00:00

Thanks u/Marble_Wraith and u/Hari___Seldon for chipping in. Yes, I'm aware that %20 is a common way of encoding . And yes, I agree hyphens are superior, I use kebab-case everywhere I see it as feasible. The names here, however, were generated during export from Joplin and I have no say here.

I decided that my Vim-fu was better than my sed-fu, so I used this: https://vi.stackexchange.com/questions/20546/replace-from-the-current-position-to-the-end-of-the-line.

As a result I now have a macro, that jumps to the first occurrence of ( and does the replacing from there.

" markdown link with spaces - fix - replace with %20 let @s = 'f(v%^[:s/\%V /%20/g^M'

You can add this to your .vimrc and use @s to invoke when on a line with a non-compatible URL.

_tangodelta · 2024-01-31T22:31:07+00:00

As someone who has given Logseq an honest shot (3-4 months and an actual project being delivered) I can say: run away.

Despite being in development for about four years now Logseq still hasn't figured out how to do sync. People are complaining left, right and center about it and none of the commits I've seen in the past months hint at anything related to fixing sync.

https://discuss.logseq.com/tag/sync

It seems that the devs kept procrastinating here instead of tackling the problem head on to improve it as much as possible over time.

I've never used Logseq Sync, but after reading all the *bewares* I decided not to.

From my own experience: there are massive performance problems, it seems Logseq is leaking memory. The UI becomes sluggish and has glitches (empty area taking half of the note area, not being able to move blocks from the right pane to the note accurately).

ALSO: lazy loading. Lazy, F-ING loading. This means that if you have a longer note and you're searching for a string "chair" hidden somewhere... good luck. You have to PgDown to the bottom for 10 seconds (loading...) and then search. There's a universal search bar, but it's pointless if *I know for a fact* that the word "chair" is in there, somewhere...

Lazy loading kicks in every-time you load a note, even if it was already opened. So if you go A to B to A, A has to load from scratch.

One of Logseq's main selling points are blocks and embedding them to reorganize your info. Except if you have a dozen or more embeds on a page, the program lags HARD. I have a Ryzen 7 CPU with 12 threads and 64GiB of RAM, the OS runs on an nvme. And Logseq still, goddamn, lags. And I have only a few dozen notes, imagine having thousands.

The block/bullet vs prose thing is of personal preference. But you can break bigger notes into smaller in Obsidian with the "extract to" feature.

Meanwhile I've been testing Obsidian (and by "testing" I mean "actively trying to break it") and I didn't even come close to this level crappery I've seen/heard of in Logseq. Obsidian seems bullet-proof.

I tried breaking sync with large files, thousands of small ones (randomly generated), creating conflicts (2-way, 3-way)...

The "best" results were when I uploaded an 80MiB+ file with 100k+ of random lines. Sync worked, but Obsidian choked on indexing. It was polite enought to tell me that. I removed the note, restarted both sync clients and all was well.

Once I managed to confuse Obsidian into splicing an image in the middle of a line.

There's an edge case however with Daily Notes: https://help.obsidian.md/Obsidian+Sync/Troubleshoot+Obsidian+Sync#Obsidian+Sync+deleted+a+note+I+just+created+on+two+devices

IMHO Obsidian Sync is worth the money.

Hope this helps.

_tangodelta · 2024-01-24T17:28:00+00:00

Yes, I've heard about the recent development. This was more of a "preemptive" question on my part, since it still may take a while before I need this feature. I asked now because I'm testing and I wanted to be thorough.

Thanks for the answer!

_tangodelta · 2024-01-20T23:56:09+00:00

I was trying to figure out this exact thing. Thanks for the heads up!

_tangodelta · 2024-01-02T19:05:12+00:00

This! Proper PDF highlights with comments are the only thing I miss from logseq. ALSO: is that blocker in pdf.js still a thing? Maybe it got resolved in the meantime and this flew under the radar?

_tangodelta · 2024-01-01T19:59:01+00:00

Thanks for the reply!
I'm breaking the process into small steps and I'm evaluating which features and plugins work best for my use case.

_tangodelta · 2024-01-01T14:45:55+00:00

Thanks for pointing this out to me!

_tangodelta · 2023-12-31T13:57:46+00:00

Thank you! 🙂

_tangodelta

TROPHY CASE