Med-Mastodon

0 posts0 participants0 posts today

Brian Greenberg :verified:⚠️ Legal alert: Broadcom is issuing cease-and-desist letters to VMware perpetual-license users 🚨📄 Perpetual-license agreements deemed non-compliant 🛑 Users must migrate to subscriptions or face legal action 🔒 Broadcom cites IP infringement and support violations 💡 Action: Audit your license status and plan your upgrade path now<a href="https://infosec.exchange/tags/VMware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VMware</a> <a href="https://infosec.exchange/tags/Broadcom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Broadcom</a> <a href="https://infosec.exchange/tags/Compliance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compliance</a> <a href="https://infosec.exchange/tags/ITsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITsecurity</a> <a href="https://infosec.exchange/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a> <a href="https://arstechnica.com/gadgets/2025/05/broadcom-sends-cease-and-desist-letters-to-subscription-less-vmware-users/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/gadgets/2025/05/broadcom-sends-cease-and-desist-letters-to-subscription-less-vmware-users/</a>

Michel Lind :fedora: :debian:If someone were to create a license that matches free/libre/open source licenses out there, but stipulates that any <a href="https://hachyderm.io/tags/scraping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scraping</a> by <a href="https://hachyderm.io/tags/GenAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GenAI</a> bots must be pre-approved and throttled - would <a href="https://hostux.social/@fsf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fsf</a> and <a href="https://social.opensource.org/@osi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osi</a> consider this free / open source? And if so, would FSF or <a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@conservancy</a> be able to enforce the terms against violators?Now to think about it maybe the first step is a shared blocklist of AI scrapers' IP ranges. If it ends up blocking cloud providers so be it<a href="https://hachyderm.io/tags/DDOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDOS</a> <a href="https://hachyderm.io/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a>

Ben BuhseSo what exactly constitutes "prominent notices stating that you modified it, and giving a relevant date" for <a href="https://hachyderm.io/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> code? For example, I'm working on a personal project and writing licensing it under the GPLv3. If I want to take and modify a single function (or a few) from another GPLv3-licened projected, how do I state the modifications and the date? Do git commits count? What exactly do I need to do?<a href="https://hachyderm.io/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://hachyderm.io/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> <a href="https://hachyderm.io/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a>

jonny (good kind)Ok <a href="https://neuromatch.social/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a> question: we have some software to interface with an <a href="https://neuromatch.social/tags/FPGA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FPGA</a> which uses the manufacturers USB python code. We want to release our code as an open source package (its currently GPL-3, but thats just my default), but it has this license: <a href="https://opalkelly.com/about-us/frontpanel-license/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://opalkelly.com/about-us/frontpanel-license/</a><blockquote>Opal Kelly hereby grants to the Licensee a temporary, non-exclusive license to install and use Software. Licensee shall not modify, distribute, resell or otherwise transfer Software for any purpose, commercial or non-commercial. Licensee may integrate and sub-license Software for distribution but Software must only be used in conjunction with Opal Kelly devices or devices incorporating Firmware.</blockquote>That to me says two opposite things: a) we are not allowed to distribute it for any purpose, and also b) we may sub-license and distribute it if we use it with their hardware (we are)Is this a normal thing in <a href="https://neuromatch.social/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embedded</a> world? Can we just... copy and paste it into a <code>vendor</code> folder and call it a day, or do we need to redesign this thing?

Rick Moen 🇺🇸 🇳🇴 🇬🇧<a href="https://sy.nthia.dev/users/hack" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hack</a> , I've been using a "license where you're not allowed to attribute the original author and must pretend that you wrote it yourself" (of a sort) on a non-software work, my personal FAQ (<a href="http://linuxmafia.com/~rick/faq/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://linuxmafia.com/~rick/faq/</a>), for decades. I wanted to permit either verbatim replication with attribution, preserving my views intact, or unrestricted CC-style remixing and morphing of my personal views but with blowback towards me from third-party changes averted by the altered work being required to be asserted to be someone else's. So, the wording is:"Copyright (C) 1995-2023 by Rick Moen. Verbatim copying, distribution, and display of this entire article (page) are permitted in any medium, provided this notice is preserved. Alternatively, you may create derivative works of any sort for any purpose, provided your versions contain no attribution to me, and that you assert your own authorship (and not mine) in every practical medium."<a href="https://federate.social/@dmarti" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://federate.social/@dmarti</a> described this licence (when I concocted it in the '90s), as "bastard reverse copyleft", and wisely cautioned about legal uncertainties owing to its novelty. (/me nods to <a href="https://teh.entar.net/@spacehobo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://teh.entar.net/@spacehobo</a>)<a href="https://infosec.exchange/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a> <a href="https://infosec.exchange/tags/CreativeCommons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CreativeCommons</a> <a href="https://infosec.exchange/tags/OpenSourceSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSourceSoftware</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/copyfight" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyfight</a> <a href="https://infosec.exchange/tags/SillyGeekTricks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SillyGeekTricks</a>

Strypey"[Bruce Perens'] specific vision of a tidy open source license catalog probably differs from mine. But I’d like to set out my thinking.In short: one permissive license, with optional credit, plus three copyleft licenses—consistent, selective, and historical—likewise with optional credit."<a href="https://mastodon.nzoss.nz/tags/KyleEMitchell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KyleEMitchell</a><a href="https://writing.kemitchell.com/2019/03/17/License-Utopia" rel="nofollow noopener noreferrer" target="_blank">https://writing.kemitchell.com/2019/03/17/License-Utopia</a><a href="https://mastodon.nzoss.nz/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mastodon.nzoss.nz/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a> <a href="https://mastodon.nzoss.nz/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a>

Max Planck Digital Library💡 Did you know... <a href="https://social.mpdl.mpg.de/tags/mpdlservices" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mpdlservices</a> <a href="https://social.mpdl.mpg.de/tags/mpdl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mpdl</a> <a href="https://social.mpdl.mpg.de/tags/softwarelicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softwarelicensing</a> 🌐 <a href="https://www.soli.mpdl.mpg.de/en/software/" rel="nofollow noopener noreferrer" target="_blank">https://www.soli.mpdl.mpg.de/en/software/</a>

Jan Lehnardt 🛋️I used to know this, but my brain seems to have shed all knowledge, and I’m sorry to bring this up even ;D — But can you help out:If software X (MIT License) uses a dependency Y (AGPL), and vendor Z makes changes to X and runs them as a server but uses Y as-is, does X count as “based on” Y and do the changes have to be releases as AGPL? <a href="https://chaos.social/tags/gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpl</a> <a href="https://chaos.social/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLicensing</a>

Recent searches

Search options

Administered by:

Server stats:

#softwarelicensing