Comment on Introducing Habitat - A Social Platform for Local Communities
mnemonicmonkeys@sh.itjust.works 1 week agoReading through your link, it seems like the main difference in your framework is that there’s auto-propogation of federation built in. Please correct me if I missed anything
Unrelated point: before you throw too much time and effort into building up federation, I want to bring something in the Matrix vs. XMPP debate: caching.
Apparently in Matrix, if a user on server A joins a chatroom on server B, then all of the content on the chatroom need to then be copied and synced to server A. There’s 2 primary problems with this: it’s a lot of duplication overhead that can limit scaling of the network and there’s legal consequences for server A caching potentially illegal content. There’s also a privacy concern as this means more parties that can see various interactions.
XMPP gets around these problems by having the user on server A just directly connect with server B, without server A caching anything.
I haven’t dug into too many of the differences myself, but wanted to bring it up in case it helped
carlnewton@feddit.uk 1 week ago
Yes, this is a good point! I don’t necessarily want to slow one Habitat down when waiting for the response of another. It could lock up other requests. If it’s possible to send the user the url to retrieve posts with frontend javascript, that may definitely be worth looking into. It sounds like an XSS minefield though, but it could very well be the way to go.
Thanks for this.