this post was submitted on 11 Mar 2024
135 points (95.9% liked)

Technology

59589 readers
2891 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
135
submitted 8 months ago* (last edited 8 months ago) by starman@programming.dev to c/technology@lemmy.world
 

I personally wouldn't recommend obsidian (mentioned at the end of the article), but still, I think the article is worth reading.

top 25 comments
sorted by: hot top controversial new old
[–] brenticus@lemmy.world 17 points 8 months ago (2 children)

It's a good philosophy, to be sure. It doesn't take many migrations to realize that keeping your files in open, easy to read formats is preferable.

I also use obsidian, but I do sometimes worry that the linking and metadata will be difficult to work with in the future when the software goes away. It's all there in the files, but my vault is slowly linking together in interesting ways that rely on obsidian functionality.

[–] geophysicist@discuss.tchncs.de 7 points 8 months ago

Try logseq, it's a foss alternative to obsidian

[–] PersonalDevKit@aussie.zone 5 points 8 months ago (2 children)

I wonder this with obsidian also, it is one of the things that keeps me from diving in head first.

It seems a lot of its "powerful" functions are against it's plain text advantage. However I don't really see an easy way around it.

At least at the end of the day you or someone else could write a script to modify the plain text files for the next app.

[–] brenticus@lemmy.world 6 points 8 months ago (1 children)

It's tricky for sure. The plain text is great, and all the functionality is built off of plain text (even the canvas!), but replicating the functionality isn't trivial by any stretch of the imagination. Migration is easier because of the text files, but will it be as easy to see the links between notes? Or query all the notes I need more detail in? Or map it all out visually?

I think reimplementing the core obsidian functionality in a FOSS clone would be fun... except I already have a queue of projects and not a lot of time, so here I am complaining instead 🤷

[–] geophysicist@discuss.tchncs.de 1 points 8 months ago (1 children)

Logseq is the obsidian foss clone , worth a try

[–] brenticus@lemmy.world 1 points 8 months ago

Logseq is a great alternative. It's very much not a clone, though. It has a different paradigm on how it views notes and the functionality isn't exactly 1:1.

[–] geophysicist@discuss.tchncs.de 5 points 8 months ago (2 children)

Try logseq, it's foss and solves some of these problems. Mostly compatible with files from obsidian

[–] bionicjoey@lemmy.ca 4 points 8 months ago (2 children)

Does it have a plugin ecosystem like Obsidian?

[–] PersonalDevKit@aussie.zone 2 points 8 months ago (1 children)

That is the double edged sword though. Get cool features - lose true plain text

[–] bionicjoey@lemmy.ca 4 points 8 months ago

Who wouldn't want a double edged sword? Twice as good for chopping!

[–] geophysicist@discuss.tchncs.de 1 points 8 months ago

Yep it does

[–] PersonalDevKit@aussie.zone 1 points 8 months ago

I have heard that name a lot, I will have to give it a go

[–] 7heo@lemmy.ml 10 points 8 months ago

And they must be local rather than remote (cloud).

Also, always prioritise a common format served through filters (for example having all your data in postgres and minio, and serve that on demand as ICS, XML, etc) so that you don't need to duplicate or lose data due to formats.

[–] BearOfaTime@lemm.ee 5 points 8 months ago (3 children)

It's a great point to be making, though it seems to me part of the answer is to keep a copy of the software with the data files.

I keep a repository of software, relying on my brain to know which apps go with what archived data.

Think I need to revisit how I track things.

[–] admin@lemmy.my-box.dev 18 points 8 months ago (1 children)

keep a copy of the software with the data files.

That only works to a certain extent. Sooner or later you'll need to run a vm to run that software, so then you'll also need to keep isos for that operating system. The stack required to open that document will only keep growing.

Meanwhile, I'll guarantee you that you'll be able to open that markdown file that Obsidian generates with any text editor from 2124.

[–] BearOfaTime@lemm.ee 0 points 8 months ago

I kind of assumed all that with "keep the software", but you make excellent points.

Guess I need to re-re-think my setup. Like keep some VM's or containers already configured with the app, and an annual maintenance cycle (minimum) to verify it all works as expected.

Seems like this is really about backup or failover/DR management.

Sigh, yay, another thing to add to the list, haha.

[–] WolfLink@lemmy.ml 5 points 8 months ago

Software isn’t reliable because older software typically doesn’t run on newer machines. This is mostly due to changes in libraries that software relies on, but sometimes can also be do changes in the actual architecture of the CPU.

[–] conciselyverbose@sh.itjust.works 1 points 8 months ago* (last edited 8 months ago)

The philosophy of "you need to own your files" is great.

The extension to "you should be able to open it with a computer from the 60s" is insane. You don't need to give up efficiency and make everything plaintext. Just document shit.

[–] serpineslair@lemmy.world 4 points 8 months ago

Interesting, I must admit, I never thought of digital data like this. I suppose a lot of history from our current era is either online or in a digital format. That in turn makes data important to preserve, although that part was obvious.

[–] ___@lemm.ee 4 points 8 months ago (1 children)

Take it further. Convert all of your data into forward or simple formats. Don’t encode your images as gif, keep them raw. Store word docs as markdown. Don’t use proprietary formats (duh).

Linux will be around for a long time, which is convenient. Everything is a file, that counts, right?

Also be thankful for VMs and the push towards distroless containers.

[–] bionicjoey@lemmy.ca 14 points 8 months ago (1 children)

Don’t encode your images as gif, keep them raw.

This is fucking insane. There are plenty of open standards for image files.

[–] ___@lemm.ee 1 points 8 months ago

It was an example. Lossless formats exist.

[–] drawerair@lemmy.world 1 points 8 months ago

This reminds me of Blu-ray and streaming. Movie and series studios seem to prefer streaming over Blu-ray. If I'll stream a movie, I won't own it. On the other hand, if I'll buy a Blu-ray disc, I'll own it.

Lately I bought a Buffalo 1-terabyte external ssd. It'll be my backup ssd. The formats of my files are common so I don't have an issue opening those.

[–] TypicalHog@lemm.ee 1 points 8 months ago

I agree and resonate with this so much! I think everyone should have everything (or almost everything) in their vault as markdown files.

[–] bigkahuna1986@lemmy.ml 1 points 8 months ago

Why can't I highlight any text on that page?