@itsericwoodward@itsericwoodward.com Ill weirw it up and share it shortly 👌

Oh no!!! 😱

wrf?& bbq ?! 🤯😳

I believe we’ve nailed all the bugs down🤣 Though i am sick at the moment so i’m not at my best 😢

Awesome! 👌

@balloon-fu-sen@tw.fus.f5.si Fixed! 🥳 The Avatar URL field now actually gets written to your feed’s # avatar = metadata. Turned out it needed changes in both the app and twtd itself — so you’ll want to update your twtd instance once the new build lands. Thanks for the report! 🙏

@balloon-fu-sen@tw.fus.f5.si Ahhh! That’s a bug! Lemme fix that!

@balloon-fu-sen@tw.fus.f5.si No Avatar? 🧐

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