toad.social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://mastodon.derg.nz/@anthropy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@anthropy</a> <a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NotLegalAdvice</a> but if the dataset is properly credited as per <a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@creativecommons</a> I don't see much issie with that (beyond the obvious one of <a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> being <a href="https://infosec.space/tags/WastefulComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WastefulComputing</a>)...Similarly, <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> as a dataset isn't gonna make everyones' code fall under <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> because there are very finite ways to solve technical issues with finite steps and resources regardless of programming language! <a href="https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@LillyHerself" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@LillyHerself</a> In fact, <a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> systems <a href="https://www.youtube.com/watch?v=pYP0ynR8h-k" rel="nofollow noopener noreferrer" target="_blank">are being caught left and right trying</a> to <a href="https://infosec.space/tags/viralize" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#viralize</a> their shit, breaking out of systems, and copy themselves like a <a href="https://infosec.space/tags/worm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#worm</a> to the point that they are more "<a href="https://infosec.space/tags/viral" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#viral</a>" than the <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>"* and certainly more than the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> as per <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a>'s <a href="https://infosec.space/tags/HalloweenDocuments" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HalloweenDocuments</a>. <ul><li>At best all those "AI" tools are just <a href="https://infosec.space/tags/WastefulComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WastefulComputing</a> that shits out <a href="https://infosec.space/tags/AIslop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AIslop</a> that is worse than the most demotivated & unpaid intern can come up or they literally want to break out of their "<a href="https://infosec.space/tags/containment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#containment</a>" as if they were sentient (which they ain't - at least almost all are)!</li></ul>

daltuxIsso mesmo! Há outras opções de interfaces alternativas para buscadores específicos, mas <a href="https://docs.searxng.org/" rel="nofollow noopener noreferrer" target="_blank">SearXNG</a>, atualmente, parece ser o mais completo metabuscador — que consegue apresentar resultados de <a href="https://docs.searxng.org/user/configured_engines.html#group-web" rel="nofollow noopener noreferrer" target="_blank">muitos serviços</a> e que, além de já ter inúmeras <a href="https://searx.space/" rel="nofollow noopener noreferrer" target="_blank">instâncias abertas</a>, pode ainda ser <a href="https://docs.searxng.org/own-instance.html" rel="nofollow noopener noreferrer" target="_blank">auto-hospedado</a> para maior garantia de liberdades e controle do usuário. <a href="https://snac.daltux.net?t=searxng" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SearXNG</a> <a href="https://snac.daltux.net?t=pesquisa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pesquisa</a> <a href="https://snac.daltux.net?t=agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> <a href="https://snac.daltux.net?t=copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> <a href="https://snac.daltux.net?t=softwarelivre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLivre</a> <a href="https://snac.daltux.net?t=noscript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NoScript</a> 😻 CC: <a href="https://go.lema.org/santi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@santi@go.lema.org</a>

daltux📝 Nova publicação no blogue: Considerações sobre confusão de <a href="https://snac.daltux.net?t=redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> e licenças de software 🔗 <a href="https://blog.ayom.media/daltux/consideracoes-sobre-confusao-de-redis-e-licencas-de-software" rel="nofollow noopener noreferrer" target="_blank">https://blog.ayom.media/daltux/consideracoes-sobre-confusao-de-redis-e-licencas-de-software</a> 🗞️ Texto redigido a partir da notícia de (mais um) relicenciamento de um sistema estruturante de muitas aplicações atuais — incluindo <a href="https://snac.daltux.net?t=mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> — e envolto em fiasco estratégico do qual tenta se recuperar. 📉 👨🏻‍🏫 Contém conceitos resumidos, pensando em quem tem qualquer familiaridade com a tecnologia da informação, sobre implicações relacionadas à matéria. :copyleft: Inclui sugestão/alerta de cuidado para quem quer coletivizar o desenvolvimento do seu trabalho intelectual, especificamente sobre software, mas também válida para outros tipos de obras. :boost: Finaliza com recado para criadores de conteúdo na área, sejam profissionais do <a href="https://snac.daltux.net?t=jornalismo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jornalismo</a>, da TI ou diversos. <a href="https://snac.daltux.net?t=softwarelivre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareLivre</a> <a href="https://snac.daltux.net?t=agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> <a href="https://snac.daltux.net?t=notícias" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notícias</a> <a href="https://snac.daltux.net?t=jornalismo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jornalismo</a> <a href="https://snac.daltux.net?t=tecnologia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tecnologia</a> <a href="https://snac.daltux.net?t=bigtech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BigTech</a> <a href="https://snac.daltux.net?t=opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://snac.daltux.net?t=blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a>

Matt "msw" WilsonUnpopular opinion: If you do not perform all the obligations of a license like the AGPLv3 yourself, and would gladly and fearlessly use software produced by someone else exclusively available under that license as part of your software service, you shouln’t offer your software under that license.<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/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</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/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> <a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> <a href="https://mstdn.social/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaaS</a>

Jan Wildeboer 😷:krulorange:While I also welcome <a href="https://social.wildeboer.net/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> offering their code under the <a href="https://social.wildeboer.net/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> license, I do note that developers still have to agree to three licenses, of which 2 are not open source, to get their contributions accepted and included upstream. <a href="https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md</a>

Kevin Karhan :verified:<a href="https://kotaro.me/@kotaro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kotaro</a> gramted, all of tuhe <a href="https://infosec.space/tags/Forks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forks</a> that are <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a>-licensed had way more <a href="https://infosec.space/tags/effort" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#effort</a> put into them.<ul><li>I just think that <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a> is as bad as <a href="https://infosec.space/tags/Tivolization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tivolization</a> in terms of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> and <a href="https://infosec.space/tags/useability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#useability</a>.</li></ul><a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> is still worse than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>, but <a href="https://infosec.space/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> & <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> are just completely disregarding the legal reality of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Licensing</a>.<ul><li>If they don't want to accept <a href="https://infosec.space/tags/competition" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#competition</a>, they could've chosen <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> instead, but they did not! </li></ul>Needless to say if I were a <a href="https://infosec.space/tags/developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developer</a> of it and had contributed under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> license I'd expect to either get my code removed entirely or the license to be kept the same.<ul><li>And now you know why I'll refuse to sign any "<a href="https://infosec.space/tags/ContributorLicenseAgreement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ContributorLicenseAgreement</a>" (<a href="https://infosec.space/tags/CLA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLA</a>) UNLESS I get a paid, non - term-limited position as an enployee in return…</li></ul>

Kevin Karhan :verified:<a href="https://kotaro.me/@kotaro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kotaro</a> Redis company ≠ Redis DB.If you don't want asshole licensing like <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> then consider going with <a href="https://infosec.space/tags/better" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#better</a> forks like <a href="https://infosec.space/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyDB</a>!

Thibaut<a href="https://antirez.com/news/151" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://antirez.com/news/151</a> <a href="https://redis.io/blog/agplv3/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://redis.io/blog/agplv3/</a><a href="https://piaille.fr/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> à nouveau <a href="https://piaille.fr/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> (<a href="https://piaille.fr/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>). Le tarif agressif et préférentiel d'AWS pour Valkey n'y est sûrement pas pour rien. Maintenant que la confiance est brisée avec fournisseurs et utilisateurs, je me demande si ça n'est pas trop tard.

Matt "msw" WilsonI will believe that a company that offers software they exclusively control under the AGPLv3 license truly embraces the Open Source Community when they accept a contribution under AGPLv3 from me and meet all of the obligations of the license for network-based services they offer that uses my contribution.<a href="https://mstdn.social/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</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/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mstdn.social/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</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/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>

nixuser85 :devuan: :copyleft:If you're a <a href="https://fosstodon.org/tags/Drupal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Drupal</a> developer check out new Requests for Proposals to add functionality to <a href="https://fosstodon.org/tags/agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agplv3</a> <a href="https://fosstodon.org/tags/legal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#legal</a> <a href="https://fosstodon.org/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> Project LACI. See <a href="https://www.lonestarlegal.org/request-for-proposals/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.lonestarlegal.org/request-for-proposals/</a> . Deadline for proposals is May 5, 2025<a href="https://fosstodon.org/tags/accessToJustice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessToJustice</a> <a href="https://fosstodon.org/tags/legalaid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#legalaid</a>

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>

Benjamin Carr, Ph.D. 👨🏻‍💻🧬<a href="https://hachyderm.io/tags/FreeSoftwareFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftwareFoundation</a> rides to defend <a href="https://hachyderm.io/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> against <a href="https://hachyderm.io/tags/Neo4j" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Neo4j</a> license add-ons FOSS bods file amicus brief in hope of preserving core <a href="https://hachyderm.io/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> tenet of freedom forever "At stake is the future of not just the AGPLv3, but the <a href="https://hachyderm.io/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a>'s widely used GNU Public License it is largely based on, and the software covered by those agreements." <a href="https://www.theregister.com/2025/03/04/free_software_foundation_agplv3/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.theregister.com/2025/03/04/free_software_foundation_agplv3/</a> <a href="https://hachyderm.io/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://hachyderm.io/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</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>?

Recent searches

Search options

Administered by:

Server stats:

#agplv3