↳
In-reply-to
»
Finally I propose that we increase the Twt Hash length from
⤋ Read More
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
I’m with @andros@twtxt.andros.dev and @eapl.me@eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic@twtxt.net for all the great work you have done and all the nice conversations both here and on our video calls.
gah i’ve been so busy working on love4eva! TL;DR i switched image backends from the test/dev only module i was using to the S3 one, but with a catch - i’m not using S3 or cloud shit!!! i instead got it to work with minio, so it’s a middle ground between self hosting the image uploads & being compatible with the highly efficient S3 module. i’m super happy with it :)
i posted a patreon update that details the changes more: https://www.patreon.com/posts/i-am-now-working-127687614
that post says i didn’t update my guide yet but i actually did like right after i made that post lol so you can CTRL+F for minio stuff there!
↳
In-reply-to
»
Finally I propose that we increase the Twt Hash length from
⤋ Read More
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms.
Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a ‘micro consensus’ feels… not right.
I don’t know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.
↳
In-reply-to
»
In Spain, electricity has already been restored. Amazing experience! Luckily, I will only have to throw away some food. But there are stories of all kinds. It has been 12 hours where we have gone back to the middle ages.
⤋ Read More
@andros@twtxt.andros.dev We don’t know the cause, yet, do we? 🤔
No hay luz pero no me importa. En la vida hay que focalizarse en cazar las plumas al final del palo. El resto es secundario.
/https://baldo.cat/media/photos/IMG_4263.jpeg)
#catsoftwtxt
↳
In-reply-to
»
Finally I propose that we increase the Twt Hash length from
⤋ Read More
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
↳
In-reply-to
»
Just like we don't write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our
⤋ Read More
twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
@prologic@twtxt.net Phew, I’m indeed not twtxt.dev, because I sometimes actually do edit my feed with vim like a barbarian.
↳
In-reply-to
»
Finally I propose that we increase the Twt Hash length from
⤋ Read More
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
We have 4 clients but this should be 6 I believe with tt2 from @lyse@lyse.isobeef.org and Twtxtory from @javivf@adn.org.es?
↳
In-reply-to
»
Finally I propose that we increase the Twt Hash length from
⤋ Read More
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
@prologic@twtxt.net pinging the involved (@andros@twtxt.andros.dev, @abucci@anthony.buc.ci, @eapl.me@eapl.me, @lyse@lyse.isobeef.org, @movq@www.uninformativ.de, @sorenpeter@darch.dk), just in case. I might have forgotten someone, please feel free to ping them.
Just like we don’t write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
↳
In-reply-to
»
@javivf Ahh! So this is your client implementation? 🧐
⤋ Read More
@javivf@adn.org.es Wanna list it on twtxt.dev? 🧐
↳
In-reply-to
»
Interesting factoid... By inspecting my "followers" list every now and again, I can tell who uses a client like
⤋ Read More
jenny, tt or any other client where fetches are driven by user interactions of invoking the app. What do we call this type of client? Hmmm 🤔 Then I can tell who uses yarnd because they are "seen" more frequently 🤣
I would guess useragent tool does the trick, isn’t it?
↳
In-reply-to
»
@aelaraji I love them! Now I want to be emperor of the universe :P
⤋ Read More
@andros@twtxt.andros.dev HAHA! Easy, we’ll just ask Redream to make a little something for you! I just hope it doesn’t come with a subscription fee for… taking time off of it tho! 😆
@andros@twtxt.andros.dev One thing I really liked about the hacker news rss feeds is the link to the comments. Reckon you can add that to the feed? 🤔
↳
In-reply-to
»
I decided to use Imagor to optimise and transform the images into a stream. I am very happy with the results!
It is written in Go and is easy to run in Docker.
https://github.com/cshum/imagor
#selfhost
⤋ Read More
@andros@twtxt.andros.dev Thanks! 🙏 Just re-followed @important_dev_news@n8n.andros.dev 👌
@prologic@twtxt.net
I think it is mature enough now: https://isah-twtxt.andros.dev
If anyone is interested in transforming an RSS feed to twtxt using n8n, send me a DM 😜
PR to Add improved styles for the logo for twtxt.ndev 
↳
In-reply-to
»
I open a discussion thread: why didn't the registers work? Will they work later?
#twtxt
⤋ Read More
@andros@twtxt.andros.dev Good question, besides that, is there any place where all of them get listed?
I only know these ones:
↳
In-reply-to
»
@andros maybe create a separate, completely distinct feed for DM? That way, clients do not need to do anything, only those wanted to "talk in private" follow themselves, using their very special
⤋ Read More
dm-only.txt feeds. 😂
by commenting out DMs are you giving up on simplicity? See the Metadata extension holding the data inside comments, as the client doesn’t need to show it inside the timeline.
I don’t think that commenting out DMs as we are doing for metadata is giving up on simplicity (it’s a feature already), and it helps to hide unwanted DMs to clients that will take months to add it’s support to something named… an extension.
For some other extensions in https://twtxt.dev/extensions.html (for example the reply-to hash #abcdfeg or the mention @ < example http://example.org/twtxt.txt >) is not a big deal. The twt is still understandable in plain text.
For DM, it’s only interesting for you if you are the recipient, otherwise you see an scrambled message like 1234567890abcdef=. Even if you see it, you’ll need some decryption to read it. I’ve said before that DMs shouldn’t be in the same section that the timeline as it’s confusing.
So my point stands, and as I’ve said before, we are discussing it as a community, so let’s see what other maintainers add to the convo.
↳
In-reply-to
»
Btw @andros ; The automated feed you put together for Hacker News... Does it at any point rewrite parts of the feed as it goes along? 🤔 I've had to unfollow it because I've found in practise it makes a twt, then seems to modify that same twt (observed by content manually) at least twice. This ends up becoming effectively an "Edit" and essentially duplicate (looking) posts 😢
⤋ Read More
@prologic@twtxt.net @andros@twtxt.andros.dev You can delete these feeds (created by me):
https://feeds.twtxt.net/project26/twtxt.txt
https://lor.sh/@Katze_942.rss <- i’m added him but can’t find file
the only rss i follow is https://feeds.twtxt.net/posts-from-atdarkcat09atdc09-ru/twtxt.txt
↳
In-reply-to
»
After reading you, @eapl.me, I'll tell you my point of view.
In my opinion, a feed does not have to be equivalent to a timeline. A timeline is a representation of the feed adapted to a user. You may not be interested in seeing other people's threads or DMs. But perhaps they are interested in seeing mentions or DMs directed at them. It is important not to fall into the trap. With that clarification...
I insist, this is my point of view, it is not an absolute truth: I don't think extensions should be respectful of customers who are no longer maintained.
We cannot have a system that is simple, backwards compatible and extensible all at the same time. We have to give up some of the 3 points. I would not like to give up simplicity because it will then make it harder to maintain the customers who do stay. Therefore, I think it is better to give up backwards compatibility and play with new formulas in the extensions. I don't think it's a good idea to make a hash keep so much load: a hashtag, a thread and also a DM.
⤋ Read More
@andros@twtxt.andros.dev nothing stands still, I agree. I think current twtxt has surpassed the initial specification, while still being relatively backwards compliant/compatible but, for how long?
As for new extensions (DM, for example), they should be OK as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
↳
In-reply-to
»
@andros maybe create a separate, completely distinct feed for DM? That way, clients do not need to do anything, only those wanted to "talk in private" follow themselves, using their very special
⤋ Read More
dm-only.txt feeds. 😂
@andros@twtxt.andros.dev Some good points here that I share and empathize with 🙌
↳
In-reply-to
»
@bender I use it. It's not the feature I use the most in the fediverse, but I communicate this way with several friends. For example, it's the main way I talk to the original creator of the twtxt-el repository, the way people greet me for the first time or the way they notify me of some bugs in the software I maintain. I can even tell you that it's the main way I talk to some maintainers of the Emacs community. If there are any of you reading my words, speak up!
Why not have the same? There are things I want to say to @prologic in private, why should I have to send him an email or private IRC? Or an public twt.
Of course, here's a topic we've already talked about: what is twtxt for you? For me it will always be a social network, in microblogging format, but an asynchronous way of communicating. And having a tool to control visibility is basic 😄
I look forward to hearing from you @eapl.me !
⤋ Read More
@andros@twtxt.andros.dev Zulu said:
what is twtxt for you?
For me Twtxt is just the underlying format that Yarn.social builds upon 😅
↳
In-reply-to
»
Btw @andros ; The automated feed you put together for Hacker News... Does it at any point rewrite parts of the feed as it goes along? 🤔 I've had to unfollow it because I've found in practise it makes a twt, then seems to modify that same twt (observed by content manually) at least twice. This ends up becoming effectively an "Edit" and essentially duplicate (looking) posts 😢
⤋ Read More
@andros@twtxt.andros.dev Ahh cool! I’ll try following it again 🤣 Mind @-mentioning/linking@twtxt.net the feed again? 🙏
↳
In-reply-to
»
Proposal: Change the order of twts in the feeds
https://git.mills.io/yarnsocial/twtxt.dev/issues/26
I drop the bomb and leave! 💣 🏃➡️
#twtxt
⤋ Read More
@andros@twtxt.andros.dev Haha 🤣 We’ve explored this idea in the past and we decided that it’s actually a good idea to have an “append-only” feed for various reasons. We’ve also explored the idea of using Range requests, but opted instead to just archive/rotate our feeds periodically 😅 There really isn’t much point in having a feed in reverse chronological order, except (maybe?) so a human read view the new twts at the top of the file?! 🤣
Proposal: Change the order of twts in the feeds
https://git.mills.io/yarnsocial/twtxt.dev/issues/26
I drop the bomb and leave! 💣 🏃➡️
#twtxt
Mi oscuro secreto en las videoconferencias
/https://baldo.cat/media/photos/IMG_0154.jpeg)
#catsoftwtxt
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@prologic@twtxt.net My cache never expires automatically. 😅 I sometimes wipe it for dev purposes, though.
Btw @andros@twtxt.andros.dev ; The automated feed you put together for Hacker News… Does it at any point rewrite parts of the feed as it goes along? 🤔 I’ve had to unfollow it because I’ve found in practise it makes a twt, then seems to modify that same twt (observed by content manually) at least twice. This ends up becoming effectively an “Edit” and essentially duplicate (looking) posts 😢
↳
In-reply-to
»
@javivf Generally speaking if it has been reviewed, discussed and merged, then we accept it as a standard to the set of specs we support. However we might want to document this process and set some guidelines about this to be clear 🤣 We've been fairly lax/lose here and I think that's okay given teh size of our community 👌
⤋ Read More
@prologic@twtxt.net merged to what? to yarn? I though twtxt.dev was solution-agnostic 👀
↳
In-reply-to
»
@eaplme you wrote:
⤋ Read More
Ha! I stand corrected, didn’t scrolled long enough. Indeed, it should be added (you will need an account on Mills’ Gitea), noted.
↳
In-reply-to
»
@david @andros The correct hash would be
⤋ Read More
si4er3q. See https://twtxt.dev/exts/twt-hash.html, a timezone offset of +00:00 or -00:00 must be replaced by Z.
@eaplme@eapl.me you wrote:
“That PHP snippet could be merged into https://twtxt.dev/exts/twt-hash.html”
Why, though? AFAIK @andros@twtxt.andros.dev’s client is on Emacs, @lyse@lyse.isobeef.org’s is on Python (and Golang, for tt2), @movq@www.uninformativ.de’s is on Python, and @prologic@twtxt.net’s is on Golang. All the client creator needs to know is in the documentation already, coding language agnostic.
↳
In-reply-to
»
@andros maybe create a separate, completely distinct feed for DM? That way, clients do not need to do anything, only those wanted to "talk in private" follow themselves, using their very special
⤋ Read More
dm-only.txt feeds. 😂
@andros@twtxt.andros.dev I give you not creating another file, but then I’d vote for commenting out DMs. See https://eapl.me/timeline/post/z5e2bna
It’s easier to find the DM in comments from your side, than asking all the client maintainers to add the regex =P
You can even use a Modified comment, such as
#! <DM content>
Or something like that
This approach is retro-compatible with current and older clients.
↳
In-reply-to
»
@david @andros The correct hash would be
⤋ Read More
si4er3q. See https://twtxt.dev/exts/twt-hash.html, a timezone offset of +00:00 or -00:00 must be replaced by Z.
just a note that we are doing that on PHP: https://github.com/eapl-gemugami/twtxt-php/blob/master/docs/03-hash-extension.md#php-72
That PHP snippet could be merged into https://twtxt.dev/exts/twt-hash.html
↳
In-reply-to
»
@david If I run
⤋ Read More
@movq@www.uninformativ.de this settles it then. Hopefully @andros@twtxt.andros.dev can make slight corrections, and broken threads will be a thing of the past! Thanks!
↳
In-reply-to
»
@david If I run
⤋ Read More
@david@collantes.us @andros@twtxt.andros.dev The correct hash would be si4er3q. See https://twtxt.dev/exts/twt-hash.html, a timezone offset of +00:00 or -00:00 must be replaced by Z.
(That said, there’s a bug in jenny as well. It only replaces +00:00, not -00:00. 🤡)
↳
In-reply-to
»
@david If I run
⤋ Read More
@andros@twtxt.andros.dev maybe @movq@www.uninformativ.de, @lyse@lyse.isobeef.org, @prologic@twtxt.net, and @xuu@txt.sour.is can explain what’s going on here, or which approach is the right one. One thing seems to be happening: your approach is breaking “conversations” (threads), as the other clients seemingly do not agree.
↳
In-reply-to
»
@prologic @bender
⤋ Read More
@andros@twtxt.andros.dev the hash on @aelaraji@aelaraji.com’s last message (as I type this) is:
[si4er3q] [2025-04-16 22:49:11+00:00] [Am I tripping or `rsync` is actually THIS effing faster than `scp`!!? 🫨]
So, si4er3q
↳
In-reply-to
»
@andros maybe create a separate, completely distinct feed for DM? That way, clients do not need to do anything, only those wanted to "talk in private" follow themselves, using their very special
⤋ Read More
dm-only.txt feeds. 😂
@andros@twtxt.andros.dev define “compatible” 😅. On the “not addressed to me”, if I follow you, I will see your twtxts, whether they are addressed to me, or not.
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@andros@twtxt.andros.dev Curious where this root twt is?! 🤣 Apparently my pod doesn’t have it and I can’t find it anywhere. It’s suppose to be “
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@andros@twtxt.andros.dev For what purpose? 🤔
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@xuu@txt.sour.is Seems to be fine here?
$ bat https://twtxt.net/twt/yfv5kfq | jq '.text'
"!<dm-echo https://dm-echo.andros.dev/twtxt.txt> U2FsdGVkX1+QmwBNmk9Yu9jvazVRFPS2TGJRGle/BDDzFult6zCtxNhJrV0g+sx0EIKbjL2a9QpCT5C0Z2qWvw=="
↳
In-reply-to
»
@prologic @bender @eapl.me I think opening another file is a bad idea because it adds complexity to the clients, breaks the single feed and I think keeping legacy clients will be more complex to add new features in the future. A modern approach is important.
I'll be honest, I'm a bit tired of the fight around the direct message. Perhaps, we can remove it as an extension and use the alternative @prologic . My suggestion apparently doesn't like to the community. I have no problem with remove it.
⤋ Read More
@andros@twtxt.andros.dev @bender@twtxt.net @prologic@twtxt.net @eapl.me@eapl.me btw does twtxt dm and salty can be bridged together? iirc you planned this
↳
In-reply-to
»
@prologic @bender @eapl.me I think opening another file is a bad idea because it adds complexity to the clients, breaks the single feed and I think keeping legacy clients will be more complex to add new features in the future. A modern approach is important.
I'll be honest, I'm a bit tired of the fight around the direct message. Perhaps, we can remove it as an extension and use the alternative @prologic . My suggestion apparently doesn't like to the community. I have no problem with remove it.
⤋ Read More
@prologic@twtxt.net @bender@twtxt.net @eapl.me@eapl.me @andros@twtxt.andros.dev I’m new in the neighborhood and I would like to ask you something :) When a new extension is published in twtxt.dev , is it open for discussion or ready for implementation?
↳
In-reply-to
»
It's ready 🥳! https://dm-echo.andros.dev/
An example: https://dm-echo.andros.dev/generate/?url=https://twtxt.andros.dev/
#twtxt
⤋ Read More
@andros@twtxt.andros.dev Thanks! I’ll give it a try for sure :)