Shakedown Social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> are something different...</li></ul>

Free Software FoundationCraig Topham, our Copyright & Licensing Associate, got together with the founder of <a href="https://hostux.social/tags/Abelujo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Abelujo</a>, a <a href="https://hostux.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> solution for managing <a href="https://hostux.social/tags/BookStores" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BookStores</a>. Read about Abelujo's backstory, uses, and future here: <a href="https://u.fsf.org/46d" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://u.fsf.org/46d</a> <a href="https://hostux.social/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://hostux.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>

Boud<a href="https://fediscience.org/@UlrikeHahn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@UlrikeHahn</a> As <a href="https://im-in.space/@Chip_Unicorn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Chip_Unicorn</a> says, Element = frontend. Org = New Vector Ltd. In terms of ethics (vs <a href="https://framapiaf.org/tags/TyrannyOfConvenience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TyrannyOfConvenience</a>) the main Matrix software is <a href="https://framapiaf.org/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> [1]; the protocol is open [2]; self-hosting is legal and ethical [3].As <a href="https://fedihum.org/@lavaeolus" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lavaeolus</a> says, security tends to oppose convenience: there's a learning curve for E2EE.I like <a href="https://framapiaf.org/tags/gomuks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gomuks</a> terminal; gomuks web is rapidly developing [4].[1] <a href="https://en.wikipedia.org/wiki/Element_%28software%29" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Element_%28software%29</a> [2] <a href="https://en.wikipedia.org/wiki/Matrix_%28protocol%29" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Matrix_%28protocol%29</a> [3] <a href="https://servers.joinmatrix.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://servers.joinmatrix.org</a> [4] <a href="https://github.com/tulir/gomuks" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/tulir/gomuks</a>

Preston Maness ☭<a href="https://sfconservancy.org/static/docs/sfc-neo4j-amicus-brief.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sfconservancy.org/static/docs/sfc-neo4j-amicus-brief.pdf</a>>A licensor is free to apply contradictory and self-defeating license terms to its software; the courts are not bound to save it from the consequences of that choice. > >... > >By stepping in to salvage Neon's catastrophic drafting, the district court is forced to adopt an interpretation that cannot be squared with the balance of the NSSL. > >... > >This court should not contort the text of this important license to preserve the interests of a single party who wielded it unwisely.The whole amicus brief is a good read, but damn there's some good sass towards the end XD This is the sort of legal work that makes the conservancy shine, and I hope that the conservancy keeps its members abreast of this case as it develops. Good work Aaron Williamson and good work Software Freedom Conservancy!<a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@conservancy</a> <a href="https://tenforward.social/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://tenforward.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://tenforward.social/tags/gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpl</a> <a href="https://tenforward.social/tags/agpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agpl</a> <a href="https://tenforward.social/tags/agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agplv3</a> <a href="https://tenforward.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://tenforward.social/tags/neo4j" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#neo4j</a>

Nicholas - ITSulu<a href="https://infosec.space/@kkarhan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kkarhan</a> <a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nixCraft</a> what are the issues with <a href="https://mastos.online/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> ?

Kevin Karhan :verified:<a href="https://mastos.online/@Nicholasr_ITSulu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Nicholasr_ITSulu</a> <a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nixCraft</a> nodds in agreement and since there are so many stakeholders with opposing interests and a <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> license, <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GAFAMs</a> can't <a href="https://infosec.space/tags/enshittify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#enshittify</a> or <a href="https://infosec.space/tags/tivolize" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tivolize</a> it!<ul><li>And due to <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2only</a> eben a move to <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a> like <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> or <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> is not possible!</li></ul>

Kevin Karhan :verified:<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GossiTheDog</a> consider putting all your content under <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>, <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> or even better <a href="https://infosec.space/tags/CCBYNCND" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCBYNCND</a>?

Tiago FGitHub - hoarder-app/hoarder: A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text searchUm aplicativo de favoritos auto-hospedável (links, notas e imagens) com marcação automática baseada em IA e pesquisa de texto completo<a href="https://github.com/hoarder-app/hoarder" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/hoarder-app/hoarder</a><a href="https://bolha.us/tags/agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agplv3</a> <a href="https://bolha.us/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://bolha.us/tags/codigoaberto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#codigoaberto</a> <a href="https://bolha.us/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a>

Kevin Karhan :verified:<a href="https://chaos.social/@frumble" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@frumble</a> <a href="https://exquisite.social/@thomholwerda" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thomholwerda</a> ja, <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> hat auch wieder Probleme.<ul><li>Ideal wäre <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> (wenn nicht sogar <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#0BSD</a>) weil GPLv3 ist mit <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> inkompatibel und daher für alles was nicht ebenfalls <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> oder <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> ist inkompatibel!</li></ul>

Kevin Karhan :verified:One can really see <a href="https://www.youtube.com/watch?v=4hZxo96x48A&t=4m15s" rel="nofollow noopener noreferrer" target="_blank">this</a> is an older video, as it misses not only <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#0BSD</a> between <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PublicDomain</a> and <a href="https://infosec.space/tags/MIT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MIT</a> but also <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> right of <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> in a tab that's right of it called "<a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a>" or "<a href="https://infosec.space/tags/Monopolistic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Monopolistic</a>" or just "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a>" and a tab right of that for "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a>" licensing, but I get ahead of myself...<a href="https://infosec.space/tags/Sarcasm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sarcasm</a> <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Licensing</a> <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> <a href="https://infosec.space/tags/Cipyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cipyright</a> <a href="https://infosec.space/tags/Copywrong" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copywrong</a> <a href="https://infosec.space/tags/rant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rant</a> <a href="https://infosec.space/tags/vent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vent</a> <a href="https://infosec.space/tags/venting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#venting</a>

Kevin Karhan :verified:<a href="https://ma.fellr.net/@fell" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fell</a> <a href="https://mastodon.xyz/@Liberapay" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Liberapay</a> <a href="https://mastodon.opencollective.com/@opencollective" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opencollective</a> also considering how the main Server & Client for <a href="https://infosec.space/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> is "asshole-licensed" under <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> I'd rather setup <a href="https://fosstodon.org/@zulip" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zulip</a> & <a href="https://lemmy.world/c/jitsimeetinstances" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jitsimeetinstances</a> / <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JitsiMeet</a>.

Kevin Karhan :verified:<a href="https://social.sdf.org/@pfr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pfr</a> <a href="https://hachyderm.io/@lucasmz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lucasmz</a> to me, <a href="https://infosec.space/tags/matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#matrix</a> is a shittier implementation of <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a>-<a href="https://infosec.space/tags/Conferencing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Conferencing</a> and since it's main implememntations are under a sort-of "<a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicense</a>" that is <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> it'll inevitably die out quickly when there are better options like <a href="https://fosstodon.org/@zulip" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zulip</a> / <a href="https://infosec.space/tags/Zulip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zulip</a> for most use-cases.

Kevin Karhan :verified:<a href="https://babka.social/@serge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@serge</a> yeah, <a href="https://infosec.space/tags/RMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RMS</a> is a cringy "FLOSS extremist" in the worst sense of it, because he started hating <a href="https://infosec.space/tags/OLPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OLPC</a> for merely making it possible to put <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> on the <a href="https://infosec.space/tags/XO1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XO1</a>.<ul><li>Not delivering it with it even as a BTO option, but merely offering <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#drivers</a>.</li></ul>And for him everythng that isn't <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> or <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> isn't <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> to him, with his fanboys getting caught harrassing projects to "switch to GPLv3" for no reason.

Kevin Karhan :verified:<a href="https://tech.lgbt/@celestia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@celestia</a> nodds in agreementI do think that you as maintainer should've the right to choose the license of your works as you see fit, regardless if <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>, <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a>, <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#0BSD</a> or whatever you like.<ul><li>If they don't like that they can happily start their own (like <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> did with <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toybox</a>)...</li></ul>Personally, I have both stuff under GPLv3 (i.e. <a href="https://infosec.space/tags/NUCbook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NUCbook</a>), <a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@creativecommons</a> <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCBYNCSA</a> (i.e. <a href="https://infosec.space/tags/ListsD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ListsD</a>) and 0BSD (i.e. <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a>) for good reasons, and whilst I'd not choose MPL, I'd fight for YOUR RIGHT to choose that (or even <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>) as a <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> as a matter if freedom!

Kevin Karhan :verified:<a href="https://fosstodon.org/@carlwgeorge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@carlwgeorge</a> <a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vermaden</a> <a href="https://fosstodon.org/@samurro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@samurro</a> <a href="https://mastodon.bsd.cafe/@tara" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tara</a> <a href="https://linuxmom.net/@vkc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vkc</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> TBH, being just marginally better than <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Oracle</a> and <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> is the only reason I'd use <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHEL</a> over <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solaris</a> or god forbid <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a>, tho I'm glad <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> isn't controlled entirely by <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> and that I can use <a href="https://infosec.space/tags/OpenSUSE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSUSE</a> and <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UbuntuLTS</a> and their parent companies didn't gave me or my (fmr.) clients/employers the finger... But hey, go keep <a href="https://fosstodon.org/@carlwgeorge/113066753513420985" rel="nofollow noopener noreferrer" target="_blank">lying to yourself</a> with the corporate propaganda of <a href="https://fosstodon.org/@carlwgeorge/113066740483764069" rel="nofollow noopener noreferrer" target="_blank">open source sustainability</a> because if you think that <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> needs to be <a href="https://infosec.space/tags/profitable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#profitable</a> you haven't understood why people choose <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> licenses like the <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2</a> and espechally <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> and how Red Hat is providing arguments to push for "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a>" a la <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>.Your <a href="https://fosstodon.org/@carlwgeorge/113066777245682297" rel="nofollow noopener noreferrer" target="_blank">dismissals</a> of criticism are childish and your way to flood my notifications with bs replies just to then flee the discussion like a coward is a really bad way to <a href="https://fosstodon.org/@carlwgeorge/113066796196131707" rel="nofollow noopener noreferrer" target="_blank">pull rank</a>.<ul><li>This behaviour reminds me of "channers" that refexively reply "You have an anime pfp, your opinion doesn't matter!" as if that's a way to engage with potential clients!</li></ul>Just because I'm not a CxO doesn't mean I know how to (dis-)recommend suppliers and underpin that with past experiences, as clients/employers trust in my judgement.

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@marcan</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> Either way, like <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> I did the <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#0BSD</a> as a <a href="https://infosec.space/tags/PermissiveLicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PermissiveLicense</a> (cuz <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PublicDomain</a> legally doesn't exist in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Germany</a>: One cannot renounce <a href="https://infosec.space/tags/Authorship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authorship</a> for legal reasons, otherwise <a href="https://infosec.space/tags/HateSpeech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HateSpeech</a> would be unprosecute-able, so only <a href="https://infosec.space/tags/Copyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyright</a> lapses 70 years post-mortem of the Authors)...<ul><li>I think "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a>" like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> is inherently unfree and <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> is just an act of committing <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> which doesn't work.</li></ul>TBH, the only way to preven <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GAFAMs</a> <a href="https://youtu.be/ZzI9JE0i6Lc" rel="nofollow noopener noreferrer" target="_blank">like Amazon</a> from leeching <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> is to either make <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> or offer the superior [<a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaaS</a>] solution by ticking boxes <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> can't ( i.e. due to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a>, like <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDPR</a> compliance) or inherently won't hecause it's antithetical to their business ( i.e. [airgapped] <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a> & Support/Management Options for self-hosted systems)...<ul><li> <a href="https://infosec.space/tags/healthcare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthcare</a>-IT based startups in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a> pay Companies like <a href="https://infosec.space/tags/Telekom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Telekom</a> to host their medical data because unlike <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a> they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies and if one butters them with enough money, they'll likely sign the hardest NDAs one can throw at them...</li></ul>

Kevin Karhan :verified:<a href="https://groupe-tazor.com/@Yuki" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Yuki</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a> as illuded by <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a>, <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> is just toxic and I'd consider it just legally less evil than <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicense</a>|s like <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> & <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>, cuz they are worse than <a href="https://infosec.space/tags/CCBYNCND" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCBYNCND</a> and <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCBYNCSA</a> for many cases...And yes, I solely used <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> and <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCBYNCSA</a> as a form of <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> in case someone points at my GitHub - I know that!<a href="https://infosec.space/@kkarhan/112134853241787929" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.space/@kkarhan/112134853241787929</a>

Matt "msw" WilsonIf licenses like the "Server Side Public License" (SSPL) move the Overton Window so that folks see that AGPLv3 is not as "scary" as some proprietary software vendors made it out to be, maybe introducing it to the public has done some SMALL service to the Free Software movement.<a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mstdn.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://mstdn.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://mstdn.social/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> <a href="https://mstdn.social/tags/SoftwareFreedom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareFreedom</a> <a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>

Matt "msw" WilsonPersonally it's still surprising to me that, as a case study, MongoDB is not primarily highlighted as an example of a firm that used the brand goodwill of "Open Source" as a way to implement a "Freemium" GTM strategy by choosing the most misunderstood and feared <a href="https://mstdn.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> license (<a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>), then invented a new license that had a cloaked field-of-use restriction (or "constructive restriction" as <a href="https://meshed.cloud/@webmink" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@webmink</a> calls it), attempting to warp the definition of <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a><a href="https://mstdn.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://mstdn.social/tags/SoftwareFreedom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareFreedom</a> <a href="https://mstdn.social/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a>

Kevin Karhan :verified:<a href="https://mckellar.social/@ian" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ian</a> The problem with all existing <a href="https://mstdn.social/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> licenses is that they don't force those that take something to publish back their modifications.<a href="https://mstdn.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> and <a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> didn't really fix that either...

Recent searches

Search options

Administered by:

Server stats:

#agplv3