Can someone make sure this works before I use it to protect my blog?

[cr0w@infosec.exchange]

@legacv

[catsalad@infosec.exchange]

@cR0w Curiosity 🅒ed the Cat

[mehdi_benadel@mastodon.balamb.fr]

@cR0w what is this bait

[jelte@mastodon.nl]

@cR0w lol. It works.

[cr0w@infosec.exchange]

@Officeplant You can. I've done it on accident before.

[tati@eldritch.cafe]

@cR0w uh,

[cr0w@infosec.exchange]

@Eetschrijver

[cr0w@infosec.exchange]

@mehdi_benadel One way to find out...

[victoria@lgbtqia.space]

@cR0w

[cr0w@infosec.exchange]

@theorangetheme

[eetschrijver@mastodon.social]

@cR0w Sorry. But this is just more Google enshittification, and I'm not the only one running away from any website that implements it.

[ehproque@neopaquita.es]

@cR0w not at a supermarket right now, can it wait till Saturday?

[albertcardona@mathstodon.xyz]

@cR0w

Once upon a time we had to tune modrewrite to keep the leechers from reusing our website's images elsewhere. One wonders what, now, will stop the leecher bots of the scraper companies. I'd use basic auth if it wasn't that LLMs may answer the challenge better than many human visitors.

[fuzzyfuzzyfungus@cyberplace.social]

@cR0w I have the oddest feeling that 'details' is doing a lot of carefully crafted heavy lifting in that privacy assertion.

[cr0w@infosec.exchange]

@ehproque Definitely make sure to test it with lots of people around.

[krypt3ia@infosec.exchange]

@cR0w Is, …Is my phone supposed to be playing pac man now?

[cr0w@infosec.exchange]

@krypt3ia Damn. I meant to use the calc payload.

[lettosprey@tech.lgbt]

@cR0w Didn't _quite_ work, but that's ok, I'm not a human.

[cr0w@infosec.exchange]

@lettosprey I think the spacing in the encoding was off.

[dilf@armpit.space]

@cR0w@infosec.exchange looks good to me