@prologic@twtxt.net @movq@www.uninformativ.de @bender@twtxt.net That would be fantastic! I encourage you to give feedback or give your experience as an issue: https://codeberg.org/Texudus/website/issues
The specification gives the feeling that it is complete, but there is always gap for small adjustments.

@bender@twtxt.net LMAOOO ty bender!!! everything i do is vibes alone

@kat@yarn.girlonthemoon.xyz if I haven’t said it before, please allow me to say it now: I kinda like your attitude. Heck, I love it!

@prologic@twtxt.net no clue whenever my servers crash i never know why i just wing it

@kat@yarn.girlonthemoon.xyz Any idea why?

Globe Safety
⌘ Read more

@lyse@lyse.isobeef.org yes, it’s bad, but it’s the message what’s important. Now, if you want, I can give you a different perspective on the site, so that you will not see it as horrible anymore. And I will do for only $199.99. A bargain!

BLOB DYLAN Seen in Williamsburg (May 2025) ?~L~X https://thenewleafjournal.com/b/7rN

@movq@www.uninformativ.de @bender@twtxt.net @kat@yarn.girlonthemoon.xyz Oh yeah, this is a great article! The site looks quite horrible, but tastes are different. :-)

SELinux : https://opensource.com/business/13/11/selinux-policy-guide

And on a similar note, cross-post from Mastodon:

What I love about HTML and HTTP is that it can degrade rather gracefully on old browsers.

My website isn’t spectacular but I don’t think it looks horrible, either. And it’s still usable just fine all the way down to WfW 3.11:

• Some blog post in various browsers
  
• Git repo viewer (stagit)
  
• Older photos of WfW 3.11
  

It’s not perfect, but it’s usable. And that makes me happy. Almost 30 years of compatibilty.

The biggest sacrifice is probably that I don’t enforce TLS and that HTTP 1.0 has no Host: header, so no vhosts (or rather, everything must come from the default vhost). (Yes, some old browsers send Host:, even though they predate HTTP 1.1. Netscape does, but not IBM WebExplorer, for example.)

(On the other hand, it might completely suck on modern mobile devices. Dunno, I barely use those. 🤪)

@movq@www.uninformativ.de I LOVE THIS POST LOL

@movq@www.uninformativ.de hahaha! They sure have a point. There is always the next, shinny bandwagon to jump into.

https://alex.party/posts/2025-05-05-the-future-of-web-development-is-ai-get-on-or-get-left-behind/

@lyse@lyse.isobeef.org it’s thankfully sorted out now but i literally turned on my PC and was like WTF IS GOING ON

@bender@twtxt.net kinda sorta, it’s in a docker container so not a VM but like VM-ish?

@kat@yarn.girlonthemoon.xyz are you running Grafana in a separate physical machine (or VM) than the one you are pulling metrics from?

@kat@yarn.girlonthemoon.xyz Oh dear, what a way to start the day! :-(

@aelaraji@aelaraji.com you got this!!!!!! grafana is SO confusing but you’ll get there :D

Running - 4 miles: 4.00 miles, 00:09:40 average pace, 00:38:41 duration
nice and easy run on the treadmill. not sure how much i am going to run this week in anticipation for the final run.
#running #treadmill

@bender@twtxt.net I think this would be a good idea as @movq@www.uninformativ.de and @andros@twtxt.andros.dev have done ✅ I may even join the experiments if I have any spare time to hack a custom yrand branch and run it up on say something like a yarnexp.mills.io or something 🤔

@bender@twtxt.net This ☝️

@sorenpeter@darch.dk No because as the spec statd originally, and we didn’t change that syntax at all:

Mentions are embedded within the text in either @ or @ format

So the lextwt parser we use will simply call this an invalid mention, which it does.

@sorenpeter@darch.dk Unfortunately it does break all clients, because the original spec stated:

Mentions are embedded within the text in either @ or @ format

In other words, why didn’t you all do the same that @movq@www.uninformativ.de did, and setup a completely different feed for this?

But Yarn does not like it: https://twtxt.net/twt/yoatzwa

@ You seem to be a bit ahead of your time: https://darch.dk/timeline/conv/jl2mf2a

Yes it seem to work(ish) on timeline at least: https://darch.dk/timeline/post/imopblq

@bender@twtxt.net My point was that the suggested syntax for extending mentions to point to a specific message (@<nick url timestamp>) and having location based treading this way, might not break older clients, since they might just igonore the last value within the brackets.

April 2025 at The New Leaf Journal ?~L~X https://thenewleafjournal.com/b/7qT

@aelaraji@aelaraji.com Oh, sorry it’s a typo. Also developer previously worked in vk (making mobile app afaik). Not he hates him xD

@kat@yarn.girlonthemoon.xyz Haha that’s crazy! I’ve spent this evening trying to the same 😆 I still don’t havn’t reached my goal yet, but I’m getting there.

@kat@yarn.girlonthemoon.xyz one of my servers’ number of currently running containers is 69. haha sex number

@kat@yarn.girlonthemoon.xyz this is one of my fave k-pop songs this year nmixx have been KILLING it

i love it when k-pop girls get to do unusual genres. you ever wanted to hear a k-pop girl group do something massive attack-ish with a bit of breakbeat? well we got it https://www.youtube.com/watch?v=jy0qJC6IbgY

@thecanine@twtxt.net doggo!!!!!!!!!!!

smug woof

@andros@twtxt.andros.dev@andros@twtxt.andros.dev i know MVC but i don’t know model view view model what does this mean…. i am learning PHP (and a tiny bit of perl scripting) as a mainly ruby girl so mayhaps i am improving but my focus is SERVERS

@prologic@twtxt.net noted 🫡 🫡 🫡

Un movimiento global promueve la posibilidad de reparar productos en lugar de desecharlos, buscando combatir la obsolescencia programada https://t.ly/dNlvM

@prologic@twtxt.net hahahahaha! Don’t you go watering that seed, mate 😅. I mean, we all dream about it, ain’t that right?

@movq@www.uninformativ.de Just like Friday’s right? 😅

@bender@twtxt.net Mondays should be optional.

@javivf@adn.org.es You’re free to send me a DM. 😉

@kat@yarn.girlonthemoon.xyz HTMX is GREAT!
I used it in my TwtxtReader MK1 for pagination and posting. It just works!

@ About the URL, since it no longer used for hashing there might be no need to change it. I agree that we keep all the parts that already are out there for the most parts. Instead of a contact field you could also just use links like: link = Email mailto:user@example.dk or link = Signal https://signal.me/sthF4raI5Lg_ybpJwB1sOptDla4oU7p[...]

@sorenpeter@darch.dk you wrote:

“This might even be backward compatible with older (pre-yarn) clients.”

Yarnd is as backwards compatible with older clients as this. I dare to say, even more so. 😅

@sorenpeter@darch.dk Yes, there are interesting things that can be incorporated to see how they work.
The issue of allowing the use of Z for UTC is interesting. I think I should add a brief explanation.
The url issue is for a debate :D . Maybe an issue could be opened. My opinion is that it is necessary to leave it as it is right now because otherwise the thread system, or replies, may have problems (404s). It’s all a matter of discussion.
I like your idea of contact. I will add it.
Thanks to you for your feedback!!!

@andros@twtxt.andros.dev Thanks for consolidating a lot of good ideas. Especially how you have deiced to just extend the mention syntax for location-based treads. This might even be backward compatible with older (pre-yarn) clients.
What about using Z for UTC +00:00- is that allowed in your specs?
Regarding url = I would suggest to only allow one and the maybe add url_old = or url_alt = !?
I’m still not a fan of a DM feature, even thou it helps that i have now been split out into a separate feed file. Instead if would suggest a contact = field for where people can put an email or other id/link for an established chat protocol like signal or matrix.

@andros@twtxt.andros.dev Yup! 👌