So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash – 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@asquare@asquare.srht.site Yeah we know 🤣 Still debating changes to the extension 😅
@asquare@asquare.srht.site We’ve collectively as a community (welcome to the community too! 🥳) had a many-week, multi-thread debate over this. It all boils down to Content Addressing vs. Location Addressing and the benefits, pros/cons of each approach. Ultimately though threads in Twtxt take advantage of a convention we formalized as the Twt Subject. This is combined with a Location-based Addressing, the Twt Hash extension. In the end we are likely to stay with this approach, but fix the parameters we use and truction.
I finally figured out that https://search.twtxt.net is not the same as https://twtxt.net/search. The former is open to the general public, unlike the latter which is only for registered users of twtxt.net. Meaning that I finally have some kind of access to an archive of the aforementioned debate.
It’s pretty hard to follow though, with the discussion being spread out over so many threads and with the https://search.twtxt.net UI displaying threads in a way that’s different than how https://twtxt.net does.
@asquare@asquare.srht.site Iant yhay what I said? Or did I fat-finger my reply 🤣
In any case, yes Content addressing can break threads when the original content is edited that’s for sure, however we’ve since agreed and realized that technically speaking, we can actually identify from a clients perspective, whether an edit took place.
@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.
@asquare@asquare.srht.site No need to apologise 😅 All very good points 👌