#hide/Show IP on error page
22 messages · Page 1 of 1 (latest)
I agree with this. Some people actually have their screen sharing on and suddenly get an error, leaking their IP.
This can be solved quite easily by only making the IP visible after you click on it.
If you would like to put something there directly, for example, put the name of the browser they are using?
Yes +1 good point team, I agree as well.
Or make it hash/generate a unique user id/identifier?
So if that info is needed to debug, it can be safely passed over to the site admin(s)
We're looking into this internally, not a guarantee but heavily in favor of it.
Sweet!
Hey there Joe, I have concerns about this approach, what if a user accidentally hovers over it, do you have a measure against that? Additionally, Cloudflare uses a hard left click to make the IP visible, I think that approach is less accident prone. Just my take on it though.
I mean if a user is screen sharing and something is blurred and they hovered over it. It is kind of their fault.
While I agree with you, I think a left click + confirmation prompt wouldn't hurt.
perhaps, we will see.
"Clicking this will reveal your IP address client-side, please ensure you are not running any screen recording or screen sharing software before continuing for your privacy."
Etc.
What if they are monitor hopping for example, etc? There are many ways in which this can be accidentally triggered. Another approach to consider is a long hover (a delay would be required) to set it off.
Something simple like text over the blurred ip that says “click to reveal” would be perfect for this
+1 for the left click.
Left click can still be css-only if you use either :focus or you get creative with styling a checkbox and :checked
cloudflare requires JavaScript for the click to reveal
Agreed.. lol
on hover is best we'll do I think for now, it's still an improvement. anything else would require modifying the DOM (adding JavaScript or modifying the HTML inc CSS hacks), which adds complexity and increases the response body to the client unnecessarily.
It was a quick win, as we had the CSS centrally stored.