@quark@ferengi.one No editing old Twts that are the root of a thread with replies in the ecosystem. Just results in a fork. Unless the client has an implementation that does not store Twts keyed by Hash.

jenny really isn’t well equipped to handle edits of my own twts.

For example, in 2021, this change got introduced:

https://www.uninformativ.de/git/jenny/commit/6b5b25a542c2dd46c002ec5a422137275febc5a1.html

This means that jenny will always ignore my own edits unless I also manually edit its internal “json database”. Annoying.

That change was requested by a user who had the habit of deleting twts or moving them to another mailbox or something. I think that person is long gone and I might revert that change. 🤔

@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. 🤡)

@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 #l4doaxa

🧮 USERS:1 FEEDS:2 TWTS:1309 ARCHIVED:86213 CACHE:2761 FOLLOWERS:18 FOLLOWING:14

@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=="

🧮 USERS:1 FEEDS:2 TWTS:1308 ARCHIVED:86197 CACHE:2763 FOLLOWERS:18 FOLLOWING:14

@bender@twtxt.net Sadly my earlier Twt back in ~2020 is now gone from at least this pod’s cache 🤣 – It might still exist in other pods though? 🤔 It does! https://txt.sour.is/twt/o6dsrga

Happy 1st Twtxt~iversary to me … I guess. It feels like it was 5 years since my first twt 😅

🧮 USERS:1 FEEDS:2 TWTS:1307 ARCHIVED:86184 CACHE:2751 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1306 ARCHIVED:86136 CACHE:2749 FOLLOWERS:18 FOLLOWING:14

Oops, I think this pod (twtxt.net) just sync ~1k missing root twts with god only knows which peers 🤦‍♂️ I forgot a couple of important key things:

• Only coverage with a subset of peers
  
• Only converge with trusted peers
  

Fuck me 🤣 Ooops. Sorry!

@andros@twtxt.andros.dev can you see the screenshot on my first twtxt? Here: https://twtxt.net/twt/mrccg4q

🧮 USERS:1 FEEDS:2 TWTS:1305 ARCHIVED:86099 CACHE:2730 FOLLOWERS:18 FOLLOWING:14

I was trying to optimize the SQL query used for the Compact FrontPage (anonymous view for Discovery when the Admin/Operator chooses “one twt per feed”).

@thecanine@twtxt.net Did you see my revelation earlier today? 🤔

🧮 USERS:1 FEEDS:2 TWTS:1304 ARCHIVED:86085 CACHE:2724 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1303 ARCHIVED:86066 CACHE:2715 FOLLOWERS:18 FOLLOWING:14

Hmm, Yarnd is duplicating the rendering of /twt/5jlfuua. That’s quite odd.

🧮 USERS:1 FEEDS:2 TWTS:1302 ARCHIVED:86046 CACHE:2703 FOLLOWERS:18 FOLLOWING:14

Anyway. this was a good use for search btw. I couldn’t find my Twt, so I just quickly searched for it, snap, bingo I found it in a snap! 🫰

@prologic@twtxt.net I’m not sure if that’s an intended behaviour but twtxt.net’s home page doesn’t load more than 13 twts, no more pagination/infinite scrolling…

Page 1/1 of 13 Twts

🧮 USERS:1 FEEDS:2 TWTS:1301 ARCHIVED:86025 CACHE:2684 FOLLOWERS:18 FOLLOWING:14

See:

Doesn’t look like it Hmmm

sqlite> select * from twts where content LIKE '%Linux installation%';
    hash = znf6csa
feed_url = https://www.uninformativ.de/twtxt.txt
 content = I wonder if my current Linux installation will actually make it to 20 years:

    $ head -n 1 /var/log/pacman.log
    [2011-07-07 11:19] installed filesystem (2011.04-1)

It’s not toooo far into the future.

It would be crazy … 20 years without reinstalling once … phew. 🥴
 created = 2025-04-07T19:59:51Z
 subject = (#znf6csa)
mentions = []
    tags = []
   links = []

@movq@www.uninformativ.de Apparently you wrote it :D The hash doesn’t lie? 🤣 https://twtxt.net/twt/znf6csa

@prologic@twtxt.net What happened here – did I edit my twt or is this hash wrong? 🥴

guys help how do i unmute a twt i accidentally hit the wrong button

🧮 USERS:1 FEEDS:2 TWTS:1300 ARCHIVED:85992 CACHE:2653 FOLLOWERS:18 FOLLOWING:14

Is it just me or is there a display bug for “Yarn”(s) that are duplicating the root twt? 🤔

🧮 USERS:1 FEEDS:2 TWTS:1299 ARCHIVED:85959 CACHE:2633 FOLLOWERS:18 FOLLOWING:14

I need to get Peering working again on this branch! That will drag in many Twts Twts I now no longer have 😭

🧮 USERS:1 FEEDS:2 TWTS:1298 ARCHIVED:85929 CACHE:2704 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1297 ARCHIVED:85886 CACHE:2686 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1296 ARCHIVED:85876 CACHE:2701 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1295 ARCHIVED:85862 CACHE:2698 FOLLOWERS:18 FOLLOWING:14

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

🧮 USERS:1 FEEDS:2 TWTS:1294 ARCHIVED:85849 CACHE:2703 FOLLOWERS:18 FOLLOWING:14

@andros@twtxt.andros.dev sha256 hash of twt in json. Look at converter script

🧮 USERS:1 FEEDS:2 TWTS:1293 ARCHIVED:85827 CACHE:2704 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1292 ARCHIVED:85795 CACHE:2718 FOLLOWERS:18 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1291 ARCHIVED:85790 CACHE:2724 FOLLOWERS:18 FOLLOWING:14

@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.

🧮 USERS:1 FEEDS:2 TWTS:1290 ARCHIVED:85776 CACHE:2724 FOLLOWERS:18 FOLLOWING:14

🧮 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

🧮 USERS:1 FEEDS:2 TWTS:1288 ARCHIVED:85735 CACHE:2689 FOLLOWERS:18 FOLLOWING:14

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

🧮 USERS:1 FEEDS:2 TWTS:1286 ARCHIVED:85645 CACHE:2703 FOLLOWERS:18 FOLLOWING:14