friendica (DFRN) - Link zum Originalbeitrag
Asking the hive mind: What do we know or recommend about using tools such as #logseq or #obsidian all along with #NextCloud or #Koofr? I'd basically like to sync notes between Android and Linux desktop and have read mixed statements on that.
Boosts welcome.
#Followerpower
#obsidian #Followerpower #nextcloud #logseq #Koofr
Als Antwort auf Kristian 🌒

mastodon - Link zum Originalbeitrag

Dźwiedziu

As you've mentioned Nextcloud there's always WebDAV.

github.com/stefandanzl/webdav

Personally I use Syncthing, but you may run into issues, as Android FS supports less characters than a modern ext.

GitHub - stefandanzl/webdav: Obsidian Plugin to sync files to self hosted Webdav Server based on checksum comparison.

Obsidian Plugin to sync files to self hosted Webdav Server based on checksum comparison. - stefandanzl/webdav
GitHub
Als Antwort auf Kristian 🌒

mastodon - Link zum Originalbeitrag

Dźwiedziu

For Android you can try the Syncthing Fork, as it has more options. I'm driving it daily with minor issues only (ST has it's limitations).

f-droid.org/packages/com.githu…

Syncthing-Fork | F-Droid - Free and Open Source Android App Repository

Wrapper for Syncthing - Open and decentralized file synchronization
f-droid.org
Als Antwort auf Jens

mastodon - Link zum Originalbeitrag

SilverBullet

@thenorthcore a current solution that's worth considering if you don't want to self host is using @Pikapods: pikapods.com/pods?run=silverbu…

PikaPods - Instant Open Source App Hosting

Run the finest Open Source web apps from $1.20/month, fully managed, no tracking, no ads, full privacy. Self-hosting was never this convenient.
www.pikapods.com
@Jens @Pikapods
Als Antwort auf Kristian 🌒

mastodon - Link zum Originalbeitrag

SilverBullet

@thenorthcore @Pikapods E2EE is on the roadmap. Currently you can opt in to encrypt synced data on the client, but the server side is up to you (in principle it's just regular, unencrypted files on disk, although that disk can be an encrypted disk, of course). For self hosting this probably fine (and useful, because it also allows you to use non-SB tools to manipulate your data), but for shared hosting environment it's probably not ideal.
@Jens @Pikapods
Als Antwort auf Nik | Klampfradler 🎸🚲

friendica (DFRN) - Link zum Originalbeitrag

Kristian 🌒

@Nik | Klampfradler 🎸🚲 Guess it depends. I'm doing hosting for HA customer systems 24x7 which consumes enough time to not want to have to do the same thing for my own stable tools too so I'm easy with paying someone to do that right (specifically given self-hosting doesn't make much sense if I "just" use some VPS or rented server but don't control the hardware underneath which I do not want to do at all for tools I personally rely upon), and using E2EE with keys stored anywhere but on their servers would be mandatory for this kind of data in any way. Having Hetzner Storage Boxes on my list to check too, but that's NextCloud again.
@Nik | Klampfradler 🎸🚲
Als Antwort auf Kristian 🌒

mastodon - Link zum Originalbeitrag

Nik | Klampfradler 🎸🚲

Self-hosting is not about doing it all yourself. It is about the freedom of choice (you can pay **someone** to do it for you, but it is up to you who this "someone" is). If Koofr goes rogue or bankrupt, you are not able to pull your Koofr off and pay someone else to continue hosting it. That's the core point about self-hostable tools.
Als Antwort auf Nik | Klampfradler 🎸🚲

friendica (DFRN) - Link zum Originalbeitrag

Kristian 🌒

@Nik | Klampfradler 🎸🚲 I know. That's why I am resorting to standardized means of data access (such as WebDAV or rclone or whatever comes to mind) and always will keep my data fully safe offline as well. I wouldn't go anywhere near Koofr or something like this if they required proprietary tools or interfaces to access data stored in there. As soon as I could easily take data off there and move them over to, say, NextCloud or something else that uses the same protocol, I'm fine with that; from that angle I don't see the software itself being self-hostable /that/ hard a requirement. 🙂
@Nik | Klampfradler 🎸🚲
Als Antwort auf Kristian 🌒

mastodon - Link zum Originalbeitrag

Rob Williamson

I'm having a good time with Obsidian + Koofr + FolderSync for Android synchronization. It's a little fiddly to set up because Koofr wants you to generate individual app credentials rather than give your user credentials to client apps.

That's probably sensible from an access control perspective, but might make a few users do a double take.

If you don't tell FolderSync to watch for changes, you may find you have sync problems, which is annoying. I tend to manually sync before editing.

⇧