You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Anders %3862NbV0jkLISzwtBhpQzPNHuy/+DZb3/s2fQVq3ODI=.sha256

One of the good things about the blobs protocol being so special is that it can be replaced with something else. The only thing the current messages do is reference a hash. Where you get that hash from doesn't really matter. So the more we can experiment with this the better. I'm also not super fond of the current blob protocol.

User has not chosen to be hosted publicly
@Anders %aq5WFeSRj1GH2gA7arEZ2w+8YW8uRQkPF/WRc7Ox92o=.sha256

@farewellutopia-dev I wonder what the requirements are. Is this a replacement just for < 5 MB blobs? I guess we want to know better who was sending what, instead of doing just flooding. But maybe that is separate from moving the bits around? Hyper has been integrated with the SSB eco system before, so that is one candidate. We don't need to use the whole peer discovery part, we already have that.

Anyway, keen to hear what you think the minimal requirements are?

User has not chosen to be hosted publicly
Join Scuttlebutt now