@andros@twtxt.andros.dev I’ve commented on the ticket: https://git.mills.io/yarnsocial/twtxt.dev/issues/14#issuecomment-19142

In all reality, though, I don’t see that our community will come to an agreement. Some folks just don’t want to give up on the content-based addressing scheme.

@lyse@lyse.isobeef.org Pros/Cons. I’m not so Vince’s that switching to location based addressing will be better.

@prologic@twtxt.net its hard to change by consensus. Some things are won in implementation.

@xuu@txt.sour.is What do you mean by this? 🧐 If we implement and other clients don’t, Then we end up forking the community no? 🤔

True. Though if the idea turns out to be better.. then community will adopt it.

if you look at the subject for that twt you will see that it uses the extended hash format to include a URL address.

2025-03-02T13:20:00-07:00 (#<fmgas3a https://twtxt.net/user/prologic/twtxt.txt?t=2025-03-02T10:12:13Z>) @<prologic https://twtxt.net/user/prologic/twtxt.txt> its hard to change by consensus. Some things are won in implementation.

I think @movq@www.uninformativ.de removed support for it in jenny. 🫠

@xuu Is this why threads are getting a bit messed up lately? 🧐