turns out zero width spaces are supported in tags and uh. i get this when i log in on @tit

oops.

I'm pretty sure visiting @tit will not work lol.

PSA: save the devs some work and Don't Do That (i'm so sorry)

edit: i am so glad i didn't tag my original post with global feed bc it would've killed it for everyone

edit2: everyone who follows me is also locked out. FUCK

edit3: looks like cohost admins are on the clock starting 9am EST. which is four hours from now. could be worse

cohomies, we caught the culprit! pic related it's the culprit (me)

So I was messing around with tags as I noticed apostrophes ended up in urls, unencoded! And I was wondering how other characters would end up in urls.

Well, it turns out that certain characters create a tag that eggbug doesn't like. So I couldn't access cohost anymore beyond the error page pictured.

Later, I realized that, being a tag, this shows up on the post, and therefore also on the feed of other users. Who confirmed that yep, they couldn't reach beyond the Uh Oh! page either.

So if you saw a big Uh Oh! page with eggbug and fire + some cryptic tag error: yep, that was my fault! sorry!

Shoutout to @lexi who devised a way to delete the post through console magicks and techwizardry, to free me and my followers from eternal "eggbug is on fire" doom!

please don't try to replicate this bug / at least not on a public facing account, it doesn't just fuck up your feed but also the feed of other people!
a bug report and an email have been sent to staff to let them know about this