@prologic@twtxt.net how about hashing a combination of nick/timestamp, or url/timestamp only, and not the twtxt content? On edit those will not change, so no breaking of threads. I know, I know, just adding noise here. :-P
@david@collantes.us Cool idea actually! The hash would also be shorter than the raw URL and timestamp.
@lyse@lyse.isobeef.org The hash/thread-id would be shorter, but you’d lose two other benefits of (replyto:…):
- You need a special client again to compute hashes.
- The original feed URL is no longer visible, thus you might need to ask a Yarn pod occasionally for missing twts (I do that surprisingly often, now that I’ve implemented it) – but now you’ve lost the guarantee that Yarn gives you the correct information, because you can no longer verify it.
@movq@www.uninformativ.de Right. That’s why, I’d bite the bullet and go for huge URLs. :-)
I havent’t looked at the code and I’m too lazy right now, does jenny also verify the fetched result against the hash?
@lyse@lyse.isobeef.org When it asks a Yarn pod, you mean? Yeah, it does so implicitly. It builds a tiny dummy feed from the JSON response and then looks for the specified twt hash in that feed.
@movq@www.uninformativ.de Ah, cool. :-)