@lyse@lyse.isobeef.org Not bad. š¤ So this started out as a flat sheet and then you cut and folded it, like paper (more or less)?
@lyse@lyse.isobeef.org very nice! Whatās the intended usage?
@movq@www.uninformativ.de You didnāt miss anything. Just time for more useful stuff. ;-)
@bender@twtxt.net Shh yes 𤣠this is the problem with politics š by that definition; Iām not conservative š¤£
@prologic@twtxt.net well, multiculturalism, immigration, and race (to mention a few, there is more) are key points on conservativeās agendas. Thatās why I asked what you thought of it. You havenāt replied yet. Of course, no answer is an answer, right?
@bender@twtxt.net Yes but I guess what Iām saying is; āso what about it?ā Arenāt most places in the world these days āmulticulturalā to some degree or another? š¤
@prologic@twtxt.net growing up in a multicultural country has nothing to do with what you think about it, does it?
@bender@twtxt.net Well see thatās just what the freakān tests say about me haha š¤£
immigration and multiculturalism
What about it? I grew up in a multicultural country.
@lyse@lyse.isobeef.org I give up. Just doesnāt give me a 360° video. š„“ Maybe Iām just having bad luck with YouTubeās randomized stuff (maybe Iām getting āexperimentsā, who knows) ā¦
@alexonit@twtxt.alessandrocutolo.it You might wanna have a look at this: https://lyse.isobeef.org/tmp/twthash.py
@prologic@twtxt.net this is 90 degrees fork. Now that you mention being conservative socialist (first I heard of the term, had to read some to grasp whatās all about), what do think about immigration and multiculturalism?
Exactly, @zvava@twtxt.net, I agree. (Although, in my client at least, I wouldnāt use hashes anywhere.)
@movq@www.uninformativ.de Iām glad it make sense for you š I will never understand it. All I know is that Iām a conservative socialist and thereās a lot of āstupid shitā⢠happening in the world (including my own country). I still blame extreme Capitalism.
Hey @itsericwoodward@itsericwoodward.com, I just wanna let you know that twtstrm/0.4.0 sends a broken User-Agent header. Instead of the URL, the nick is repeated.
@prologic@twtxt.net Hm, I donāt know. Over here, we have parties that we would call āleftā or ārightā, one of them even calls themselves āThe Leftā. No idea about your political landscape, but it still makes sense for us. š¤ For me, at least.
@bender@twtxt.net š¤£
@zvava@twtxt.net Hahaha, I love it! This illustrates the contradiction very well.
@prologic@twtxt.net how dare you! (read it with Greta emphasis, and accent)
@movq@www.uninformativ.de See hereās the thing⦠I just donāt fucking gt this whole āleftā vs. ārightā shit⢠anymore. None of it makes any sense whatsoever. When my wife tries to explain it to me itās completely the opposite to what you just said just now š± ā So from here on, Iām just going to keep things simpleā nuttersā and ānormalā š¤£
@bender@twtxt.net I feel you buddy š¤ At one point we have quite a vibrant community. Phil was great, jlj too and Adi was well just Ado š
@prologic@twtxt.net Germany was listed as āopposingā on https://fightchatcontrol.eu/ for a while, now itās back to āundecidedā. According to netzpolitik.org, itās still debated. Also according to that page, there could be an important vote on the EU level on October 13/14.
The green party and the (far) left are opposing this (at least in Germany). Sadly, Germany is leaning more right with every year ⦠As for young people: The (far) left is the strongest party among young people, with the (far) right being the second strongest one. (https://www.tagesschau.de/wahl/archiv/2025-02-23-BT-DE/umfrage-alter.shtml) Is there cause for hope? I donāt know.
@prologic@twtxt.net you doing this reminded me of mkws, and Adi. Good times, we have seeing so many people come and go. It is kind of sad, when I think about ājjlā, and Phil, and the many othersā¦
I am feeling āmushyā today. Ugh, ageing sucks.
@bender@twtxt.net Yup! Fixing that now! š Also the Tags page and the size of the trags is intentional, as more posts are tagged with the same tag, those will result in larger size rendered tags in a kind of ātag cloudā ā At this this is the intention.
@prologic@twtxt.net yup, thatās what I meant. The lack of it on the URL is fine, but on the post itself it is always a good idea. Time frames matter.
Test.

@bender@twtxt.net Ahh yes I see what you mean. no indicate of when the post was made right? That should be ideally displayed on the page somewhere? Would you expect it in the url as well, because not having /posts/yyyy/mm/dd/.... was actually intentional. But yeah I should figure out where to put some additional metadata on the page.
@bender@twtxt.net hopeful of the same š¤
@prologic@twtxt.net I canāt upload a screenshot (tried, but Yarnd simple āateā my reply). See https://zsblog.mills.io/posts/hello-zs-blog.html. Is has no date/time on it.
@movq@www.uninformativ.de LOL. I wish and hope they keep proposing it until the proposers die of natural causes, and then it vanishes. Hopeful thinking, I knowā¦
@movq@www.uninformativ.de Kill it with fire š„
@prologic@twtxt.net need to work on the CSS. For example, the tags are too big, the code blocks (and the inline ones) are too small, the single posts have no date (intended?), and so on. Itās an alpha start!
@prologic@twtxt.net They have not rolled it out (yet), they are ājustā discussing it (for the n-th time).
@alexonit@twtxt.alessandrocutolo.it Yeah I think weāre overstating the UNIX principles a bit here 𤣠I get what youāre trying to say though @zvava@twtxt.net š If I could go back in time and do it all over again, I would have gotten the Hash length correct and I would have used SHA-256 instead. But someone way smarter than me designed the Twt Hash spec, we adopted it and well here we are today, it works⢠š
@alexonit@twtxt.alessandrocutolo.it Yes well Iām pretty big on self-hosting. Iāve even tried to start a small business/company around it (but thatās another story for another day!) ā Meanwhile I would encourage you to have a look at the work weāve done in Salty.im š
@alexonit@twtxt.alessandrocutolo.it Well we have to really use the same spec or threading doesnāt really work in a truly decentralized manner š
Thatās what Iām using right now, while my own client is still in the making.
A simple bash script to write a post in a mktemp file then clean it with regex.
I donāt even bother to hash the replies, I just open https://twtxt.net and copy the hash by hand since Iām checking the new posts from there anyway (temporarily, as I might end up DoS-ing everyoneās feed in my client right now).
@zvava@twtxt.net I axtually latest did and I wasnāt the only one š¤£
@zvava@twtxt.net Thatās what Iām leaning towards yeahš¤
@prologic@twtxt.net to clarify: i meant the ability to parse feeds using unix command line utilities, as a principal of twtxtv1ās design. im not sure how feasible it is to build a simple feed reader out of common scripting utilities when hashing is in play, and;
i concede, it does make a lot of sense to fix up the hashing spec rather than completely supplant it at this point, just thinking about what the rewrite would be like is dreadful in and of itself x.x
And I need to make something absolutely clear as well here. Twtxt was completely and utterly dead back in {Aug 2020](https://yarn.social/about.html) when I came across the spec and its simplicity and realised the lost opportunity. Since then weāve continued to grow a small but thriving community. The extensions weāve built over time have stood and lasted the test of time for the past ~5 years. We need not break things too badly, because what we have today and was designed years ago actually works quite well⢠(despite some flaws).
@zvava@twtxt.net Going to have to hard disagree here Iām sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) Iām sorry youāve completely lost me! Iām old enough to pre-date before Linux became popular, so Iām not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the āthingā⢠youāre replying to and forming a chain of other replies (a thread).
Iām sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a āMagic Dateā for which our clients use the modified function(s).

@prologic@twtxt.net the simplest thing to do is to completely forgo hashing anything because we are communicating using plain text files right now :3 while i agree hashes are incredibly helpful in the backend im not sure it has a place outside of it, it basically eliminates two core design principals of twtxt (human readability and integrating well with unix command line utilities) and makes new clients more difficult to build than it should be
@bender@twtxt.net Well honestly, this is just it. My strong position on this is quite simple:
Do the simplest thing that could work.
Itās one of the age old UNIX philosphies.
Therefore, the simplest thing⢠to do here is to just increase the hash length, mark a magic⢠date/time as @lyse@lyse.isobeef.org has indicated and call it a day. Weāll then be fine for a few hundred years, at which point thereāll be no-one left alive to give a shit⢠anyway š¤£
@prologic@twtxt.net considering other alternatives we have seeing (of which I have lost track already), yes. Why donāt you guys (client makers) take a step at a time and, for now, increase the hash length to deal with the collisions. Then location-based addressing can be added⦠or not, you know. š
@alexonit@twtxt.alessandrocutolo.it My problem is I donāt see a world where we donāt employ some form of cryptography to use as keys for threads in databases and other such things honestly. Iām not going to use url#timestamp as keys.
index.md a prehook and a few utilities:
@bender@twtxt.net Yes I did about a week or so ago. It took me a lot of effort to get the content even rendered in the first place. LOL I had to basically export my blog as HTML (can you believe that?!) ā The Hugo export just didnāt work at all š¤£
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
@movq@www.uninformativ.de Yes itās kind of terrible š ā Letās not do this š¤£
@bender@twtxt.net Really? š¤
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
@prologic@twtxt.net Thatās a completely flat threading model (you canāt reply to replies). Is that intentional?
@prologic@twtxt.net thatās not too bad! šš»šš»šš»
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
This is possibly the only other threading model I can come up with for Twtxt that I think I can get behind.
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
Example:
Alice starts thread href=āhttps://txt.sour.is/search?q=%2342:ā>#42:**
2025-09-25T12:00:00Z (tno:42) Launching storage design review.
Bob replies:
2025-09-25T12:05:00Z (tno:42) (ofeed:https://alice.example/twtxt.txt
) I think compaction stalls under load.
Carol replies to Bob:
2025-09-25T12:08:00Z (tno:42) (ofeed:https://alice.example/twtxt.txt
) Token bucket sounds good.
@itsericwoodward@itsericwoodward.com Iām glad to hear it š¤£
I would personally rather see something like this:
2025-09-25T22:41:19+10:00 Hello World
2025-09-25T22:41:19+10:00 (#kexv5vq https://example.com/twtxt.html#:~:text=2025-09-25T22:41:19%2B10:00) Hey!
Preserving both content-based addressing as well as location-based addressing and text fragment linking.
@alexonit@twtxt.alessandrocutolo.it Holy fuck! 𤣠I just realized how bad my typing was in my reply before 𤣠š¤¦āāļø So sorry about that haha š I blame the stupid iPhone on-screen keyboard āØļø
@alexonit@twtxt.alessandrocutolo.it Maybe I misunderstood, but you have to keep the timezone offsets in mind. Simple alphabetical sorting of the timestamp strings does not yield a truly chronological order. It might be close enough for you, though.
@alexonit@twtxt.alessandrocutolo.it that sounds pretty much like Italy! LOL. We pay $48 on renewal in Florida, US, but that fee isnāt Federal, so other states may pay more, or less.
@itsericwoodward@itsericwoodward.com I used the dates as is for indexing them as string, the ISO format allows for free auto sorting.
@bender@twtxt.net What?! In my country you have to pay 100⬠every 10 years of which about 75% are just taxesā¦
@movq@www.uninformativ.de Iāve got this magic spell in my config: -f bestvideo[height<=?1080]+bestaudio/best
@itsericwoodward@itsericwoodward.com pretty cool! Started following you, not to miss any progress. Thanks for the exhaustive reply!
yt-dlped https://www.youtube.com/watch?v=OZTSIYkuMlU. It's only worth for an experiment, no recommendation to watch.
@lyse@lyse.isobeef.org thatās pretty cool! The first video I see on YouTube of that kind. Thanks!
@lyse@lyse.isobeef.org Hm, I couldnāt trick yt-dlp into downloading the correct format. Works in the browser, though. š
@bender@twtxt.net @movq@www.uninformativ.de I had automatically yt-dlped https://www.youtube.com/watch?v=OZTSIYkuMlU. Itās only worth for an experiment, no recommendation to watch.
@melyanna@tilde.club Exit! Exit!!1! https://movq.de/v/c51aa76926/exit-exit-exit.jpg
@lyse@lyse.isobeef.org I canāt remember the last time I came across a 360° video. š¤
@bender@twtxt.net A renewed vision test might be a good idea for some people. š I mean, it is kind of curious that you get this license as a young person and then it lasts a lifetime, without any further tests. As long as you donāt screw up really bad, it remains valid ā¦
@movq@www.uninformativ.de I tried making an ascii scribble of penguin waving back at you but I gave up halfway through my first try xD ⦠HI! š
Thanks @bender@twtxt.net itās been a long time indeed but, I was here the whole time. Just silent. I just didnāt have much meaningful/worth twting about ⦠/ME flips a bird to life
@movq@www.uninformativ.de better than in the US. Our lasts only 10 years, and you need to go through the vision test, and, of course, pay). Recently they added a little gold star denoting āreal IDā compliance, and we had to pay $10 to get the old one replacedāout of the regular renew āscheduleā.
In here it is all about control, and money.
@lyse@lyse.isobeef.org is it a 360 degree video online, or a local one?
@alexonit@twtxt.alessandrocutolo.it Yhays kind of love you!! Stance and position on this. If we are going to make chicken changes in the threading model, letās keep content based addressing, but also improve the use of experience. So in fact, in order to answer your question, I think yes, we can do some kind of combination of both.
@lyse@lyse.isobeef.org I donāt think thereās any point in continuing the discussion of Location vs. Content based addressing.
I want us to preserve Content based addressing.
Letās improve the user experience and fix the hash commission problems.
@aelaraji@aelaraji.com welcome back dude! Long time no see!
@movq@www.uninformativ.de Yeah, it took quite some time to load. But then it was briefly back. Now itās 503ing immediately all the time.
@lyse@lyse.isobeef.org https://www.celestrak.com (where the TLE files are downloaded from) seems to be down. :/
@lyse@lyse.isobeef.org šæšæšæš
@movq@www.uninformativ.de Woah, cool!
(WTF, asciiworld-sat-track somehow broke, but I have not changed any of the scripts at all. O_o It doesnāt find the asciiworld-sat-calc anymore. How in the world!? When I use an absolute path, the .tle is empty and I get a parsing error. Gotta debug this.)
@prologic@twtxt.net I know we wonāt ever convince each other of the otherās favorite addressing scheme. :-D But I wanna address (haha) your concerns:
I donāt see any difference between the two schemes regarding link rot and migration. If the URL changes, both approaches are equally terrible as the feed URL is part of the hashed value and reference of some sort in the location-based scheme. It doesnāt matter.
The same is true for duplication and forks. Even today, the ācannonical URLā has to be chosen to build the hash. Thatās exactly the same with location-based addressing. Why would a mirror only duplicate stuff with location- but not content-based addressing? I really fail to see that. Also, who is using mirrors or relays anyway? I donāt know of any such software to be honest.
If there is a spam feed, I just unfollow it. Done. Not a concern for me at all. Not the slightest bit. And the byte verification is THE source of all broken threads when the conversation start is edited. Yes, this can be viewed as a feature, but how many times was it actually a feature and not more behaving as an anti-feature in terms of user experience?
I donāt get your argument. If the feed in question is offline, one can simply look in local caches and see if there is a message at that particular time, just like looking up a hash. Whereās the difference? Except that the lookup key is longer or compound or whatever depending on the cache format.
Even a new hashing algorithm requires work on clients etc. Itās not that you get some backwards-compatibility for free. It just cannot be backwards-compatible in my opinion, no matter which approach we take. Thatās why I believe some magic time for the switch causes the least amount of trouble. You leave the old world untouched and working.
If these are general concerns, Iām completely with you. But I donāt think that they only apply to location-based addressing. Thatās how I interpreted your message. I could be wrong. Happy to read your explanations. :-)
@kat@yarn.girlonthemoon.xyz Mine shows 1/1 of 14 Twts š I think this is a bug š¤Æ
@itsericwoodward@itsericwoodward.com any news about this? I am, at the very least, curious!
@alexonit@twtxt.alessandrocutolo.it I took it down mostly because of continued abuse and spam:l. I intend to fix I and improve the drive and its sister at Summer point š¤
@alexonit@twtxt.alessandrocutolo.it thank you and welcome back to Yarn! The somewhat plushie-like look is intentional, so Iām glad it was noticed.
Only have 2 sizes of him in this pose, as well as most other sitting poses, but if thereās ever a sitting pose, shared by more than 2 of them, Iāll be sure to make a matrioska edit.
@prologic@twtxt.net thanks, I already follow @important_dev_news@n8n.andros.dev too.
BTW, the feed on https://feeds.twtxt.net/ seem down? It says itās in maintenance.
@alexonit@twtxt.alessandrocutolo.it Love this š
@alexonit@twtxt.alessandrocutolo.it Yeah same 𤣠Thereās also this @news-minimalist@feeds.twtxt.net feed that shows up the most important shit⢠anyway (when/if that happens).
@alexonit@twtxt.alessandrocutolo.it Personally, I find the reversed order of URL first and then timestamp more natural to reference something. Granted, URL last would be kinda consistent with the mention format. However, the timestamp doesnāt act as a link text or display text like in a mention, so, itās some different in my opinion. But yeah.
@bender@twtxt.net Seriously I have zero clue 𤣠I donāt read or watch any news so I have no idea š¤¦āāļø
The big QR code canine, has been one of my favourites - because even after a few months, I still find the pose really cute. Always thought a chibi version is a necessary addition and now I finally drew it.

@prologic@twtxt.net I know you were away, but were you under a rock?! š
@prologic@twtxt.net Yes, no doubt. Thereās always something somewhere.
@lyse@lyse.isobeef.org Some stuff is actually more reliable, thatās true. Itās also waaaaaaaaaaay more expensive, though ⦠:-)
I called it a day, yes. \o/
@movq@www.uninformativ.de But itās so reliable and they have all the experts, they know what theyāre doing! And donāt forget, itās way cheaper! Just think of the 34 cents saved every year on paper, the business dude calculated!
Enjoy your weekend! (I hope, you just called it a day and donāt have to drive to the office or silly shenanigans like that.)
@lyse@lyse.isobeef.org Yep! Super fast and efficient! š
long month 