🧮 USERS:1 FEEDS:2 TWTS:1533 ARCHIVED:91209 CACHE:2755 FOLLOWERS:22 FOLLOWING:14
All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. You’ve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].
After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?
Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(…) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.
But that was it. All test green. \o/
🧮 USERS:1 FEEDS:2 TWTS:1532 ARCHIVED:91202 CACHE:2757 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1531 ARCHIVED:91198 CACHE:2766 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1530 ARCHIVED:91190 CACHE:2765 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1529 ARCHIVED:91181 CACHE:2774 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1528 ARCHIVED:91171 CACHE:2779 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1527 ARCHIVED:91026 CACHE:2772 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1526 ARCHIVED:90998 CACHE:2753 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1525 ARCHIVED:90728 CACHE:2735 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1524 ARCHIVED:90723 CACHE:2737 FOLLOWERS:22 FOLLOWING:14
It’s that time again, I’ve just rotated my #twtxt feed!
Find last quarter’s twts at the feed: https://tilde.pt/~marado/twtxt-2025Q3.txt , or see them on the web: https://tilde.pt/~marado/twtxt-2025Q3.html
🧮 USERS:1 FEEDS:2 TWTS:1523 ARCHIVED:90719 CACHE:2737 FOLLOWERS:22 FOLLOWING:14
Hmmm, looks like my twt hash algorithm implementation calculates incorrect values. Might be the tilde in the URL that throws something off. :-? At least yarnd and jenny agree on a different hash.
🧮 USERS:1 FEEDS:2 TWTS:1522 ARCHIVED:90698 CACHE:2723 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1521 ARCHIVED:90686 CACHE:2719 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1520 ARCHIVED:90641 CACHE:2691 FOLLOWERS:22 FOLLOWING:14
@tilde.club@tilde.club unwritten etiquette (by me, and for me, but one can hope, right?).
- Proper grammar (in any language).
- Correct capitalisation, and punctuation.
- Subject extension support.
Anything else doesn’t matter. ☺️
🧮 USERS:1 FEEDS:2 TWTS:1519 ARCHIVED:90624 CACHE:2685 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1518 ARCHIVED:90616 CACHE:2689 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1517 ARCHIVED:90598 CACHE:2685 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1516 ARCHIVED:90591 CACHE:2685 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1515 ARCHIVED:90581 CACHE:2681 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1514 ARCHIVED:90562 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1513 ARCHIVED:90556 CACHE:2686 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1512 ARCHIVED:90551 CACHE:2686 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1511 ARCHIVED:90542 CACHE:2679 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1510 ARCHIVED:90529 CACHE:2679 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1509 ARCHIVED:90522 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
@bender@twtxt.net You are totally correct! The thing is: The Caveman within was thinking how minimal can one go before things start to get too uncomfortable? And if cavemen weren’t supposed to be too self-conscious about their spelling, I could have just ssh remote echo "$(date -Is)\tTwt Twt Mother-Lover! 🤣🤣" >> /path/to/twtxt.txt and called it a day.
@aelaraji@aelaraji.com yeah, it looks tedious because it is. LOL. I can twt no matter where I am because a) with Yarn is as easy as opening a web browser, and b) with jenny is as easy at SSHing to my VPS. But, the keyword is fun. That’s what matters!
Just typing twts directly into my twtxt file.
Details:
- Opening my twtxt file remotely using
vim scp://user@remote:port//path/to/twtxt.txt
- Inserting the date, time and tab part of the twt with
:.!echo "$(date -Is)\t"
- In case I need to add a new line I just
Ctrl+Shift+u, type in the2028and hitEnter
- In order to replay, you just steal a twt hash from your favorite Yarn instance.
It looks tedious, but it’s fun to know I can twt no matter where I am, as long as can ssh in.
🧮 USERS:1 FEEDS:2 TWTS:1508 ARCHIVED:90502 CACHE:2665 FOLLOWERS:22 FOLLOWING:14
Holly! I thing I might have figured out a way to twt like a true caveman 🤣
The sad thing tho is this caveman will have to cheat a bit in order to replay properly…
(P.S: I hope the multi-lines trick works, if not then F..rog it!)
🧮 USERS:1 FEEDS:2 TWTS:1507 ARCHIVED:90489 CACHE:2664 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1506 ARCHIVED:90474 CACHE:2656 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1505 ARCHIVED:90468 CACHE:2655 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1504 ARCHIVED:90467 CACHE:2656 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1503 ARCHIVED:90457 CACHE:2649 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1502 ARCHIVED:90441 CACHE:2638 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1501 ARCHIVED:90431 CACHE:2634 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1500 ARCHIVED:90420 CACHE:2628 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1499 ARCHIVED:90410 CACHE:2635 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1498 ARCHIVED:90405 CACHE:2647 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1497 ARCHIVED:90403 CACHE:2655 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1496 ARCHIVED:90398 CACHE:2661 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1495 ARCHIVED:90390 CACHE:2678 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1494 ARCHIVED:90389 CACHE:2679 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1493 ARCHIVED:90384 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1492 ARCHIVED:90379 CACHE:2696 FOLLOWERS:22 FOLLOWING:14