

what you want is Syncthing Lite: https://f-droid.org/packages/com.github.catfriend1.syncthinglite
Sur le microblogging: @[email protected]
Sur le web: https://www.rako.space/
Sur xmpp: [email protected]
Sur deltachat: https://i.delta.chat/#F2EACE10C8C69DE92EE5B72B308C75A6FA0B3479=&i=AXCOWs9ZS0ZlgudzJAm8ERqz&s=WZ2khNFSyDdAW-N3yjqQTnTK&a=phj2so4ey%40nine.testrun.org&n=Invite (si vous n’êtes pas du spam je vous ajouterai à mon vrai compte)


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


ai;dr


I don’t understand, how is yunohost not selfhosting ?
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 :)