Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation

@bender@twtxt.net Hehe good sleuthing 🤣 I swear it was an edit ✍️ Haha 😂 yarnd now “sees” both every single time, where-as before it would just obliterate the old Twt, but remain in archive. Now you get to see both 😅 Not sure if that’s a good thing or not, but it certainly makes it much clearer how to write “code logic” for detecting edits and doing something more UX(y) about ‘em 🤔

@bender@twtxt.net It’s pretty cool though 🤣

@sorenpeter@darch.dk Oh!

Wrote some serious Python for the first time in like 10 years 😱 I feel so dirty 🤣

@lyse@lyse.isobeef.org Very nice! 👌 So lovely and green 😅 – What’s with the sign in ? 🧐

Interesting edit observed by the new yarnd powering this pod twtxt.net 🧐

@movq@www.uninformativ.de I’ve tried and there’s little interest so I’ve given up for now 😭

@bender@twtxt.net Wut?! 😂

@bender@twtxt.net Oh 🤣🤣🤣

Should ink to this

Hmm not sure how that link is 404’kng for you 🧐 It doesn’t here 🤦‍♂️

@bender@twtxt.net What you talk’n about 🤣 It’s not broken, it’s perfectly functional 🤣

@lyse@lyse.isobeef.org Seems legit 😅

I have a great idea for fixing the US economy. Get rid of all the nuclear weapons 🤣

@javivf@adn.org.es Wanna list it on twtxt.dev? 🧐

@javivf@adn.org.es Ahh! So this is your client implementation? 🧐

Today I added support for Let’s Encrypt to eris via DNS-01 challenge. Updated the gcore libdns package I wrote for Caddy, Maddy and now Eris. Add support for yarn’s cache to support # type = bot and optionally # retention = N so that feeds like @tiktok@feeds.twtxt.net work like they did before, and… Updated some internal metrics in yarnd to be IMO “better”, with queue depth, queue time and last processing time for feeds.

Also you have too much time on your hands 🙌 Haha 😂

@movq@www.uninformativ.de Only 99.9% pfffft 🤣

Was just looking at the client you’re using Twtxtory 🤔 Very nice! 👍 is this your client, did you write it? I’d not come across it before!

@twtxtory@twtxtory.adn.org.es Hello 👋 Welcome to Yarn.social / Twtxt 😅

@javivf@adn.org.es pretty much 👌

@quark@ferengi.one I do have an idea for syncing this 🤞

$ bat https://twtxt.net/twt/edgwjcq | jq '.subject'
"(#yarnd)"

hahahahaha 🤣 Does your client allow you to do this or what? 🤔

Bahahahaha 🤣

@bmallred@staystrong.run Hehe, @bender@twtxt.net is gonna be upset with you for “making up a thread/subject” 🤣

@bmallred@staystrong.run No! Never 😆

Interesting factoid… By inspecting my “followers” list every now and again, I can tell who uses a client like 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 🤣

First draft of yarnd 0.16 release notes. 📝 – Probably needs some tweaking and fixing, but it’s sounding alright so far 👌 #yarnd

It worked! 🥳

@bender@twtxt.net It isn’t @aelaraji@aelaraji.com’s fault at all here 😅 I think the only way I can improve this somewhat is by introducing a similar convergence that I believe @movq@www.uninformativ.de built for Jenny which would fetch the mentioned feed temporarily to see if it contains the subject being replied to (in case it’s not in the cache).

I’ll think about doing this too, but I have to do it carefully so as not to cost too much in terms of resources or performance…

@bender@twtxt.net Nah it’s there but it’s a reply to a thread that isn’t found here hmmm 🤔

@bender@twtxt.net Oh I see hmmm 🧐

Related Twt

@bender@twtxt.net Hah! 😂

@bender@twtxt.net Well… I don’t believe it’s possible to prevent or avoid all system accidents. However, managing system safety and putting in control structures goes a long way 👌

@bender@twtxt.net How is this dense or boring? 🧐

@bender@twtxt.net Not quite sue I understand your reaction 🤣

These ideas are dr the two books:

• Drift into Failure: From Hunting Broken Components to Understanding Complex Systems by Sidney Dekker (2011)
  
• Engineering a Safer World by Nancy Leveson (2011)
  

The former I haven’t read. The later I haven’t finished reading 😅

@bender@twtxt.net 🙌

And the idea of asynchronous evolutions comes from system accidents where control failures emerge when system structure, constraints, and evolution are poorly managed.

The idea of drift into failure is small normal adaptations erode safety over time without people noticing.

@bender@twtxt.net allow me to try and explain over several Twts…

A visual flow chart diagram that illustrates how two different but very related concepts can lead to system accidents 👌

• asynchronous evolution
  
• drift into failure

Here’s an example of what you end up with (I don’t follow the feed, but it’s in my pod’s cache)

@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? 🤔

@kat@yarn.girlonthemoon.xyz Yes see UPGRADE.md – I believe @xuu@txt.sour.is is now running this live after a couple of hiccups and a bug fix. So yeah if you can, that would be cool, basically looking for early beta testers (I was the alpha tester 🤣)

@andros@twtxt.andros.dev Thanks! 🙏 Just re-followed @important_dev_news@n8n.andros.dev 👌

Also a lot of patience 😅