WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

I'll update if I manage to get it to go through.

Edit 1: It's not the slash, and putting spaces before the periods doesn't do anything either. I also tried copy/pasting it in and out of a text editor in case there was some weird unicode, but that didn't do anything.

Edit 2: Snipping off the second sentence allowed me to post, then editing and pasting it back in worked. I also refreshed the tab a few times to see if that was the problem (didn't do anything). No idea what was going on here.

I'll update if I manage to get it to go through. Edit 1: It's not the slash, and putting spaces before the periods doesn't do anything either. I also tried copy/pasting it in and out of a text editor in case there was some weird unicode, but that didn't do anything. Edit 2: Snipping off the second sentence allowed me to post, then editing and pasting it back in worked. I also refreshed the tab a few times to see if that was the problem (didn't do anything). No idea what was going on here.

(post is archived)

[–] 0 pt

If you have the text somewhere from before you edited it - the failing text, that is - maybe paste it in at somewhere like https://r12a.github.io/app-conversion/ and compare the UTF codes with those of the edited text that works. Maybe there's some wonky character that tripped it up? Maybe something I wouldn't even expect to be a problem like a hard to see double space separating some words?

[–] 0 pt

Anticlutch found it above. It's "bit" and "does" separated by a space. No idea how I got it to paste in the end.

[–] 0 pt

It seems like maybe it's bit and then do. I had problems posting that but it then do seemed to work.

[–] 0 pt

Interesting

Edit: Yep, "bit" "do" seems to be causing the problem. Incidentally, I looked up "bit" dot "do" and it seems to be a URL shortener. I'm guessing spammers were using it.