@carsten@yarn.zn80.net Working on it 🙏
Which I guess I got the name of the feature wrong, it’s filters_and_lists
🤦♂️ But yarnd --enable-feature list
will always tell you what’s currently being feature flagged / experimental:
$ ./yarnd --enable-feature list
Available Features:
- foo
- filter_and_lists
- webfinger
@eldersnake@we.loveprivacy.club No worries – For reference I’m currently running:
filter_and_lists
webfinger
Fixed now 😅 Sorry @lyse@lyse.isobeef.org 🙏
@movq@www.uninformativ.de Sorry about that, I accidently messed up some “blocked feeds” on my pod 🤦♂️
@movq@www.uninformativ.de Ooops I think I tucked something 😆
@tkd@yarn.takuma-csirt.com Ahh cool 👌 Feel free to contribute anything back like YouTube embedding 👌
@eldersnake@yarn.andrewjvpowell.com Thays behind a feature flag at the moment. lists_and_filtets
kind of glad you upda semi-frequently, because it means there are more people testing the latest changes 🙇♂️
@eldersnake@we.loveprivacy.club Literally the only difference is edge
is what the CI builds. Unfortunately I’m unable to give it a properly version number from tags from CI. Go off the commit hash and build date, looks like you’re on the latest version and the same as my pod 👌
@mckinley@twtxt.net Hey, haven’t seen you around lately? 🤔
Sorry for the fast spam 🙏
Like this should be a reply to:
Hopefully that’s the last bug squished 🤞 I overlooked the fact that a Twt can actually have an empty subject d’uh 🤦♂️
Hopefully that’s the last bug squished 🤞 I overlooked the fact that a Twt can actually have an empty subject d’uh 🤦♂️
@bender@twtxt.net Fixed another bug 🐛 🔨
@bender@twtxt.net I’ll keep working at it 👌
@bender@twtxt.net Are you sure it isn’t caching? I just saw your reply in the right Yarn now 🤣
Its the only thing that makes sense. I’ve double and triple checked the templates and backend code. The diff really wasn’t that large 🤦♂️ I did however change some structural elements of the HTML used.
Done
I’m starting to think there’s some kind of stupid ass caching problem going on somewhere. I’m going to nuke the Cloudflare cache now… If you can nuke your Mobile Safari cache for good measure?
And Mobile here
@bender@twtxt.net I’m on Desktop here
@bender@twtxt.net I’m starting to feel quite stupid now 🤦♂️
And a reply to the fork
And a fork for good measure
Reply from discover
Reply from timeline
Test post (please ignore)
@mckinley@mckinley.cc Cool! 👌 Got an example to show? 🤔
What am I missing? 🤦♂️
@bender@twtxt.net I just did, this is my reply to:
Go to “Discovery”, and tap reply to anything.
From Discover view.
I did fix
Hmm
Every case I’ve tested is working… I’m not sure what I’ve missed 😢
Hmm
@bender@twtxt.net Test
It’s not like I’m using a different interface 😅
@bender@twtxt.net it should! 🤣
@bender@twtxt.net it should
@bender@twtxt.net Can’t. be completely certain, but that might have done it…
Which I think I fixed 🤔
Not seeing any JS bugs on Mobile Safari, so gonna re-roll my pod after fixing a minor bug 🤞
That one worked
@bender@twtxt.net hmmm
Teat
Da fuq?!
Test yeah 😢
Fuck that’s a bug. But I think there might be a Javascript bug on Mobile 🤦♂️