I’ve always seen these self hosted S3 API compatible services as something a developer would use for testing.

Could maybe simplify the solution with https://syncthing.net/ or https://restic.net/ for self hosted backups.

Paperless will store documents in plain text. Maybe one could write a small webserver or extend Paperless to serve an RSS feed that could be consumed by Yacy.

My ranking attempt

“3: Only allow topics that arent limited to one language, library, etc. (general topic community)” “5: Only allow crossposts into the community with things like news being posted in the specific community first (crosspost community)” “4: Dont allow questions of how to do X in X language but allow actual discussions or news about the language in addition to general topics (general & discussion community)” “2: Allow any posts and direct people in the comments to more specific communities for their future posts (people catching community)” “1: Allow all posts relevant to the instance (main community)”

Basically desiring that posts be in their respective communities with the main community acting as a catch-all for posts that don’t fit into any existing community or announcements like community launches.

I know ranked voting is a good system, but the options are a bit confusing to me as they don’t seem mutually exclusive. Perhaps it is correct, but I have never seen a ranked vote like this. For example, I believe you could allow cross posting in addition to allowing topics that are not limited to one language.