FediHood is a social network built around the place where you live. You choose a city and the topics you care about, then read what neighbours are saying and join in.
It stays a normal fediverse app. Your posts can reach Mastodon, PixelFed, Misskey and the rest, and posts from those servers reach you too.
Source code: https://git.holos.social/tom79/FediHood
There’s only one instance so far: https://fedihood.social/
If new instances are created, they should show up here: https://fedihood.fediverse.observer/list
This seems unreasonable to me:
I don’t think an encrypted message feature is necessary for this kind of a web app. If people want to send encrypted messages, they can just switch to a different service for that. Like you get them to know on fedihood, exchange matrix handles or phone numbers or whatever, and then you can use a different service for private communication.
Because AI Surveillance states are nothing for concern.
Less friction is better though. And not everyone knows where else to go for E2E.
The problem to me would be development burden, but its alreast implemented so…
E2EE is very hard to implement safely. serious cryptography is not a hobbyist project. just look at all the problems matrix has had with it.
Makes e2ee much easier that way.
I feel like it should still work if making a backup didn’t clear a browser, and restoring to a second browser should let both work.
key management is lot harder. signal does not support multi-clients for a reason, you can look at the history of matrix with encryption to find out what are the problem is. I’m not sure they even fixed or just know of all the failure modes of it.
Matrix is a good example I think: It allows a client to authorize another client so both work. It’s not the same ‘backup’ scenario, but proves the concept can work.
Is there an easy reference for the history there? I’ve used it over the years but not regularly enough to see it changing.