@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 the 2028 and hit Enter
  
• 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

🧮 USERS:1 FEEDS:2 TWTS:1491 ARCHIVED:90373 CACHE:2702 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1490 ARCHIVED:90364 CACHE:2702 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1489 ARCHIVED:90325 CACHE:2699 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1488 ARCHIVED:90316 CACHE:2704 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1487 ARCHIVED:90294 CACHE:2698 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1486 ARCHIVED:90287 CACHE:2718 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1485 ARCHIVED:90281 CACHE:2739 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1484 ARCHIVED:90274 CACHE:2755 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1483 ARCHIVED:90252 CACHE:2744 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1482 ARCHIVED:90241 CACHE:2743 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1481 ARCHIVED:90211 CACHE:2731 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1480 ARCHIVED:90198 CACHE:2728 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1479 ARCHIVED:90183 CACHE:2723 FOLLOWERS:22 FOLLOWING:14

I finally solved the loading issue in my WIP reader, TwtStrm (and apologies again to anyone that got spammed while I was diagnosing the issue).

After another round of coding this weekend, I’m happy to report that it now renders all the twts (with markdown parsing), complete with localstorage and server-based file caching.

🧮 USERS:1 FEEDS:2 TWTS:1478 ARCHIVED:90172 CACHE:2715 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1477 ARCHIVED:90160 CACHE:2714 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1476 ARCHIVED:90118 CACHE:2724 FOLLOWERS:22 FOLLOWING:14

I meant, “jlj”. He used to be at https://twt.nfld.uk/, long gone now too. I wonder…

@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™ 😅

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

🧮 USERS:1 FEEDS:2 TWTS:1475 ARCHIVED:90066 CACHE:2689 FOLLOWERS:22 FOLLOWING:14

I finally resolved my issues with hashing twts… with REGEX!

Dates in JavaScript are truly strange creatures.

🧮 USERS:1 FEEDS:2 TWTS:1474 ARCHIVED:90050 CACHE:2682 FOLLOWERS:22 FOLLOWING:14

@bender@twtxt.net Thanks for asking!

So, I’ve been working on 2 main twtxt-related projects.

The first is small Node / express application that serves up a twtxt file while allowing its owner to add twts to it (or edit it outright), and I’ve been testing it on my site since the night I made that post. It’s still very much an MVP, and I’ve been intermittently adding features, improving security, and streamlining the code, with an eye to release it after I get an MVP done of project #2 (the reader).

But that’s where I’ve been struggling. The idea seems simple enough - another Node / express app (this one with a Vite-powered front-end) that reads a public twtxt file, parses the “follow” list, grabs (and parses) those twtxt files, and then creates a river of twts out of the result. The pieces work fine in seclusion (and with dummy data), but I keep running into weird issues when reading real-live twtxt files, so some twts come through, while others get lost in the ether. I’ll figure it out eventually, but for now, I’ve been spending far more time than I anticipated just trying to get it to work end-to-end.

On top of it, the 2 projects wound up turning into 4 (so far), as I’ve been spinning out little libraries to use across both apps (like https://jsr.io/@itsericwoodward/fluent-dom-esm, and a forthcoming twtxt helper library).

In the end, I’m hoping to have project 1 (the editor) into beta by the end of October, and project 2 (the reader) into beta sometime after that, but we’ll see.

I hope this has satisfied your curiosity, but if you’d like to know more, please reach out!

🧮 USERS:1 FEEDS:2 TWTS:1473 ARCHIVED:90042 CACHE:2678 FOLLOWERS:22 FOLLOWING:14

🧮 USERS:1 FEEDS:2 TWTS:1472 ARCHIVED:90032 CACHE:2678 FOLLOWERS:22 FOLLOWING:14

Nothing serious! just a sanity check Twt x) ...

@kat@yarn.girlonthemoon.xyz Mine shows 1/1 of 14 Twts 😆 I think this is a bug 🤯

🧮 USERS:1 FEEDS:2 TWTS:1471 ARCHIVED:90021 CACHE:2680 FOLLOWERS:22 FOLLOWING:14