It’s also (expectedly) in the feed file on disk:
2024-08-04T21:22:05+10:00 [foo][foo=][foo][foo=]
It’s also (expectedly) in the feed file on disk:
2024-08-04T21:22:05+10:00 [foo][foo=][foo][foo=]
@prologic@twtxt.net Yep. Doesn’t matter if JS in turned on or not. So it is somewhere hiding in the Go core. Some replacement going berserk, I’d say.
It happens to each bracketed text individually: https://lyse.isobeef.org/tmp/bracketed-text/triple.png
But then the question still is, why on earth does it happen to old twts, too? I’m getting into my code excavator.
@lyse@lyse.isobeef.org I think it’s these lines of code: https://git.mills.io/yarnsocial/yarn/src/commit/5101ec240ddb0e5e39809bf8a7b847508b3ac298/internal/feed.go#L162-L166
Git bisecting reveals https://git.mills.io/yarnsocial/yarn/commit/3a760502be273c306b488f8815adfd85b97a37f0 from five weeks ago. This updates all sorts of dependencies. Markdown and lextwt jump into my eye. These are my best bets so far.
@lyse@lyse.isobeef.org More on #yarn.social on LiberaChat (IRC) obviously 🙄
Fixed! 💪
Or rather reverted lextwt (for the time being)
Many thanks @lyse@lyse.isobeef.org 🙏
@prologic@twtxt.net Thanks for reverting! Now we just have to properly fix the bug. Or decide whether this attribute feature is really needed in the first place.
@lyse@lyse.isobeef.org Yeah @xuu has a Paul request to fix this already so I’ll have a look at that and get that merge soon.
[fixed]
@xuu [confirmed]