11–20 of 126 posts
Very cool. How does Plus handle updating screenshots taken on authenticated pages once that authentication has expired?
This seems like a spectacular way to break permissions restrictions and escape data to non-authorized entities. If it's successful, it's the sort of thing that will be brutally blocked by IT all over the place. Very slick, though.
B/c I feel like that is super common and kind of impossible to stop with a permissions approach.
Really interesting tool and not even quite sure how the technology works. It's opening it's own browser window (hidden) and capturing the same x/y pixels? Pretty clever. Also, does anyone know what this new design trend is called? The bordered / minimal-but-not look?
Very cool. How does Plus handle updating screenshots taken on authenticated pages once that authentication has expired?
This is so clever. Love it. Would love a version that just runs locally without sending things to the cloud.
?
This seems like a spectacular way to break permissions restrictions and escape data to non-authorized entities. If it's successful, it's the sort of thing that will be brutally blocked by IT all over the place. Very slick, though.
Is it all that much more a risk than taking a screenshot, putting it on cloud storage like OneDrive/GDrive, and sharing with a "anyone who has the link" permission? B/c I feel like that is super common and kind of impossible to stop with a permissions approach.
When you take a screenshot, its contents are known and fixed.
When you regularly and automatically refresh a screenshot of a particular x/y coordinate part of a specific screen on a website, what happens when "positive customer interactions" gets moved, and "internal notes on this customer, not for sharing with them" gets put in that spot?
Very cool. How does Plus handle updating screenshots taken on authenticated pages once that authentication has expired?
(I'm an EM at Plus) It's a bit complex, and not quite perfect, but I'm pretty happy with what we've done so far. The first method is by looking at the HTTP status codes. Since we're running a full browser on our side, we can tell if the status codes that returned are different than the initial capture. We also have been training an image classification model on pictures of log-in screens — this has worked surprisingl…
This seems like a spectacular way to break permissions restrictions and escape data to non-authorized entities. If it's successful, it's the sort of thing that will be brutally blocked by IT all over the place. Very slick, though.
Is it all that much more a risk than taking a screenshot, putting it on cloud storage like OneDrive/GDrive, and sharing with a "anyone who has the link" permission? B/c I feel like that is super common and kind of impossible to stop with a permissions approach.
Earlier quoted context omitted.
?
The nice thing about this approach, to my mind, is that it can turn interactive interfaces and make them "read-only". It also seems like a pretty safe way to send data from behind your firewall.