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).
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 🥳
# url = preamble so every client hashes your feed the same way. Thanks @fastidious for the report 🙏
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 😅
@movq@www.uninformativ.de I don’t. but i do use IRC so hmmm 🧐
@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? 🙏