prologic

twtxt.net

Problems are Solved by Method\" πŸ‡¦πŸ‡ΊπŸ‘¨β€πŸ’»πŸ‘¨β€πŸ¦―πŸΉβ™” πŸ“βš― πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘§πŸ›₯ -- James Mills (operator of twtxt.net / creator of Yarn.social 🧢)

πŸ‘ 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

​ Read More

Looks like twtxt.app on mobile emits +00:00 UTC timestamps instead of Z – Yarnd should handle both, but doesn’t πŸ€¦β€β™‚οΈ On the list 🀞

​ Read More

@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 πŸ€”

​ Read More

+00:00 vs Z should be treated as equivalent UTC πŸ€¦β€β™‚οΈ I’ll take a look at the timestamp parsing in Yarnd 🧐

​ Read More

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

​ Read More

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 πŸ™

​ Read More

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

​ Read More

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

​ Read More

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 🀞

​ Read More