rako

This is really nice, but I don’t understand what the willow part really brings, unfortunately

rsync and rclone are two different projects

The hosting part is, indeed, a technical part but a tool like copyparty can help here:

https://github.com/9001/copyparty/blob/hovudstraum/README.md#markdown-viewer

It runs everywhere, is just a single file you double-click to open and browse from your browser. Makdown files are automatically rendered. You can upload a bunch of files directly, or just send them by mail and put them in a directory served by copyparty

That’s basically what gopher is: a capsule of hierarchically ordered documents, easily browsable thanks to a normalized interface

https://en.wikipedia.org/wiki/Gopher_(protocol)

The web is one of its spiritual successor and is plenty usable to share text files. Most if not all software can generate indexes of content in a directory. wget and friends can be used to retrieve the whole archive. If you generate html files you can then style them independently of the content.

I would love to see an [AI] tag, so I can easily hide it. Coupled with temporary bans in case of missing disclosure it would really sanitize the community

Then failure to disclose can be condemned, for instance by temporary bans

And with garage hosted on multiple places you can even have an S3 endpoint, with redudancy, without the cloud !

https://garagehq.deuxfleurs.fr/

If not hosting anything is ok for you, deltachat allows you to share locations to people in a chat. It’s fully e2ee. You can use it with existing relays, but if you want you can host one that will be useful to everyone: https://chatmail.at/

Do people actually discover projects by randomly wandering on github though

I mean, it’s all links, a link to github or a link to codeberg won’t change much

it’s called capitalism

Be at peace with the mess. All the software you’re using have beend developed on their own, each has a different setup, maintenance work, they don’t fit with each other they just kinda not bother each other. Unless you’re using all the software included in a bsd or 9front base install, where everything is made to carefully fit, it’ll be crappy to look at.

Be at peace with the mess, which also means be at peace with burning some/all of it and starting fresh when something new comes up or you want to “simplify” a part.

The selfhosting, much like art, isn’t so much in the output: it’s in the process of trying, failing, succedding with a crappy solution, and then goind on with the learning. If you wanted a robust beautiful stack you’d be paying professionals to do that :)

what you want is Syncthing Lite: https://f-droid.org/packages/com.github.catfriend1.syncthinglite

You didn’t talk about self-hosting in your initial comment. S3 is not made for you, I guess it’ ok to just move on to the next article

S3 is made for scaling. At an individual scale it doesn’t matter. At scale, S3 moves maintenance time away from managing individual issues about something not working or slow here and there towards configuring and maintaining a consistent piece of architecture

No, it’s made for entities managing data for thousands/millions of people. “overengineering" implies a specific scope, it’s not the one you think about

S3 is not made for you. It’s made for entities that need to store millions of objects, with thousands of different rules, reading/writing from hundreds of machines without coordination, and with consistent, low latency. Now that some software use that as a storage layer, having an implementation for you is useful

if a craptp is useful it’s not crap anymore heh

I can only comment on tooling: fedify is very good, easy to get in and powerful enough for any usecase

https://fedify.dev/

ai;dr

ai;dr