In-reply-to » One of the biggest gripes of the community with the way the threading model currently works with Twtxt v1.2 (https://twtxt.dev) is this notion of:

@lyse@lyse.isobeef.org Sorry I didn’t mean to upset you or anyone here in the community. I am/was merely trying to solve what I perceive to be a problem and an ask in the community:

How do I know what a hash refers to?

I believe the reason for this stems from a curiosity of the user of whether they might find that thread interesting or whether there are new interested feeds to follow?

Although my idea increases complexity slightly (introducing a new concept) I don’t think it’s particular hard to understand, reason about or implement (complicated). One could even even make the implementation quite simple in fact.

Either way, the idea of a service (cantralised) or participating clients/registries (distributed) providing reverse hash lookups doesn’t sound too bad really.

What do you propose to solve the above problem? 🤔

⤋ Read More