2 ms·
With the Slack integration, someone using `/giphy searchterm` will send over things like: slack enterprise ID, team ID, user ID, the team's domain, their name,
by ljm 5y ago
With the Slack integration, someone using `/giphy searchterm` will send over things like: slack enterprise ID, team ID, user ID, the team's domain, their name, the slack workspace's name, etc...
Facebook could quite easily use that data to draw more connections between people. Who they work with, who they might know within the same teams and enterprises, etc. etc.
- ec109685 5y agoNo, that's incorrect. The giphy command is created by Slack and doesn't share any data with Giphy [1]. [1] https://medium.com/delta-cx/facebook-bought-giphy-but-doesnt-really-care-how-you-use-gifs-26e99514e5e7 https://medium.com/delta-cx/facebook-bought-giphy-but-doesnt...
- crtasm 5y agoThat says "...designed to give Giphy nearly zero data.", unclear what is still shared. Signal goes to great lengths to preserve privacy with their giphy integration: https://signal.org/blog/signal-and-giphy-update/ https://signal.org/blog/signal-and-giphy-update/
- ljm 5y agoAnd at what point does FB use their considerable might to replace Slack's giphy bot with one that FB makes? The article basically says that Slack made a special case for Giphy, and so they decided that Giphy in particular doesn't get the same treatment as your typical slack bot or slash command. So, all FB needs to do is block that integration and either force their own or negotiate a new setup with slack. "You have a command called giphy and giphy is our trademark, so stop." The article you link to explains all of this, so I don't think you've refuted my point, really, except to say that it doesn't happen right now.