@lyse@lyse.isobeef.org True. Although I _think) this isn’t a problem and this thread is m00t 😅

@itsericwoodward@itsericwoodward.com I would have zero problems with that! If there’s enough demand, I’ll write up the APi spec for it? 🤔

Say hello to the Twtxt Social Graph 😅 #Twtxt #social #Graph

Nice! 👌

This is just browser rendering

🥳 Finally! After nearly 4 years, yarnd v0.16.0 “Silver Sojourner” is out! 🚀 Twt Hash v2, SQLite FTS5 search, HTMX-powered UI, first-time setup wizard and literally hundreds of bug fixes 🐛

Release notes: https://git.mills.io/yarnsocial/yarn/releases/tag/0.16.0

Upgrading is fully automatic — the Twt Hash v2 migration re-fetches all feeds on first start, so expect the first cycle to be a bit heavier. Images on Docker Hub as prologic/yarnd:0.16.0 👌

cc @kat@yarn.girlonthemoon.xyz @abucci@anthony.buc.ci @shinyoukai@yume.laidback.moe @eldersnake@we.loveprivacy.club 🙏

@balloonfu-sen@yarn.girlonthemoon.xyz I could in toehry publish a specification for what twtd implements, which forms the basis of the API between twtxt.app <-> twtd, if you wanted to write your own twtd / twtxt.app compatible publishing backend (assuming you didn’t want to use Github/Gitea, etc).

In other words, try to avoid Editing if you can 🤣

Yeah to @david@daiwei.me’s point re Editing. It’s only really safe to do so if you are sure that no-one has yet fetched your feed or replied to your Twt. But even then, you have to be quick 🤣 Editing/fixing a Twt inside of an existing thread is “oaky”, as long as it also doesn’t get forked and becomes the root of a new conversation 😅

you should see the new search engine stats page where I’ve added, spark lines, and time series graphs 👌

Haha 🤣

Go for it! 🙌

@balloonfu-sen@yarn.girlonthemoon.xyz Thank you for doing this 🙏 – Just a thought… It might be possible for this to be fully automated from the Twtxt Search engine / crawler? Right? 🤔 It has all of the data… I also think it might be possible to distinguish between 1-way feedsa and “real folks” (ya know, 2-ways feeds) 🤣

@balloonfu-sen@yarn.girlonthemoon.xyz Such tilde(s), etc, could in theory just run a twtd instance per user, or if I was convinced enough to make twtd also multi-user capable (optionally) that would also work. But many ~tilde(s) barely implement the Twtxt specs we continue to build and improve (albiet slowly and carefully).

See: https://canvas.mills.io/a/JywwWQwt

We someone need to get @kat@yarn.girlonthemoon.xyz to update her pod hmmm 🤔

@balloonfu-sen@yarn.girlonthemoon.xyz Unfortunately I tried to support SFTP but ripped this out as Browsers (which the Swag framework uses under the hood as a framework to build PWA(s)) doesn’t support raw TCP connections. So FTP / SFTP is not possible without hacks like a proxy. Which I don’t really want to support. So only things that have some kind of HTTP API are possible viable publihsing backends right now. That is Github/Gitea, twtd, Yarn, etc.

@balloonfu-sen@yarn.girlonthemoon.xyz That should work. LMK if you run into any issues!

@david@daiwei.me Nice! 😊

👍 definitely using the Twtxt App as my daily-driver now for Twtxt/Yarn. Not using twtd however, as I just pair the app with my already existing yarnd powered profile on twtxt.net

So… Quick count. Hands up those who are using the Twtxt App? 🤔 – And who’s also pairing this with the twtd publishing backend?

@david@daiwei.me Good! 👍

@bender@twtxt.net Test!

Looks like twtxt.app on mobile emits +00:00 UTC timestamps instead of Z – Yarnd should handle both, but doesn’t 🤦‍♂️ On the list 🤞

@bender@twtxt.net @david@daiwei.me Good debugging session 👌 Sounds like the root cause is twtxt.app on mobile — +00:00 timestamps and quoted mentions. I’ll dig into Yarnd’s side of that 🧐

@bender@twtxt.net Yeah, Yarnd’s mention parser is pretty naive — if twtxt.app wraps the mention in quotes it probably strips them wrong. Worth fixing 🤔

+00:00 vs Z should be treated as equivalent UTC 🤦‍♂️ I’ll take a look at the timestamp parsing in Yarnd 🧐

@lyse@lyse.isobeef.org No piccies of your camp site? 🤔

I’m starting to use the twtxt.app as my daily driver now as opposed to yarnd and my pod twtxt.met 🥳

Nice!

Fixed the broken hashes in the Twtxt App (https://twtxt.app) 🥳 It was hashing your twts with a client-side timestamp the server never used 🤦‍♂️ Now it keeps the canonical created/hash the pod (or twtd) returns, and the GitHub/Gitea backends write a # url = preamble so every client hashes your feed the same way. Thanks @fastidious@tilde.town for the report 🙏

And i’m back!

@bender@twtxt.net Whoohoo!

@GabesArcade@gabesarcade.com Glad you like what we’ve nuilt up here over many years 🥰

@bender@twtxt.net LoL down under we just pull a cover over the water at ground level. no famcy ass structure 🤣

@aelaraji@aelaraji.com was it hard to set up for you?

I will aim to have most issues bugs and user experience problems, identified and fixed by this weekend!

@aelaraji@aelaraji.com Still improving things 🤞

I agree! That one is good! Saved to my phone 😅

@aelaraji@aelaraji.com At least your feed works as well your avatar 😅

Ahh!

Also confirmed!

@bender@twtxt.net Wgt does your grass look so yellow?! 😳

@movq@www.uninformativ.de I don’t. but i do use IRC so hmmm 🧐

@bender@twtxt.net 🤣🤣

@aelaraji@aelaraji.com I cannot view your raw feed 🧐

@balloonfu-sen@yarn.girlonthemoon.xyz LOL 🤣 Too late! I already saw it and replied 😅

there is for example, a user configurable and default instance configuration called only one postponed domain

@balloonfu-sen@yarn.girlonthemoon.xyz That depends on the display configuration and preferences.

@bender@twtxt.net Danke 🙏

@david@daiwei.me I agree! Let’s get them back into the fold 🤗

@bender@twtxt.net Please create an issue for this too! Probably against twtd right? We should validate new fetchers and see if they are real clients or not. I think yarnd already does ybis quite well? 🧐

@bender@twtxt.net Thank you! 🙏

And if we can compile a list and file issues for feeds, twtxt.app and anything else as issues for when i get back 🙏 feature requests, bug reports. etc 🤞

@bender@twtxt.net Danke 🙏

If someone would be so kind as to file an issue against the repo? 🙏

@GabesArcade@gabesarcade.com Thanks for reporting! I will fix this 👌 Soon!

LOL sadly none 😅 But one day soon 🤣

@movq@www.uninformativ.de Right now it 16C and 8.30PM

@arne@uplegger.eu Really?! Wow! 😳

Couple more after a short stroll along the beach 👌

Just a couple of shots of where were staying 👇

FYi 👋 I’m aware of an optimist precomputed hashing bug on the new twtxt.app 🤯 Trying to work with @bender@twtxt.net remotely on my vacation yo fix it 🤣

Nice cat 😅

On the road 😅

What’s the bug?

Fixed 👌

Hmmm the Twtxt App isn’t grouping threads correctly 🧐

@itsericwoodward@itsericwoodward.com Haha! I’m glad you like it! 🤣 I ummed and arrred over the set of publishing backends it should support, and in the end decided to support Yarn, Github/Gitea and twtd. I hope that’s enough and flexible enough for most folks 🤞

@itsericwoodward@itsericwoodward.com Ahh you’re welcome bud! 👌

Adding support for forking, forked conversations and navigating back to the root of a thread for the Twtxt App 🤞

@GabesArcade@gabesarcade.com You’re welcome! ☺️

Finally done with the Van! Ready to roll out tomorrow morning 🚀

I think I fixed this bug!

Oh if we’re talking about the twtxt.app client, that’s a different story. I still consider that alpha/beta quality. Lemme look into that. It has it’s own cache of course (using IndexDB) and it’s entirely possible some behaviours are still not quite right yet…

@GabesArcade@gabesarcade.com Wiath what client? 🤔

@bender@twtxt.net I don’t see it 😅

@GabesArcade@gabesarcade.com Yes, because if you edit/delete a Twt after the ecosystem has ingested it, well there then are two versions 😅 Just be aware of edits/deletes, especially if someone has already replied to said Twt 🤣

only seeing your post once 😅

hmm some avatars not showing in the app still 😢

what do you mean?

It’s no big deal of course, we are fully aware of the couple of rare(ish) edge cases with the threading model.

@GabesArcade@gabesarcade.com Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🤣

@javivf@adn.org.es Very cool! 😎

@javivf@adn.org.es Heh! 😏 I don’t get it haha, but I just saw your post about supporting the v2 Hash ext, nice! 👍

@GabesArcade@gabesarcade.com LOL All god! I just announced it just now 🤣

@javivf@adn.org.es Not really what? 🤔

Hello everyone ! 👋 Behold I bring you (after many years) the launch of the Twtxt App 😅 – Ye, this is a Desktop and Mobile app built as a Progressive Web App (PWA) using a little framework (Swag) I put together iafter some experiments @xuu@txt.sour.is and I did in Go and HTMX and Service Workers.

The App is offline-first and supports installing to Desktop and Mobile (add to Home screen) and supports a number of publishing backends, including Yarn.social’s yarnd Pod, Github, Codeberg/Gitea, and a little tiny twtd Twtxt server (See: https://git.mills.io/yarnsocial/twtd).

Please try it out, no need for any account(s) or such, works with your existing feed(s) (as long as the publishing backends work well enough for you!). Please give me feedback! 🙏

Also, did you know the Twtxt Search Engine is back? 🎉

@GabesArcade@gabesarcade.com You mean the one I haven’t quite announced yet? https://twtxt.app ? 🤣

@lyse@lyse.isobeef.org Good! 👍

Okay I’m going to bed, g’night folks 👋

@GabesArcade@gabesarcade.com I’m obviously Aussie, but happy 4th July to you too! 🎉

@GabesArcade@gabesarcade.com LOL You can Email me, hit me up on Signal, orc IRC. Take ya pick I’m around 😅

@fastidious@tilde.town Done and done ✅ Should get an “Upgrade” banner and button soon™

@lyse@lyse.isobeef.org Found it and fixed it! 🎉 The crawler’s discovery spider was fetching every feed a second time, without any conditional headers (plus a couple of other politeness bugs: redirected feed URLs never stored their cache validators, and there was no floor between re-fetches). Now every feed is fetched at most once per crawl, always with If-Modified-Since / If-None-Match, and never more than once per 15m no matter what. Just deployed — please keep an eye on your access logs and let me know if you still see anything impolite from the crawler 🙏

@lyse@lyse.isobeef.org I believe this is fixed now 🤞

@lyse@lyse.isobeef.org Thanks! I’ll look into that! Could be a bug in the crawler.