md.obsidian.Obsidian VS go-appimage

My Flatpak version was updated the same day. Very impressive.

I tried flatpak command line instructions as mentioned here but that too giving error

There are Linux solutions to this, macOS makes apps request permissions to important folders/ full disk access, any operating system should let you run something as a locked-down user without read/write access to your important files, etc. Installing Obsidian on Linux using flatpak or recent macOS + a firewall would let you manage a lot of the risks there, for example.

If you want simple markdown notes I recommend Paper, for to-do lists a good option is Endeavour, and there is third option, Obsidian, I don't use it because it feels complex, but maybe you will like it

Is that not this? https://flathub.org/apps/details/md.obsidian.Obsidian

It's probably best to open an issue here to ask what's going on if you're interested: https://github.com/flathub/md.obsidian.Obsidian/issues

You can check in github repo how a flatpak package is done. Here is how Obsidian is done. If you don't like any permission, you change it through flatseal app or command line. Most gnome apps and apps that follows gnome HIG are maintained by the official developers themselves. Valve, Mozilla are maintaining their respective products.

Snap and flatpak run a daemon to integrate into your system. Appimage has an optional daemon to give you the same integration https://github.com/probonopd/go-appimage

Handles making it executable, automatic upgrades, no need to move it to your $PATH, and adds the application to your app list.

Only other thing you might want to do is symlink a friendly name for cli

It's possible to make appimages that bundle a libc, although most don't. The go-appimage project contains a static build tool that will bundle the linker and wrap executable invocation in that. The intention seems to be providing support on older systems for programs built with a glibc that is too new, but I'm using it to ship a musl binary that can run on glibc systems.

I look forward to watching the FOSDEM talk this weekend, so perhaps getting ahead of myself. But I'm curious whether you think the move in appimage toward static linking would solve some of the hairy issues you pointed out? For example: https://github.com/AppImage/AppImageKit/issues/1193 and https://github.com/probonopd/go-appimage/

AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy

There's an automatic way to make .desktop entries from appimage, I use https://github.com/probonopd/go-appimage/blob/master/src/appimaged/README.md

There are helper programs to help you manage them and integrate them with the system like other package formats.

their is you can use appimaged https://github.com/probonopd/go-appimage

Would be great if most distros (including Ubuntu, Fedora, etc.) would include AppImageLauncher or appimaged by default. Would make it much simpler for most people.