@movq@www.uninformativ.de Awwwwww! Thank you, that is now in my collection. :-) The other ones aren’t bad either, very nice!
@thecanine@twtxt.net My apologies, mate! :-( As @david@collantes.us pointed out, this was definitely not my intent at all.
For the easter egg hunt, I first looked for a hidden image map link on the pixel dog in the right lower corner itself. Maybe one giant pixel just links to somewhere else, I figured. But I couldn’t find any and then quickly moved on. Hence, I naturally viewed the HTML source. Because where else would be a good hiding place for easter eggs, right?
Next, I noticed the <font> tags. I thought I had read quite some time ago that they are not an HTML5 thing, but wasn’t entirely sure about it. So, I asked the W3C HTML validator. Sure enough. I thought I let you know about the violations. If somebody had found a mistake on my site, I’d love to hear about it, so I could fix it. I’m sorry that my chosen form of report didn’t resonate with you all that well. I reckoned you’ll also find it a bit funny, but I was clearly very wrong on that.
I actually followed the dog cow link to the video, so I ended up on the easter egg. However, I didn’t recognize it as such. ¯_(ツ)_/¯ Oh well.
Regarding my message about the browser quirks: I read your answer that you were arguing against the HTML validator findings. Of course, everybody can do with their sites whatever they likes.
@xuu@txt.sour.is Nice one! 👍
@xuu@txt.sour.is hmmm, maybe I deleted myself.
i can see your twts here: https://watcher.sour.is/?uri=https://eapl.me/tw.txt
@david@collantes.us.. i see this one but it says its dead. https://watcher.sour.is/?uri=https://ferengi.one/twtxt.txt
i can see your twts here: https://watcher.sour.is/?uri=https://eapl.me/tw.txt
@david@collantes.us.. i see this one but it says its dead. https://watcher.sour.is/?uri=https://ferengi.one/twtxt.txt
yep, it looks nice! How could add my URL?
Is it following the same endpoints than https://registry.twtxt.org/swagger-ui/#/users/addUser ?
BTW, I think that the usage section has a wrong base URL or something.
For example if you enter here: https://watcher.sour.is/conv/4rx5iyq
It says to look for this URL: https://watcher.sour.is/conv/4rx5iyq/api/plain/users
Which seems to return the content from https://watcher.sour.is
Hi, So i made a little MVP registry crawler tool for twtxt. It now has a basic UI to play with. It has a somewhat full history back to about 2018-ish. Plus some interesting bits that were timestamped to earlier.
Find it here: https://watcher.sour.is
Code base is found here: https://git.sour.is/sour-is/xt
Hi, So i made a little MVP registry crawler tool for twtxt. It now has a basic UI to play with. It has a somewhat full history back to about 2018-ish. Plus some interesting bits that were timestamped to earlier.
Find it here: https://watcher.sour.is
Code base is found here: https://git.sour.is/sour-is/xt
@lyse@lyse.isobeef.org The bird in the wallpaper? That’s a photo from a trip to a local zoo. 😃 This little guy was sitting in one of the bushes and didn’t mind people getting rather close. Full version and more from that day.
@lyse@lyse.isobeef.org I do agree “the rules of the web”, are far too loose - at least the syntax ones. I do think backwards compatibility is necessary.
As for my website, it might be visually very similar, to how it looked since its creation, many years ago, but it is frequently improved. Features that originally used JavaScript, changed to HTML and CSS components, code simplified, optimised to withstand browser updates and new screen resolutions,… Even a good chunk of the errors on your list, were already addressed and I plan to address the rest soon.
Just find it a bit depressing, that my attempt to bring back some of the old Internet spirit, by making a hidden easteregg page page for this years April 1st, was met with people complaining about April fools day jokes and you insinuating my website sucks.
@movq@www.uninformativ.de Sorry for being completely offtopic, but that’s a really cute bird! :-)
@prologic@twtxt.net you mean, “I’ll ix this oon 😂” ™
@prologic@twtxt.net @eapl.me@eapl.me I want to highlight another social problem: People don’t read. Paper industry is a bad moment because people don’t pay for books; it does not matter if it is a physical or digital platform. I have this information because I have a good friend who left the industry after publishing a magazine, books and working in an editorial. DRM is a try to give some more money.
@lyse@lyse.isobeef.org I’m allways on the frontline! 🙃
probably this one https://yarn.girlonthemoon.xyz/user/kat/twtxt.txt
probably this one https://yarn.girlonthemoon.xyz/user/kat/twtxt.txt
@movq@www.uninformativ.de @xuu@txt.sour.is That sounds like kat! :-)
Is there some Makefile shenanigans going on maybe? $V and $C being swallowed by the Makefile. I fell in that trap again the other day.
@movq@www.uninformativ.de Oh yeah, take some pictures when you do. :-)
Just saw this user agent popping up:
yarnd/ERSION@OMMIT go1.23.4 (+https://.../twtxt.txt; @username)
ERSION? OMMIT? 😅
@bender@twtxt.net @eapl.me@eapl.me @xuu@txt.sour.is @movq@www.uninformativ.de Glad you all agree. :-D My SOAP knowledge is extremely rusty, I luckily had not to deal with that crap anymore for quite some years now. I even couldn’t remember the XML declaration and had to look it up. ;-)
@lyse@lyse.isobeef.org … I was fully expecting this to be a WSDL file. 😂
@prologic@twtxt.net I only buy stuff like that, for example games on GOG.COM. Or simply CDs or DVDs. (Rarely I “buy” a movie on some popular streaming service, fully aware that this is just “renting it”.)
But yeah, I sadly have to agree with @bender@twtxt.net. 😢
@lyse@lyse.isobeef.org Aww, this reminds me that I haven’t done any Fraktur/calligraphy in a hell of a long time. I should pick that up again. It’s always nice to see this on old buildings.
@lyse@lyse.isobeef.org this is 1990’s certified approved
@lyse@lyse.isobeef.org this is 1990’s certified approved
@lyse@lyse.isobeef.org Yeah, to be fair, there’s not much of a difference other than a few grace notes (and just lower frequencies). I was mostly just fooling around with this one. 🥴
@movq@www.uninformativ.de Yeah, I’m also disappointed each and every time.
@lyse@lyse.isobeef.org This is so crazy to me. When I think “forest”, I assume “untouched nature”, but that couldn’t be further from the truth. 🫤
@thecanine@twtxt.net And this is exactly why there are quirks modes in browsers…
I’m actually glad I don’t have to deal with all this web shit and work with compilers that hit me in the face when I do something illegal. :-)
@prologic@twtxt.net Fully agreed. I’m far more likely to buy such mediums when DRM-free. I never go near Amazon eBooks etc because of their lock-in, and I have a Kobo eReader which needs to have the books side loaded unless directly from the Kobo store. I prefer DRM-free files every time.
@andros@twtxt.andros.dev sha256 hash of twt in json. Look at converter script
Hello, i want to present my new revolution twtxt v3 format - twjson
That’s why you should use it:
- It’s easy to to parse
- It’s easy to read (in formatted mode :D)
- It used actually \n for newlines, you don’t need unprintable symbols
- Forget about hash collisions because using full hash
Here is my twjson feed: https://doesnm.p.psf.lt/twjson.json
And twtxt2json converter: https://doesnm.p.psf.lt/twjson.js
about:compat in Firefox.
@movq@www.uninformativ.de Wow, I use Firefox and didn’t realize this existed! Thanks for pointing it out. I noticed at least one bug cited a webcompat.com report; I wonder if someone at Mozilla monitors those. https://webcompat.com/issues?page=1&per_page=50&state=open&stage=all&sort=created&direction=desc
@javivf@adn.org.es Welcome to twtxt!
@lyse@lyse.isobeef.org Thanks for taking a look, and for pointing out the mixture of tabs and spaces.
I think I’ll leave reachability.c alone, since my intention there was to use an indent level of one tab, and the spaces are just there to line up a few extra things. I fixed reachability_with_stack.cc though.
SqliteCache again with a slight tweak. I might have to rethink the hard-coded LIMIT 50.
@bender@twtxt.net nope.. its causing OOM issues currently.
SqliteCache again with a slight tweak. I might have to rethink the hard-coded LIMIT 50.
@bender@twtxt.net nope.. its causing OOM issues currently.
@lyse@lyse.isobeef.org you must be loved by all the web developers in town! But ok, I have added all the missing semicolons, that should technically be there, but them not being there, does not make a difference.
Font color change inside every summary element, was a very deliberate choice, to color the text, but leave the arrow black (same as website background). But ok, I rewrote the CSS to hide the arrows and make all summaries white - since this also works better, with some dark theme enforcing browser extensions.
HOWEVER “p” as a child element of “summary” is a thing, that as far as I know, all browsers respect and if a font color is applied only once, I don’t think it matters, if it’s done through HTML or CSS, you smart ass.
@thecanine@twtxt.net I found it! This looks like colored easter eggs when squinting.
@kat@yarn.girlonthemoon.xyz They all just wanted to be friends with a cool gal like you. ;-) It’s sad that putting things openly on the internet just waits to be raided by script kiddies, bots or spammers eventually.
@movq@www.uninformativ.de Yeah, like nearly all of them. There is the so called Bannwald, where it typically is not allowed to log, but there’s only one in my entire county and I haven’t even visted it. I should change that. https://de.wikipedia.org/wiki/Bannwald
@movq@www.uninformativ.de Hahaha, geil! :-D
@movq@www.uninformativ.de Haha, that’s cool! :-D
@movq@www.uninformativ.de That’s really great! I can’t tell the difference to the original. :-)
thanks for sharing @xuu@txt.sour.is!
Checking for example https://watcher.sour.is/api/plain/twt or https://registry.twtxt.org/api/plain/tweets, I don’t know whether this syntax is being used by clients or by people. Is it integrated on Yarn in any way? Genuinely asking to know more about it.
If I might throw a quick thought to those working on the registries, it would be nice to have an endpoint with a valid twtxt output (perhaps cached or dumped to a static file) which a client could point to, helping to discover it’s content in a way which is compatible with the twtxt spec.
Taking the first twt I found in https://watcher.sour.is/api/plain/twt as an example:
reddit_world_news https://feeds.twtxt.net/Reddit_World_News/twtxt.txt 2025-03-28T00:29:25Z **China bans US logs. 3 billion dollar[...])
it would be something like
TIME <@NICK URL> TWT
2025-03-28T00:29:25Z <@reddit_world_news https://feeds.twtxt.net/Reddit_World_News/twtxt.txt> **China bans US logs. 3 billion dollar[...])
That way you could watch the latest twts with your client, something similar to what we find on Mastodon: https://mastodon.online/public/local
Some support from the clients to separate these ‘discovery’ content, from your following timeline might be required. 🤔
sorry @prologic@twtxt.net, timeline doesn’t autocomplete the mentions yet, and it was ‘difficult’ to look for your URL from the phone.
@eapl.me@eapl.me I am currently working on Implementing a registry that is also a crawler. It finds any feeds that are mentioned or in the follows header.
https://watcher.sour.is/api/plain/twt
https://watcher.sour.is/api/plain/users
I think @prologic@twtxt.net is also working on one.
@eapl.me@eapl.me I am currently working on Implementing a registry that is also a crawler. It finds any feeds that are mentioned or in the follows header.
https://watcher.sour.is/api/plain/twt
https://watcher.sour.is/api/plain/users
I think @prologic@twtxt.net is also working on one.
somehow I forgot that existed.
Perhaps it was its mention of being a demo implementation here:
https://twtxt.readthedocs.io/en/latest/user/registry.html#registry
So I though it wasn’t really active.
Anyway, I think that’s a good idea.
Is there something similar available on Yarn? Sorry for for asking if that was mentioned recently.
I think that the clients may help you to submit your URL to these directories, and also to get a view of the twts in them.
For anyone following the proposals to improve replies and threads in twtxt, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/
Please share the link with the twtxt community, and leave your vote on your preferred proposals, which will be used to gauge the perceived benefits.
Also, the conversation is open to discuss implementation concerns or anything aimed at making twtxt better.
@kat@yarn.girlonthemoon.xyz Does … does that mean … that we’re “trending” on TikTok? 😅
@xuu@txt.sour.is I had a lot of trouble figuring out how to do this too 😂
@am@yarn.girlonthemoon.xyz who are you
@gretahayes@yarn.girlonthemoon.xyz realest shit ever
@mana@yarn.girlonthemoon.xyz godspeed
@mana@yarn.girlonthemoon.xyz :D no problemmmm
@lyse@lyse.isobeef.org THANK YOUUUU I AM BOOKMARKING THIS FOR THE FUTURE <3
@mana@yarn.girlonthemoon.xyz it was FUCKING INSANE also HI MANA
@kat@yarn.girlonthemoon.xyz it’s mostly under control now but jesus christ i almost had a panic attack
@lyse@lyse.isobeef.org Commercial forest, I guess? (Are there any other forests?)
@lyse@lyse.isobeef.org I had that as my avatar/userprofile pic at work for a few years. 😆
@lyse@lyse.isobeef.org Luckily, yeah. Happens every now and then. It’s usually not even worth reporting, they often fix it in 30-90 minutes anyway.
@xuu@txt.sour.is Yeah, it will be delayed. Oh well. That’s just the way it is. :-)
@movq@www.uninformativ.de Hahaha, that filename! :-D 100 times better than I could ever play.
@xuu@txt.sour.is If the unread counter becomes negative, wouldn’t that mean I have that many more read messages? :-D
@bender@twtxt.net You’re spot on, it’s important to not introduce classical bugs!
@movq@www.uninformativ.de Oh dear. :-( Have they fixed it?
@prologic@twtxt.net @movq@www.uninformativ.de I had a t-shirt with this one or the other decade ago. :-)
@eapl.me@eapl.me this “directory” is actually named registry. You can see users at https://registry.twtxt.org/api/plain/users and his twts at https://registry.twtxt.org/api/plain/tweets
Twtxt was made for nerds, by nerds.
I’d like to change that. It’s by nerds/hackers, for nerds/hackers and friends of these. It doesn’t have to be hacky all the time, as you don’t need to be a nerd to have a blog.
But, for that to happen, someone has to build the tools to improve UX.by design there really is no way to easily discovers others
Yeah, I agree, and although there are directories of email addresses, usually you don’t want that, unless you are a ‘public figure’.
I couldn’t say that a microblogging is a “social network” by default, as a blog is not either. At the same time, people would expect to find new people and conversations, as you’d do in a forum.
I think of two features on top of the current spec:
- Clients showing a few posts of what your following are watching but you don’t, so perhaps you find something interesting to follow next. Or that feature of “Your ‘followings’ are following these accounts/people”. (Hard to explain in english, but I hope you get the idea)
- Sharing your .txt into some directory, saying “Hey, I have this twtxt URL, I want to be discovered”. I’m thinking of something like the Federated tab on Mastodon.
Hmm so looking at the swagger of the registry spec client it seems to just take a “page”.. That seems worse than doing an offset. Lol.
https://github.com/DracoBlue/twtxt-registry/blob/master/src/swagger.json
Hmm so looking at the swagger of the registry spec client it seems to just take a “page”.. That seems worse than doing an offset. Lol.
https://github.com/DracoBlue/twtxt-registry/blob/master/src/swagger.json


@bender@twtxt.net thinked about Gemini protocol. Why corporations shit this name with cryptocurrency and LLMs?
@xuu@txt.sour.is like feeds+bridgy.fed? Will be happy anyway
@bender@twtxt.net I taught the whole ecosystem 😁
@prologic@twtxt.net @eapl.me@eapl.me The question I was asked the most was: How do I discover people?
Someone came up with a fantastic idea, instead of adding the new twt at the end of the feed, do it at the beginning. So you can paginate by cutting the request every few lines.
@doesnm@doesnm.p.psf.lt haha its not coming back. he talked of a stand alone thing like feeds. but not in yarnd
@doesnm@doesnm.p.psf.lt haha its not coming back. he talked of a stand alone thing like feeds. but not in yarnd
hmm @prologic@twtxt.net how did replying to lyse double up here?

hmm @prologic@twtxt.net how did replying to lyse double up here?

@movq@www.uninformativ.de That’s not very retrocomputing!
about:compat in Firefox.
@lyse@lyse.isobeef.org I remember WebKit having a similar list, but I can’t find it right now … 🙈
@prologic@twtxt.net In all seriousness: Don’t worry, I’m not going to host some Fediverse thingy at the moment, probably never will. 😅
But I do use it quite a lot. Although, I don’t really use it as a social network (as in: following people). I follow some tags like #retrocomputing, which fills my timeline with interesting content. If there was a traditional web forum or mailing list or even a usenet group that covered this topic, I’d use that instead. But that’s all (mostly) dead by now. ☹️
@movq@www.uninformativ.de I see, fair point, yeah.
about:compat in Firefox.
@movq@www.uninformativ.de Yikes! I didn’t know about about:compat. Crazy!
@xuu@txt.sour.is Wow, that’s a giant graveyard. In my new database I have 16,428 messages as of now. Archive feed support is not yet available, so it’s just the sum of all the 36 main feeds.
Thank you @python_valencia@twtxt.python-valencia.es for letting me show you the secrets of a decentralised plain text social network like twtxt.
I hope you enjoyed the talk! ❤️🐍
#python #twtxt
I want to present the twtxt feed from Python Valencia: https://twtxt.python-valencia.es/
Technical curiosity: It is generated using n8n, using the official rss.
#welcome
@bender@twtxt.net That … was better than expected. 😂