# 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? π
@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 π€
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks π€£
@GabesArcade@gabesarcade.com Youβre welcome! βΊοΈ
Finally done with the Van! Ready to roll out tomorrow morning π
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks π€£
I think I fixed this bug!
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks π€£
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β¦
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks π€£
@GabesArcade@gabesarcade.com Wiath what client? π€

