Earlier quoted context omitted.
squarely in the former camp. there's something deeply abhorrent about creating a place that encourages people to share and build and collaborate, then turning around and using their creative output to put more money in shareholder pockets. i deleted my reddit and github accounts when they decided the millions of dollars per month they're receiving from their users wasn't enough. don't have the power to move our shop…
Yeah I haven't put a new codebease on GH in years. It's kind of a PITA hosting my own gitea server for personal projects but letting MS copy my work to help make my professional skillset less valuable is far less palatable. Companies doing this would make me much less angry if they used an opt-in model only for future data. I didn't have a crystal ball and I don't have a time machine, so I simply can't stop these com…
Slack AI Training with Customer Data
351–360 of 426 posts
Re: Slack AI Training with Customer Data
#352This is as systemically concerning as the data practices seen on Discord with integrations like statbot.net, though at least Slack is being transparent about it. Regardless, I find all of this highly problematic.
And this is just one of many, many problems associated with the platform.
Re: Slack AI Training with Customer Data
#353Re: Slack AI Training with Customer Data
#354Earlier quoted context omitted.
That's exactly my point. "File over app"[1] is just as relevant for businesses as it is for individuals — if you don't want your data to be used for training, then take sovereignty of it. [1] https://stephango.com/file-over-app
"File over app" is a good way of putting it! Something strange is happening on your blog, fwiw: Bookmarking it via command + D flips the color scheme to "night mode" – is that intentional?
Re: Slack AI Training with Customer Data
#355Re: Slack AI Training with Customer Data
#356Re: Slack AI Training with Customer Data
#357Earlier quoted context omitted.
Yeah I haven't put a new codebease on GH in years. It's kind of a PITA hosting my own gitea server for personal projects but letting MS copy my work to help make my professional skillset less valuable is far less palatable. Companies doing this would make me much less angry if they used an opt-in model only for future data. I didn't have a crystal ball and I don't have a time machine, so I simply can't stop these com…
Why do you think it's a pain to host the Gitea?
Hosting my own service rather than using a free SaaS solution that is entirely someone else's problem? There's a significant difference there. I've been running Linux servers either professionally or personally for almost 25 years, so it's not like it's a giant problem... but my work has been increasingly non-technical over the past 5 years or so, so even minor hiccups require re-acclimating myself to the requisite constructs and tools (wait, how do cron time patterns work? How do I test a variable in bash for this one-liner? How do iptables rules work again?)
It's not a deal breaker, but given the context, it's definitely not not a pain in the ass, either.
Re: Slack AI Training with Customer Data
#358> We offer Customers a choice around these practices. If you want to exclude your Customer Data from helping train Slack global models, you can opt out. If you opt out, Customer Data on your workspace will only be used to improve the experience on your own workspace and you will still enjoy all of the benefits of our globally trained AI/ML models without contributing to the underlying models. Why would anyone not opt…
Whats baffling to me is why companies think that when they slap AI on the press release, their customers will suddenly be perfectly fine with them scraping and monetizing all of their data on an industrial scale, without even asking for permission. In a paid service. Where the service is private communication.
Monetizing on user activity data through opt-out collection is not new. Pretending that his phenomenon has anything to do with AI seems like a play for attention that exploits peoples AI fears.
I'll sandwich my comments with a reminder that I am not pro-exploiting users' ignorance for their data.