anyone know why a service would escape slashes (not backslashes, forward slashes) in their JSON?

like this shit is all {"url":"http:\/\/www.foobar.egg\/web\/site.html"}

is this because /foo/ is a regex string in JS?

but they're inside quotes!

@foone something something regex / something something being handled at the wrong layer was my first guess
@foone 😬 i smell a regex injection attack
@foone "little bobbie backslashes, we call her"
@foone I cannot think of a *good* reason, but bad reasons include that or "trying to use the whole ass url as a filesystem path component somewhere"

they didn't escape . so probably not regex
@foone cursed DSL where both / and \ work as string escape prefixes
@emily @foone ... but each for different sets of characters...
@emily @foone and you have to use the opposite one to escape each
@brennen @foone / as an escape *suffix*

\n = n/
\t = t/
\/ = \/, accidentally ambiguous because someone let the C people do syntax again, later defined to mean / as a patch

edit: you know you're good at computer when your shitposts find bugs in your fedi server https://codeberg.org/superseriousbusiness/gotosocial/issues/4762
[bug] Markdown escaping rules applied even when Markdown is turned off

### Describe the bug with a clear and concise description of what the bug is. I made [this post](https://fedi.uni.horse/@emily/statuses/01KKSSWHXVSYFV3R3XQTBSB7PT), in which I suggested a cursed variant of backslash escapes. In the process, I discovered a different cursed variant of backslash es...

Codeberg.org
@emily @foone i wouldnt use the lack of escapes on `\.` as a guarantee, just because _ive_ missed that enough times, the match will still work even when you get wrong so its easy to miss.
@emily @foone the JSON crackpot explicitly added \/ as (optional) escape for slash; I’m not sure he ever gave a reason for that but regexen and URLs have been named.