markor VS Nextcloud

Emacs with Orgmode on the desktop. That's where most of my editing work happens. And for mobile the app Markor, synced via rsync in Termux with my desktop.

Additionally the app Joplin, which syncs via WebDAV to my server and is used by both me and my wife on both desktop and mobile to share notes, shopping list, web clips etc.

Joplin is excellent for sharing but its editing capabilities leave a bit to wish for. That's where Markor comes into play. Both support Markdown, so its easy to use both.

https://github.com/gsantner/markor

Just curious, any reason you're using TMarkor instead of Markor? (https://github.com/gsantner/markor/ , https://play.google.com/store/apps/details?id=net.gsantner.m...)

Only asking since this was also the editor I ended up settling on in Android, but it seems like TMarkor is just a repackaging of Markor without any references to its forked(?) source.

My requirement was that the repo had to be open source so that I could audit the repo and compile the APK from source, as well as potentially fork it for personal modifications if needed.

As other commenters posted, maintaining screenshots is a pain. Especially with software that's regularly changing.

That said, there are more than a few GitHub readmes that contain screens. Sometimes quite a few screens. Here's an example: https://github.com/gsantner/markor

The new Version 2.11 of [email protected] is now available on f-droid

Try Markor

Use Markor as my org-roam Set up my notes directory as my "home" directory, and set up some templates for creating new files, and set some timestamp formats to match org's. Also has a recursive text search that's good enough for my uses.

This is the Markor github repository with links to F-droid: https://github.com/gsantner/markor

There are web based VSCode you can run. Or if you push to Github that with give you a good read and a ok write experience. I treat mobile as a read only so I use Markor.

I already use Markor for some things on Android, so this might work really cleanly, unless I'm misunderstanding Foam's structure.

You can also use Syncthing with any kind of local files only editor to make them sync-able. For example with Markor

Nextcloud is a complete cloud service providing file shares, online office tools, messaging with visio-conference, and many others tools. It could be used as NAS as it provides a WebDav sharing service per user.

If complete self-hosting is a must, I now need some file server capable of generating shareable links, to be used in my Markdown image components. In summary, Syncthing is great for Dropbox-style backups, but can't share links, NextCloud is too resource-heavy and Seafile is interesting but apparently has proprietary encryption, which left me with the lightweight Filebrowser

In my opinion it’s not a good alternative if you or your team members expect exactly the same quality of service. When you switch to Nextcloud you’ll have to expect more bugs, less reliability, less performance and obviously more maintenance (since it's typically self-hosted) compared to Google Drive, Dropbox or One Drive. So you'll have to go into this with a different kind of mindset. What you gain is independence and extendability due to a rather big platform ecosystem.

E.g. here are some specific things and examples of things you'll have to deal with, in no specific order. These are just some things I've had to deal with recently.

- You'll have to educate people in your group that there are at least 3 different ways to share files among each other and that they can all coexist in parallel (Individual Shares vs. Group Shares vs. Group folders vs. Circles/Teams) (I did a german blog post on this: https://bitbetter.de/blog/nextcloud-freigabe-chaos/)

- Handling of file/folder names with special characters is a mess e.g. if you have Windows and Linux clients there will most certainly be conflicts. (Luckily this has been fixed recently by the `forbidden_filename_characters` config option – which is not enforced yet via the Web UI) see https://github.com/nextcloud/ios/issues/2802

- Creating Nextcloud users with spaces in their names, will break CalDAV on iOS Devices (https://github.com/nextcloud/server/issues/15641)

- Nextcloud (aka Collabora) Office is very slow if you want to actually work collaboratively with it (no matter the power of your Collabora server) – unfortunately it's no match for Google Docs or Office 365

See Configuration and syntax changes and Special packages. The latter this time includes changes around PostgreSQL, which should be upgraded to 16.1.

Nextcloud——File Sharing and Collaboration Platform

Website: Nextcloud