@doesnm@doesnm.p.psf.lt never!
@bender@twtxt.net hmm.. indeed.
@bender@twtxt.net the EF this feed is muted. Why is yarn busted? 😁 @lyse@lyse.isobeef.org @prologic@twtxt.net
Your TOTP value has been accepted
@bender@twtxt.net So turns out something is setting my HashingURI to the value {{ .Profile.URI }} and that is making my hashes wrong so it cannot delete or edit twts.
Interesting list of features to protect users and communities on bluesky. I wonder if any make sense in text context.
Nope. 😐
Can I edit this twt?
Why is the rooted post after the replied post?? time shenanigans?
Oh. so i can see it now that i trust your pod.
@prologic@twtxt.net just rebuild my image.. though git says i am already at latest
Lol. “Lighty Encrypted” https://www.pcmag.com/news/hot-topic-breach-confirmed-millions-of-credit-cards-email-addresses-exposed
@prologic@twtxt.net I never got the root for this
@wbknl@twtxt.net I have thought of getting one. I wish there were easier tools for it than direwolf
🤑😜
@bender@twtxt.net Linux and Android. I would never iOS my friend.
@lyse@lyse.isobeef.org agree on the HTTP stuff. I mean we could mention that for optimization see RFC yadda yadda should be followed for caching. but not have it part of the spec proper.
@eapl.me@eapl.me Neat.
So for twt metadata the lextwt parser currently supports values in the form [key=value]
https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698
@sorenpeter@darch.dk on 4 for gemini if your TLS client certificate contains your nick@host could that work for discovery?