• 0 Posts
  • 54 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle















  • I informed my SecOps team and they reached out to Slack. Slack posted an update:

    We’ve released the following response on X/Twitter/LinkedIn:

    To clarify, Slack has platform-level machine-learning models for things like channel and emoji recommendations and search results. And yes, customers can exclude their data from helping train those (non-generative) ML models. Customer data belongs to the customer. We do not build or train these models in such a way that they could learn, memorize, or be able to reproduce some part of customer data. Our privacy principles applicable to search, learning, and AI are available here: https://slack.com/trust/data-management/privacy-principles

    Slack AI – which is our generative AI experience natively built in Slack – is a separately purchased add-on that uses Large Language Models (LLMs) but does not train those LLMs on customer data. Because Slack AI hosts the models on its own infrastructure, your data remains in your control and exclusively for your organization’s use. It never leaves Slack’s trust boundary and no third parties, including the model vendor, will have access to it. You can read more about how we’ve built Slack AI to be secure and private here: https://slack.engineering/how-we-built-slack-ai-to-be-secure-and-private/


  • Because foss is usually not the easiest option. In fact it’s often quite difficult to maintain. So not only creating foss but then hosting your projects on foss is not tenable. Where does the line get drawn? OK you’re running forgejo. Are you running it on infrastructure that you control? You don’t control the DNS, you don’t control the ISP, you don’t control the fiber, you don’t control most of the stack. Putting something on GitHub is really inconsequential if you’re making your project open source since anyone can use it for anything anyway, so who controls the platform doesn’t matter in the slightest.