lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

66
active users

#Redis

0 posts0 participants0 posts today
📝 Nova publicação no blogue: Considerações sobre confusão de #Redis e licenças de software

🔗 https://blog.ayom.media/daltux/consideracoes-sobre-confusao-de-redis-e-licencas-de-software

🗞️ Texto redigido a partir da notícia de (mais um) relicenciamento de um sistema estruturante de muitas aplicações atuais — incluindo #Mastodon — 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 #jornalismo, da TI ou diversos.

#SoftwareLivre #AGPLv3 #notícias #jornalismo #tecnologia #BigTech #OpenSource #blog
daltux · Considerações sobre confusão de Redis e licenças de softwareHá notícia de que o projeto Redis — moderno sistema de banco de dados chave-valor largamente utilizado — passa a ter sua publicação regid...

You know, I literally was just going back and forth between redis and valkey the other day and settled on Redis. I don't think the SSPL preserves software freedom, but it seemed better than Amazon and Google's BSD-licensed stuff, which would be a walled-off, "take what you get or fork off" sort of environment. I genuinely had the thought "I wonder why the don't just go with the AGPL, that would be toxic enough to the likes of Amazon and Google".

...whaddayaknow.

redis.io/blog/agplv3/

I probably had this mental conversation with myself at the same time as these people were working on the final draft of this blog post.

wild.

Edit: also, releasing on #MayDay? 🔥

RE: fosstodon.org/@atoponce/114433

Redis · Redis is now available under the the OSI-approved AGPLv3 open source license.The rise of hyperscalers like AWS and GCP has unlocked incredible speed and scale for startups and enterprises alike. But for companies rooted in open source, it has posed a fundamental challenge: how do you keep innovating and investing in OSS projects when cloud providers reap the profits and control the infrastructure without proportional contributions […]
Replied in thread

L'estructura tècnica d'#appy funciona gràcies a Python, fastAPI, #Postgresql (base de dades) i #Redis (memòria cau).
Tot de manera asincrona per evitar punts de bloqueig, passen moltes coses en parall·lel, simultàniament, bàsic per a tenir fluïdesa tant en les interaccions amb altres servidors com amb les aplicacions client.
appy funciona bé fins i tot en una #Raspberry 4B, per tant també és una opció vàlida per a tenir el perfil fediversal auto gestionat i a casa.

What Happens to Relicensed #OpenSource Projects and Their Forks?
Contributor impact varies after projects adopt more restrictive licenses, finds Community Health Analytics in Open Source Software (CHAOSS) research on #Elasticsearch, #Redis, #Terraform and their forks.
So "Looking at all of these projects together, we see that the forks from relicensed projects tend to have more organizational diversity than the original projects," they conclude.
thenewstack.io/what-happens-to

The New Stack · What Happens to Relicensed Open Source Projects and Their Forks?Contributor impact varies after projects adopt more restrictive licenses, finds CHAOSS research on Elasticsearch, Redis, Terraform and their forks.
Continued thread

We were still struggling with email delivery from Forgejo. It looks like some queues are corrupted and restoring them is very hard. Most queued messages are spam or registration emails with already expired tokens. Finally, we made the decision to reset the queue and will do that in a few minutes.

We are using the opportunity to switch the queues to #redict / #redis, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).