Mastodon Chapril

0 message0 participant0 message aujourd’hui

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>

Giacomo Tesio<a href="https://mastodon.online/users/larsmb" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@larsmb@mastodon.online</a> Unfortunately, even <a href="https://snac.tesio.it?t=agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> is full of loopholes. Biggest one is being a different license than <a href="https://snac.tesio.it?t=gplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a>. That's basicaly why I use the <a href="https://snac.tesio.it?t=hackinglicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackingLicense</a> for my code: <a href="https://code.tesio.it/p/self-hosting/doh.cgi/file?name=LICENSE.txt&ci=tip" rel="nofollow noopener noreferrer" target="_blank">https://code.tesio.it/p/self-hosting/doh.cgi/file?name=LICENSE.txt&ci=tip</a> It's both a <a href="https://snac.tesio.it?t=copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> license and a shrink-wrap contract designed to close such loopholes. <a href="https://tldr.nettime.org/users/tante" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tante@tldr.nettime.org</a> <a href="https://social.vivaldi.net/users/lproven" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lproven@vivaldi.net</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>

Boud<a href="https://mastodon.ouvaton.coop/@ouvaton" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ouvaton</a> Je ne savais pas que le code source d'Overleaf soit sous l' <a href="https://framapiaf.org/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> . Ce qui implique que chaque instance doit de façon *évidente* informer ses utilisateurs de cela : "a convenient and prominently visible feature" [0]A coup d'oeil et par <a href="https://framapiaf.org/tags/SearXNG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SearXNG</a> j'ai l'impression qu'Overleaf.com viole grossièrement l' <a href="https://framapiaf.org/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> . La licence est hyper-cachée.<a href="https://framapiaf.org/tags/AGPLViolation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLViolation</a> <a href="https://framapiaf.org/tags/AGPLv3Compliance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3Compliance</a> [0] <a href="https://www.gnu.org/licenses/agpl-3.0.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.gnu.org/licenses/agpl-3.0.html</a> [1] <a href="https://www.overleaf.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.overleaf.com</a> [2] <a href="https://search.ononoki.org/search?q=overleaf+agpl" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://search.ononoki.org/search?q=overleaf+agpl</a> [3] <a href="https://search.ononoki.org/search?q=overleaf+affero" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://search.ononoki.org/search?q=overleaf+affero</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>?

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#agplv3