rako

I think it’s a very good idea for reusing old, unused phones and make them useful again. No need to buy a phone for that.

This is the point where having a 24/7 up server is not the smartest thing to do and a device that is sometimes turned off is fine

Be aware that if you have a single machine syncthing won’t work.

Use any software that can do software merging, like meld, it does the job

If you’re not going to have many editors, don’t hesitate to look at https://feather.wiki/ . It’s a single-file wiki with everything embedded, so to modify it you actually do your changes then get the new index.html that you can push back to the hosting place. No server-side process, no scaling issues, SEO-friendly, portable, backupable, etc…

This means your pages would retain the classic wiki change log, so that it can all be generated from a Git repo that’s small enough to keep on a floppy disk.

That already exists: https://ikiwiki.info/ . It is by default a bit more raw than dokuwiki but does the same thing in the end.

fossil is made by actual engineers, maybe we should follow that path

When capitalism can’t find a new way to grow and is challenged by dominees, it funds fascism as an investment towards to guarantee their dominance

I have a vps I use for other stuff, and put syncthing on it. My files are replicated between it, my computer and my phone. On the vps I activated the setting to store old versions

For photos I use hetzner’s storage share, a nextcloud offering. Photos are browsable with nextcloud’s “memories” app, really useful.

I don’t really believe in “backups”, ie a full copy of the content in another format that is unusable unless you run it through a special restoring process. If the files are being copied, why not make it useful ? Syncthing makes it so all environments are equally usable, and the versioning prevents mistakes. There is no restore phase: the files are already usable.

I really think we need to move our thinking away from the one-machine-with-copies mindset, and architecture our usages around multiple-machines-by-default. If the goal of backups is resiliency, a syncthing clusters achieves that.

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