social.bund.de

0 posts0 participants0 posts today

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>

thomas<a href="https://social.bund.de/@BKG" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BKG</a> Anscheined ist das Softwaremodul <a href="https://muenchen.social/tags/SSR2OBS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSR2OBS</a> zentral für die Anwendung. Gibt es Pläne, das zum allgemeinen Download zur Verfügung zu stellen? Noch besser, als <a href="https://muenchen.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>? Dual-Licensing mit einer restriktiven Copyleft-Lizenz wie <a href="https://muenchen.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> wäre für Hobbyanwender und Forschung völlig ausreichend.

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://mastodon.social/@pid_eins" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pid_eins</a> Speaking of valid criticism: The <a href="https://infosec.space/tags/Stallmanists" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stallmanists</a> and "<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> Fanboys" are a literal net negative as their nonchalant attitude about bricking userspace with minor updates, and complete disregard to the fact that not everything is <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>-compatible <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> but that <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> also exists and thus "just recompile it!" is not an option, showed me.It's the reason why I demand everything to be statically linked binaries in <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a>, because I think people should also "own" the dependencies and take responsibility.<ul><li>Ideally this would push developers to building lean, clean and well-maintained as well as -maintainable applications.</li></ul>

Lionel JeanneratAvec une relative discrétion, nous développons un <a href="https://tooting.ch/tags/logiciellibre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#logiciellibre</a> pour facilement lancer son site auto-hébergé de e-shop et crowdfunding. Il est déjà fonctionnel en alpha 🔥.Il a été financé par la Confédération 🇨🇭 et le canton :ch_Neuchatel: via le prog. NPR. <a href="https://social.admin.ch/@gov" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gov</a>Les 1ères boutiques, ainsi que le code sous <a href="https://tooting.ch/tags/agplv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#agplv3</a>, seront présentés en jan 24. Il y aura la Bookinerie de <a href="https://re.lire.im/@pvheditions" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pvheditions</a> qui mettra en valeur ses livres sous <a href="https://tooting.ch/tags/ccbysa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ccbysa</a> <a href="https://tooting.ch/tags/artlibre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#artlibre</a>. :cc: :ccby: :cc_sa: <a href="https://tooting.ch/tags/mastolivre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastolivre</a>Je me réjouis.

Kevin Karhan :verified:<a href="https://postchat.io/@JustinLachance" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@JustinLachance</a> <a href="https://hci.social/@tod" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tod</a> It's called "Formulating a <a href="https://mstdn.social/tags/NuancedOpinion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NuancedOpinion</a>" and I can highly recommend it. It's way more complex but it allows for some consistent yet realistic approaches.I.e. one can acknowledge that <a href="https://mstdn.social/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> and <a href="https://mstdn.social/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> showed the need for stronger <a href="https://mstdn.social/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> whilst also noting that neither <a href="https://mstdn.social/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> nor <a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> nor <a href="https://mstdn.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> doesn't adress that problem and instead demand illegal actions to comply [i.e. surrendering all patents] which ignore the reality of <a href="https://mstdn.social/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a>. <a href="https://postchat.io/@JustinLachance/110907574633552171" rel="nofollow noopener noreferrer" target="_blank">https://postchat.io/@JustinLachance/110907574633552171</a>

Flous :gnome: :debian:<a href="https://fosstodon.org/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> is the most protective of computer user freedom. Use it on source code repository services like <a href="https://fosstodon.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> or <a href="https://fosstodon.org/tags/GitLlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLlab</a> to future-proof your rights.

Boud<a href="https://mastodon.social/@angdraug" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@angdraug</a> <a href="https://mastodon.technology/@rysiek" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rysiek</a> <a href="https://toot.aquilenet.fr/@civodul" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@civodul</a>Does the GNU Affero General Publice License v3 <a href="https://framapiaf.org/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> for software package S *require* that a web service W running S provide a facility for user U of the S on W to export his/her user-created *content* from server W to local files?[My guess is "no". In which case if U gets tired of W (or W closes down, changes ToS, whatever), then U can start a new service running S, but may have to recreate the content from scratch (or html scrapes).]<a href="https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License</a>

Recent searches

Search options

Administered by:

Server stats:

#agplv3