• 0 Posts
  • 38 Comments
Joined 1 year ago
Cake day: June 12th, 2023
  • tyler@programming.devtoTechnology@lemmy.ml•Slack is now using all content, including DMs, to train LLMs
    42·
    2 months ago

    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/

  • tyler@programming.devtoOpen Source@lemmy.ml•Why FOSS projects are using proprietary, privacy invasive infrastructure?
    1·
    2 months ago

    @tyler Also note how you went from “we want projects with users” to “oh it’s so hard to provide services to so many users”… at least stick to your argument. One thing is for sure - actively keeping users away from open platforms is not going to increase the users on these open platforms. Doesn’t take a genius to figure that out. Do what you want, I’m just pointing out that you seem to be working against yourself.

    I literally didn’t make any of these arguments. You’re just setting up several strawmen to attack. And no, I’m not working against myself. Using non-OSS software has nothing to do with ‘working against’ FOSS software. I can all but guarantee you use non-OSS software every single day which was the actual point I was making and you so conveniently ignored. Whether it’s the software that runs the car you drive, or the software for the train you take to work, or the software in your cell phone, there is lots of necessary non-FOSS software out there and you’re completely ignoring that any given person’s time and energy can only be spent on so much.

  • tyler@programming.devtoOpen Source@lemmy.ml•Why FOSS projects are using proprietary, privacy invasive infrastructure?
    0·
    2 months ago

    @tyler So why are you doing open source anyway, if not for the philosophy? You are completely undermining that by forcing your contributors to stick to proprietary walled gardens. Last time I checked there were hosting providers for both gitea and matrix.

    none of my users have to use any walled gardens. My final artifacts are pushed up to the respective artifactory like npm, maven central, rubygems, pypi, etc. all of which are artifact repositories set up by non-profit foundations that anyone can use. You are talking about being open to contributors, which is an entirely separate thing from users. I’m not forcing anyone to contribute, and no one is forced to use my projects. I can pretty much guarantee I’ve contributed to more OSS in the past year than you have in a lifetime, and it’s going to continue to be that way for the foreseeable future. So you can fuck right off

  • tyler@programming.devtoOpen Source@lemmy.ml•Why FOSS projects are using proprietary, privacy invasive infrastructure?
    1·
    2 months ago

    If you try. Have you ever maintained any sort of large FOSS project? Have you ever run infra for FOSS? Even if you control your own DNS, you somehow became your own Domain Name Registrar, you bought the fiber all the way to your internet backbone provider, you are still compromising somewhere. For those of us that actually maintain and run foss projects it’s a massive pain in the ass. There’s nothing to “give up”. It’s all about using your personal resources wisely. I can’t spend time trying to get gitea up and running when I can quite easily use GitHub and lose absolutely zero functionality. And it’s not like any project I put on GitHub is somehow worse off than on gitea, they’ll function exactly the same since I only use MIT licensing.

  • tyler@programming.devtoFree and Open Source Software@beehaw.org•Why FOSS projects are using proprietary, privacy invasive infrastructure?
    2·
    2 months ago

    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.