sxan

I think there's such a knee-jerk reaction to any mention of crypto currency, even in comparison, that even a whiff of a relationship generates negative reactions. As you say, much of it is based on no actual knowledge about the topic. It doesn't help that there are some truly deplorable people associated with cryptocurrency, a great many bad actors, and proof-of-work was in retrospect a terrible design decision by Satoshi.

Blockchain isn't cryptocurrency, and vice-versa, but most people can't distinguish between the two. If there's any mention of blockchain on the site, or especially if you mention bitcoin (as you did) you're going to get crusaders.

Thank you, I'll check them out.

I never considered that Alaska might be less serviced than other states, given how removed it is. It's no Hawaii, but still.

My problem has always been finding a SIP company I wanted to give my money to, for providing a land line #. For a glorious, brief, period, I was able to do this through Google Voice. But then they got rid of that feature, and I haven't found another provider who I like the looks of.

LogSeq has other note types; it's just the default is bullets.

LogSeq is about as future proof as you can get. Notes are stored in a directory tree as markdown files.

Try it, it's good. There's a mobile app, for Android, at least. It's free; it only takes a little time investment, so low barrier for entry.

LogSeq is nice.

For this who don't know, it's well designed, in that it doesn't add bloat and obfuscation like a DB would; it keeps everything in a filesystem structure in markdown files. What's really nice is that this makes it something you can use with a plain editor, or with the application, or with the app on mobile; the app(s) add a lot of convenience functionality to the basic storage design.

It's a well-thought-out system, and I appreciate how clean it is, and how independent of the application the data is. I haven't looked at the code base, but I have a lot of respect for the developer must based on the design & architecture decisions.

I have a feeling you're looking for something different, but: mine is a big todo.txt document that I open with fzf. I just add lines to it and tack on @keywords.

If your needs are more hierarchical and structured, I'd still try to stick with a plain-text and fuzzy-search based solution, and split stuff up into different files.

IMHO, you're starting from a good place (plain text files). Maybe you just need a little tooling for searching and keyword filtering.

Fucking Deloitte!

Ah, so it has a "watch" mode? Cool.

Ditto.

I get angry with SyncThing; don't get me wrong. I really wish they'd add a per-file-type merge plugin capability, and I get far more sync conflicts than I care for. I get situations where a client on one computer stops (mostly, Android killing it) and it needs to be manually restarted.

What I've never had it data corruption. It's to the point where I implicitly trust that if SyncThing says it's synced, I know it's on the destination. It might be a stored as a sync conflict, but it's there.

How is rclone fire and forget? You have you manually run it every sync, right?