Two of my six contributions to twtxt.net broke something. What a success! The first one intentionally – twt hashes now use RFC 3339 formatted timestamps. This caused old conversations to be broken. And yesterday by accident the second one. Luckily just a layout thing, but a fix is already underway.

FOLLOW: @xuu from @lyse using twtxt/1.2.3

Hello @lyse Thank you for contributing by the way 🤗

@lyse Btw.. stick an `avatar.png` on `lyse.isobeef.org` next to / alongside your `twtxt.txt` feed 😎 Twtxt pods will pick that up on the next feed cache update 😀

@prologic (#pu5mbba) Yeah, I know. I'm still trying to come up with something nice and easily recognizable. I just placed a JPEG next to it, but something this small doesn't work terribly well. I'll keep experimenting.

@prologic (#gsidgea) My pleasure! Thanks for all your efforts on improving twtxt as a whole.

@lyse (#pu5mbba) I like what you’ve put up now! It looks like a lawnmower made of Lego? 😁

@lyse (#gsidgea) No worries! I try to make these improvements as much as possible in a way that is compatible with the original spec/format or can be done with simple tools/files/protocols

@prologic (#pu5mbba) Hahaahaaa, brilliant, you're right, it's the A-Team lawnmower. :-D I took the photo yesterday in front of a new background – here in much higher resolution. Unfortunately, I don't have enough dark gray bricks to better imitate the original coloring. There are also plenty of pictures from a couple of years ago: I definitely should weed out all the duplicates someday…

@prologic (#4uhyaha) Just request the last seen twt as well in the `Range` header and if it doesn't match the old one you've already seen, you know that this feed doesn't operate in append only mode, so that you can request the whole feed. It's worth mentioning that this also happens if the key value comments at the beginning of the file have changed, too, e.g. when the maintained subscription list has been modified. Yes, not ideal. Healthy 2021 everybody!