The ability to easily do synchronization through a Nextcloud instance (or commercial cloud storage providers like OneDrive) is what’s keeping me on Joplin.
The ability to easily do synchronization through a Nextcloud instance (or commercial cloud storage providers like OneDrive) is what’s keeping me on Joplin.
You’re getting a lot of flack in these comments, but you are absolutely right. All the concerns people have raised about “AI” and the recent wave of machine learning tech are (mostly) valid, but that doesn’t mean AI isn’t incredibly effective in certain use cases. Rather than hating on the technology or ignoring it, the FOSS community should try to find ways of implementing AI that mitigate the problems, while continuing to educate users about the limitations of LLMs, etc.
Maybe I’m misunderstanding this, but their FAQ specifically says:
By default, your documents are stored inside the docker volume paperless_media. Docker manages this volume automatically for you.
It also says that documents are removed from the consumption directory, renamed, and put into a folder that you shouldn’t modify.
And that’s my problem with the project. I want to be able to keep my file name and organizational structure.
I experimented with self hosting RSSHub a while back and I do believe you could get past rate limiting on Instagram by configuring the app with your personal Instagram account credentials. I think those without an Instagram account were advised to follow pages via the Pikuki route instead.
Amaze File Manager can do this.
I’ve had no problems with the Discord flatpak and updates. I use a KDE variant of UBlue and the package manager prompts me to update all flatpaks when I start the computer (whenever there are updates available), which I do with one click.
For a new user, i would think that individually managing package updates is probably not a desired workflow.