3 ms·
After hard-avoiding social networks, I spent some time thinking about this problem when I wanted to share pictures of my kids. One of my requirements was priva
by mawise 4y ago
After hard-avoiding social networks, I spent some time thinking about this problem when I wanted to share pictures of my kids. One of my requirements was privacy, another was _not inventing a protocol_. I landed on RSS and built Haven[1], but I made the rookie mistake of putting my principles above usability. I want it to be hard-decentralized so everyone runs their own server--but nobody wants to run their own server.
I still have vision for what Haven could be, and supporting self-hosting remains important but I think I'll end up with something like the Matrix/Element model where there is a (free?) centralized server you can use, or you can host your own with full interoperability.
[1]: https://havenweb.org https://havenweb.org
- mjevans 4y agoAvoid building new protocols. However if it really can't even be shoehorned into an existing protocol, or if there are extremely clear problems (to the point that the existing closest option is even unsuitable as a compatibility / bootstrap interface); then go ahead and make a protocol that really covers the use case, if you can also make an open source (as in free beer) library anyone can use to talk with it.