I’m honestly surprised that Slack doesn’t have some kind of steganographic watermarking so that leaked screenshots can be traced back to the original user, given how many big companies use it for all their internal comms.
-
I’m honestly surprised that Slack doesn’t have some kind of steganographic watermarking so that leaked screenshots can be traced back to the original user, given how many big companies use it for all their internal comms.
-
-
[email protected]replied to [email protected] last edited by
Even so, they're going find this guy fast. Just have to cross reference all the participants of leaked meetings
-
[email protected]replied to [email protected] last edited by
I see you don't use slack at work. Everyone is in every channel all the time for no reason. It's madness.
-
[email protected]replied to [email protected] last edited by
I did use slack; we had general channels with tons of people and smaller channels/meeting rooms with 5-30 people. If it was a 5-30 channel they can be found.
-
[email protected]replied to [email protected] last edited by
Christ I got added to this for college, such a mess of an app. Really difficult to follow what is what on it.
-
[email protected]replied to [email protected] last edited by
These companies can barely make the basics work on their apps, let alone all of this
-
[email protected]replied to [email protected] last edited by
It's really not. Depends on how your structure it I suppose
-
[email protected]replied to [email protected] last edited by
Only if that channel was private. You don't have to join a channel to be able to read its contents.
-
[email protected]replied to [email protected] last edited by
Oh what the fuck. I don't believe Teams is that way.
-
[email protected]replied to [email protected] last edited by
The reason is that it's great for collaboration and sharing info
-
[email protected]replied to [email protected] last edited by
Just one of the reasons that Teams is horrible to use!
-
[email protected]replied to [email protected] last edited by
There are public and private channels, simple as.
-
[email protected]replied to [email protected] last edited by
The techniques you're thinking of are for documents sent by email or some such. You add innocuous whitespace or typos that are unique to each one, and send them individually. If one leaks, you can match it to the employee who received it. That doesn't work for screenshots of Slack.
-
[email protected]replied to [email protected] last edited by
Well you could make it work, for example some random pattern in chat backgrounds that trace back to whoever is the user. That would still show up in a screenshot.
-
[email protected]replied to [email protected] last edited by
Slack or the OS would need to support it directly, and I don't think either of those have it.
-
[email protected]replied to [email protected] last edited by
True, but that's why the original comment seemed surprised, that a service like Slack doesn't have this given how many corporations use it.