(#lnrgahq) @bender@bender Yeah me too hmm 🧐
@bender @twtxt.net Yeah me too hmm 🧐 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1291 ARCHIVED:85790 CACHE:2724 FOLLOWERS:18 FOLLOWING:14
(#lnrgahq) @eapl.me@eapl.me@eapl.me@eapl.me Ahh I see 😅
@eapl.me @eapl.me @eapl.me @eapl.me Ahh I see 😅 ⌘ Read more
@xuu@txt.sour.is Got the most basic view working 😅
@xuu @txt.sour.is Got the most basic view working 😅 ⌘ Read more
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. 🤔
(#w4mnpkq) @xuu@xuu Actually… I’m working on a new Sqlite backend/cache for yarnd 🤣 I might revive yarns (_the crawler / search …
@xuu @txt.sour.is Actually… I’m working on a new Sqlite backend/cache for yarnd 🤣 I might revive yarns ( the crawler / search engine) one day 🤞 ⌘ Read more
**(#lnrgahq) @eapl.me@eapl.me@eapl.me@eapl.me What’s with your client not using the proper syntax for mentions?
$ bat 'https://twtxt.net/twt/ ...**
[@eapl.me _@eapl.me_](https://twtxt.net/external?uri=https://eapl.me/twtxt.txt&nick=eapl.me) [@eapl.me _@eapl.me_](https://twtxt.net/external?uri=https://eapl.me/tw.txt&nick=eapl.me) What’s with your client not using the proper syntax for mentions?
$ bat ‘https://twtxt.net/twt/lnrgahq’ | jq ‘.text’
”(#4xaabhq) thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a … ⌘ Read more
@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.
I wonder if I can do away with the followers follows mutes tables and expect the client to actually filter Twts appropriately before Displ …
I wonder if I can do away with the followers follows mutes tables and expect the client to actually filter Twts appropriately before Display? This would simplify the SqliteCache considerably and also mean it would be agnostic of single-user or multi-user as that’s delegated to another layer. Hmmm 🧐
⌘ Read more
Whoohoo! 😇
Whoohoo! 😇
⌘ Read more
(#zrsxk3a) @bender@bender I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly en …
@bender @twtxt.net I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly enough can add to their feeds. Otherwise yarnd uses WebSub between pods and is fairly dumb. I could never find an “intelligent” way to back-off without hurting freshness. ⌘ Read more
(#4xaabhq) @eapl.me@eapl.me@eapl.me@eapl.me Done
@eapl.me @eapl.me @eapl.me @eapl.me Done ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1290 ARCHIVED:85776 CACHE:2724 FOLLOWERS:18 FOLLOWING:14
(#dxzebnq) @movq@movq Hah I used to be a heavy mpd user myself once upon a time 😅
@movq @www.uninformativ.de Hah I used to be a heavy mpd user myself once upon a time 😅 ⌘ Read more
(#kb25goa) @xuu@xuu I had a lot of trouble figuring out how to do this too 😂
@xuu @txt.sour.is I had a lot of trouble figuring out how to do this too 😂 ⌘ Read more
Loved this so much I had to re-post it! 🤣 Thanks @xuu@xuu
Loved this so much I had to re-post it! 🤣
Thanks @xuu @txt.sour.is ⌘ Read more
(#srxmgka) @xuu@xuu LOL 😂
@xuu @txt.sour.is LOL 😂 ⌘ Read more
(#okqf5bq) LOL 😂
LOL 😂 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1289 ARCHIVED:85766 CACHE:2716 FOLLOWERS:18 FOLLOWING:14
@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
thanks andros!
instead of adding the new twt at the end of the feed, do it at the beginning
The PHP client did that originally, although I didn’t see a real benefit if you use… a client.
It could help if you read the .txt file through a browser or something. Also, not many clients are prepared to cut the request, and you can’t rely on the file being organized that way, so finally we dropped that feature.
(#vmkz5nq) @bender@bender I gave up after page 4 (DuckDuckGo) 🤣
@bender @twtxt.net I gave up after page 4 (DuckDuckGo) 🤣 ⌘ Read more
(#7xubh7a) @bender@bender I tend to think of Twtxt like Email. It is truely decentralised. So therefore by design there really is no way to …
@bender @twtxt.net I tend to think of Twtxt like Email. It is truely decentralised. So therefore by design there really is no way to easily discovers others except through social interactions and a sort of “word of mouth” of human exchanges of communications. ⌘ Read more
@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.
(#gkqvwra) @xuu@xuu no disagreements from me!
@xuu @txt.sour.is no disagreements from me! ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1288 ARCHIVED:85735 CACHE:2689 FOLLOWERS:18 FOLLOWING:14
(#frq4vla) Wait! What’s going on?! 🧐
Wait! What’s going on?! 🧐 ⌘ Read more
tt reimplementation that I already followed with the old Python tt. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.
neat! my watcher is currently sitting at about 75 MB following over 1500 feeds. only about 200 are currently somewhat active.
-rw-r--r--. 1 xuu xuu 69M Mar 25 20:46 twt.db
-rw-r--r--. 1 xuu xuu 32K Mar 25 21:34 twt.db-shm
-rw-r--r--. 1 xuu xuu 5.6M Mar 25 21:34 twt.db-wal
sqlite> select state, count(*) n from feeds group by 1;
hot|7
warm|8
cold|183
frozen|743
permanantly-dead|857
tt reimplementation that I already followed with the old Python tt. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.
neat! my watcher is currently sitting at about 75 MB following over 1500 feeds. only about 200 are currently somewhat active.
-rw-r--r--. 1 xuu xuu 69M Mar 25 20:46 twt.db
-rw-r--r--. 1 xuu xuu 32K Mar 25 21:34 twt.db-shm
-rw-r--r--. 1 xuu xuu 5.6M Mar 25 21:34 twt.db-wal
sqlite> select state, count(*) n from feeds group by 1;
hot|7
warm|8
cold|183
frozen|743
permanantly-dead|857
🧮 USERS:1 FEEDS:2 TWTS:1287 ARCHIVED:85662 CACHE:2700 FOLLOWERS:18 FOLLOWING:14
(#bnzefnq) Yeah link please 🙏
Yeah link please 🙏 ⌘ Read more
(#ajd3rxa) @lyse@lyse I think the community should be allowed to experiment mate 😅 Just make tt2 ignore such items in feeds a …
@lyse @lyse.isobeef.org I think the community should be allowed to experiment mate 😅 Just make tt2 ignore such items in feeds and you’re good 👍 ⌘ Read more
(#xxu5i3a) @eapl.me@eapl.me@eapl.me@eapl.me Yeah yarnd already filters/ignores them (for now)
@eapl.me @eapl.me @eapl.me @eapl.me Yeah yarnd already filters/ignores them ( for now) ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1286 ARCHIVED:85645 CACHE:2703 FOLLOWERS:18 FOLLOWING:14
(#uuch2uq) It looks interesting but not enough for me to buy one 😅
It looks interesting but not enough for me to buy one 😅 ⌘ Read more
(#xxu5i3a) @andros@andros This is cool! 😍 Migut just have to add support for this to see how it might work in yarnd 🤣
@andros @twtxt.andros.dev This is cool! 😍 Migut just have to add support for this to see how it might work in yarnd 🤣 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1285 ARCHIVED:85637 CACHE:2704 FOLLOWERS:18 FOLLOWING:14
(#5iql3wa) @movq@movq Is that the cwrsion that still ran on MS-DOS?
@movq @www.uninformativ.de Is that the cwrsion that still ran on MS-DOS? ⌘ Read more
(#xnhs6rq) @andros@andros Is this a book republished as a Markdown doc on GitHub or written that way?
@andros @twtxt.andros.dev Is this a book republished as a Markdown doc on GitHub or written that way? ⌘ Read more
(#wjlte6a) @lyse@lyse I’m in the banking industry, so don’t see this much🤣
@lyse @lyse.isobeef.org I’m in the banking industry, so don’t see this much🤣 ⌘ Read more
(#wr3x5cq) @andros@andros Cool! Can I joking ciwtuau? 🤔
@andros @twtxt.andros.dev Cool! Can I joking ciwtuau? 🤔 ⌘ Read more
(#vegthcq) @andros@andros @lyse@lyse ’s new client 😊
@andros @twtxt.andros.dev @lyse @lyse.isobeef.org ’s new client 😊 ⌘ Read more
(#rozpvfa) Unfortunately none of the content on the Wikipedia page for him really criticises much of his work. He must be really good at being a …
Unfortunately none of the content on the Wikipedia page for him really criticises much of his work. He must be really good at being a “businessman” and killing tech innovation 🤣 ⌘ Read more
(#rozpvfa) > After working 14 years at IBM, he became senior vice president and chief technology officer at enterprise search vendor Verity in 2 …
After working 14 years at IBM, he became senior vice president and chief technology officer at enterprise search vendor Verity in 2004.[16][14][12] In July 2005, he was hired by Yahoo! to lead Yahoo! Research in Sunnyvale, California.[17] At Yahoo!, he worked on research projects including search and advertising.[15][18] In 2011, he was appointed as Yahoo!’s chief strategy offi … ⌘ Read more
(#rozpvfa) @thecanine@thecanine I read this article and did some research. Wow! Amazing really how we can build really good tech, then kill it q …
@thecanine @twtxt.net I read this article and did some research. Wow! Amazing really how we can build really good tech, then kill it quietly all for the sake of more revenue and profits for shareholders 🤣 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1284 ARCHIVED:85614 CACHE:2703 FOLLOWERS:18 FOLLOWING:14
(#3ok7ifq) @movq@movq It’s stupid that this is geo blocked right? 😂 Must be hmmm 🤔
@movq @www.uninformativ.de It’s stupid that this is geo blocked right? 😂 Must be hmmm 🤔 ⌘ Read more
**(#3ok7ifq) @movq@movq Hmm
Video unavailable
🥲**
@movq @www.uninformativ.de Hmm
Video unavailable
🥲 ⌘ Read more
(#7ujtv2a) So amazing! 🤩
So amazing! 🤩 ⌘ Read more
(#7ujtv2a) @xuu@xuu Fuxk you’re brilliant 😍
@xuu @txt.sour.is Fuxk you’re brilliant 😍 ⌘ Read more
(#upij2ia) @xuu@xuu You’re lucky 🍀
@xuu @txt.sour.is You’re lucky 🍀 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1283 ARCHIVED:85598 CACHE:2694 FOLLOWERS:18 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1282 ARCHIVED:85584 CACHE:2693 FOLLOWERS:18 FOLLOWING:14
(#ym6tt2a) @kat@kat You are right! 🤣 That was a really lovely rendition of that song! 🎧 🙌
@kat @yarn.girlonthemoon.xyz You are right! 🤣 That was a really lovely rendition of that song! 🎧 🙌 ⌘ Read more
(#7j4k23q) @kat@kat Sounds alright to me 😹
@kat @yarn.girlonthemoon.xyz Sounds alright to me 😹 ⌘ Read more
(#h5cwthq) @kat@kat That’s thankfully not entirely true. There are some companies that are starting to realize that “Cloud” i …
@kat @yarn.girlonthemoon.xyz That’s thankfully not entirely true. There are some companies that are starting to realize that “Cloud” is actually more expensive and so we’re starting to see a bit of a migration back 🤞 ⌘ Read more
(#tmfu5da) @kat@kat I actually have experience building Caddy modules hmmm 🧐
@kat @yarn.girlonthemoon.xyz I actually have experience building Caddy modules hmmm 🧐 ⌘ Read more
(#tmfu5da) @kat@kat Interesting project 🤔
@kat @yarn.girlonthemoon.xyz Interesting project 🤔 ⌘ Read more
(#6kqvwyq) @andros@andros Yes 🙌
@andros @twtxt.andros.dev Yes 🙌 ⌘ Read more
Business trips / Off-Sites can be rather exhausting 😴
Business trips / Off-Sites can be rather exhausting 😴
⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1281 ARCHIVED:85547 CACHE:2670 FOLLOWERS:18 FOLLOWING:14
I have applied your comments, and I tried to add you as an editor but couldn’t find your email address. Please request editing access if you wish.
Also, could you elaborate on how you envision migrating with a script? You mean that the client of the file owner could massively update URLs in old twts ?
🧮 USERS:1 FEEDS:2 TWTS:1280 ARCHIVED:85265 CACHE:2782 FOLLOWERS:18 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1279 ARCHIVED:85261 CACHE:2781 FOLLOWERS:18 FOLLOWING:14
(#6kqvwyq) Yes
Yes ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1278 ARCHIVED:85213 CACHE:2788 FOLLOWERS:18 FOLLOWING:14
(#h3a6nma) @xuu@xuu Nice! 👍
@xuu @txt.sour.is Nice! 👍 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1277 ARCHIVED:85199 CACHE:2783 FOLLOWERS:18 FOLLOWING:14
(#6z2zhta) @movq@movq This is pretty good, love the music 🎶 Haha 😆
@movq @www.uninformativ.de This is pretty good, love the music 🎶 Haha 😆 ⌘ Read more
(#h3a6nma) @xuu@xuu Got a sample to show/share? 🤔
@xuu @txt.sour.is Got a sample to show/share? 🤔 ⌘ Read more
(#7psf6rq) @thecanine@thecanine 👌
@thecanine @twtxt.net 👌 ⌘ Read more
(#a62gvwa) Kind of catchty 😄
Kind of catchty 😄 ⌘ Read more
(#zldiqva) @movq@movq Bahahahahaha 😂
@movq @www.uninformativ.de Bahahahahaha 😂 ⌘ Read more
(#7ujtv2a) @xuu@xuu Oh wow! Thank you ! 🙏 And yeah even at 2x it sounds good enough to comprehend 🤣
@xuu @txt.sour.is Oh wow! Thank you ! 🙏 And yeah even at 2x it sounds good enough to comprehend 🤣 ⌘ Read more
(#dfvkgaq) @movq@movq apparently very hard 😆
@movq @www.uninformativ.de apparently very hard 😆 ⌘ Read more
(#zldiqva) @movq@movq I’d have to hear it to get it 🤣
@movq @www.uninformativ.de I’d have to hear it to get it 🤣 ⌘ Read more
(#uavwuqq) @eapl.me@eapl.me@eapl.me@eapl.me MH my pod seems to have the correct URL 🤣
@eapl.me @eapl.me @eapl.me @eapl.me MH my pod seems to have the correct URL 🤣 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1276 ARCHIVED:85172 CACHE:2772 FOLLOWERS:18 FOLLOWING:14
(#oc3snia) @xuu@xuu Yeah looks like an edge case. Because of the way he announces his preferred nick in the feed the “Reply” button spit …
@xuu @txt.sour.is Yeah looks like an edge case. Because of the way he announces his preferred nick in the feed the “Reply” button spits out @eapl.me@eapl.me@eapl.me for me, which then gets eaten as two mentions, probably matching twice against my following list? ⌘ Read more
(#ep5rg4q) @eapl.me@eapl.me@eapl.me@eapl.me test
@eapl.me @eapl.me @eapl.me @eapl.me test ⌘ Read more
(#ep5rg4q) @eapl.me@eapl.me@eapl.me@eapl.me I replied in the fork, but essentially there’s no reason we can’t support two different models here. …
@eapl.me @eapl.me @eapl.me @eapl.me I replied in the fork, but essentially there’s no reason we can’t support two different models here. We already do this anyway with numerous single-user, single hosted and managed feeds + a bunch of multi-use … ⌘ Read more
(#j3xacqa) @eapl.me@eapl.me@eapl.me@eapl.me I think the general idea that we’re settling on here is that maybe we can build a simple solution …
@eapl.me @eapl.me @eapl.me @eapl.me I think the general idea that we’re settling on here is that maybe we can build a simple solution to this whole “wtf is this hash?” problem. yarnd already forms a sort-of “distributed network” amongst its pe … ⌘ Read more
(#rozpvfa) @thecanine@thecanine 👀
@thecanine @twtxt.net 👀 ⌘ Read more
(#dfvkgaq) @movq@movq Same 😢
@movq @www.uninformativ.de Same 😢 ⌘ Read more
(#r5t4s6q) @andros@andros What a nice thing to say 🙇♂️
@andros @twtxt.andros.dev What a nice thing to say 🙇♂️ ⌘ Read more
(#ep5rg4q) @andros@andros Would it help if I documented the two protocols that yarnd uses today for this “distributed network”? 🧐
@andros @twtxt.andros.dev Would it help if I documented the two protocols that yarnd uses today for this “distributed network”? 🧐 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1275 ARCHIVED:85157 CACHE:2789 FOLLOWERS:18 FOLLOWING:14
(#i67a3pa) @andros@andros Simple enough 👍
@andros @twtxt.andros.dev Simple enough 👍 ⌘ Read more
(#ep5rg4q) @eapl.me@eapl.me@eapl.me@eapl.me I don’t think there’s anything wrong with an optional distributed network with participating members …
@eapl.me @eapl.me @eapl.me @eapl.me I don’t think there’s anything wrong with an optional distributed network with participating members of the community. As long as it’s optional. ⌘ Read more
(#ep5rg4q) @andros@andros this is actually already achieved with yarnd
@andros @twtxt.andros.dev this is actually already achieved with yarnd ⌘ Read more
(#6z7qt4a) @eapl.me@eapl.me@eapl.me@eapl.me So what was the definition of a web log back in the day? 🧐
@eapl.me @eapl.me @eapl.me @eapl.me So what was the definition of a web log back in the day? 🧐 ⌘ Read more
(#3nbdgya) @bender@bender Me neither 🙌
@bender @twtxt.net Me neither 🙌 ⌘ Read more
(#r5t4s6q) @lyse@lyse Ita more so that with enough data you start to need an index
@lyse @lyse.isobeef.org Ita more so that with enough data you start to need an index ⌘ Read more
(#r5t4s6q) @andros@andros I agree 💯
@andros @twtxt.andros.dev I agree 💯 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1274 ARCHIVED:85144 CACHE:2787 FOLLOWERS:18 FOLLOWING:14
⌘
⌘