@datacop @cypherhippie following up on the off-topic discussion on Jitsi regarding overlap between @battlemesh and #Fediverse ( #Fedicamp?): I'd be super interested to get a better insight into what resources a Mastodon instance needs + how its data flow looks like. How much data is sent synchronously / simultaneously / redundantly to multiple receivers, how much is sent on-demand? Could smarter routers lead to less resource requirements for an instance/server? Could (long-term) #multicast help?
Discussion
Loading...
@datacop @cypherhippie @battlemesh also I guess text messages alone don't need much resources? But what about media? As a user I've had the experience that seemingly from small instances videos would sometimes need a long time to buffer. Is that a pot. issue with the current Mastodon implementation + federalization?
Far in the future, would it make sense if a toot or boost (w. media) would use multicast (maybe via https://datatracker.ietf.org/doc/draft-jholland-quic-multicast/) if the network is capable of it?
@datacop @cypherhippie @battlemesh or is Mastodon / the #fediverse maybe already using some #Bittorent like, peer to peer based approach to distribute media and to distribute network load?
I would really love to understand the technical aspects of the Fediverse better, to know how/if we could somehow support this (and other/similar) model(s) from the OSI layers below it in some ways.
I’m excited that there is someone interested in this overlap 🤗
I can see myself organizing an online Discussion/Workshop on those questions 👍
Who would be interested?