What does the #twtxt community think about having a p2p database to store all history? This will be managed by Registries.
@andros@twtxt.andros.dev this is actually already achieved with yarnd
@eapl.me@eapl.me@eapl.me@eapl.me I don’t think there’s anything wrong with an optional distributed network with participating members of the community. As long as it’s optional.
@andros@twtxt.andros.dev Would it help if I documented the two protocols that yarnd uses today for this “distributed network”? 🧐
I’d like to know more about what andros and prologic are talking about, I feel lost.
“This will be managed by Registries.” Are we talking about these registries?
https://twtxt.readthedocs.io/en/latest/user/registry.html
@eapl.me@eapl.me@eapl.me@eapl.me I replied in the fork, but essentially there’s no reason we can’t support two different models here. We already do this anyway with numerous single-user, single hosted and managed feeds + a bunch of multi-user yarnd pods that form a “distributed network”.