Live data from Hacker News

Protecting your email address via SVG instead of JavaScript

rouninmedia.github.io

101–110 of 180 posts

Re: Protecting your email address via SVG instead of JavaScript

#104
post #70

Heavily guarded fortress would indicate something of value inside, and the big crooks may spend a little more effort. In the age of AI, this becomes even easier. { "model" : "gpt-4-turbo", "messages" : [ { "role" : "system", "content" : [ { "type" : "text", "text" : "return a json array of all valid emails found in the image." } ] }, { "role" : "user", "content" : [ { "type" : "image_url", "image_url" : { "url" : "da…

We've had OCR for decades before GPT. I suspect GPT might perform worse than OCR. What a waste.

Re: Protecting your email address via SVG instead of JavaScript

#105

Don't have time to test myself right now - what about accessibility, can a screen reader read it?

I tested and seems accessible on the live demo. Not sure if is as protected as the author claims though, but it might throw some bots for a spin.

> but it might throw some bots for a spin.

Until some bot dev sees this, accepts the challenge, and then solves it as a function within their package that never needs updating again because it is now done. So, live it up while it is not solved. After that, just shrug your shoulders at yet another idea no longer being useful

Re: Protecting your email address via SVG instead of JavaScript

#108
A friend of mine is an absolute wizard and has been building essentially “responsive images” as SVGs with JS inside. They adapt to their size programmatically. It’s… interesting.

The fact that SVGs can even have JS embedded feels both untapped and kind of dangerous.

Re: Protecting your email address via SVG instead of JavaScript

#109

Earlier quoted context omitted.

I tested and seems accessible on the live demo. Not sure if is as protected as the author claims though, but it might throw some bots for a spin.

> but it might throw some bots for a spin. Until some bot dev sees this, accepts the challenge, and then solves it as a function within their package that never needs updating again because it is now done. So, live it up while it is not solved. After that, just shrug your shoulders at yet another idea no longer being useful

The key in this case is that this is not a problem for me even if someone implements such a protection.

The rest is mice and traps.

Post reply on HN