Social 📸 Photography

Kazuky Akayashi ฅ^•ﻌ•^ฅBon ... 🤬 y a des fedigens sous Debian 12 qui ont installer Valkey qui est censé d'après leur doc être dans les dépôts :blobPikaFacepaw: <a href="https://social.zarchbox.fr/tags/Valkey" rel="nofollow noopener" target="_blank">#Valkey</a> <a href="https://social.zarchbox.fr/tags/Redis" rel="nofollow noopener" target="_blank">#Redis</a> <a href="https://social.zarchbox.fr/tags/Debian" rel="nofollow noopener" target="_blank">#Debian</a>

:projetstodon: Shalien<a href="https://tech.lgbt/@bookwyrm" class="u-url mention" rel="nofollow noopener" target="_blank">@bookwyrm</a> Installed, running (not thanks to <a href="https://mastodon.projetretro.io/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a>, <a href="https://mastodon.projetretro.io/tags/socket" class="mention hashtag" rel="nofollow noopener" target="_blank">#socket</a> and python <a href="https://bookwyrm.projetretro.io/user/shalien" rel="nofollow noopener" translate="no" target="_blank">https://bookwyrm.projetretro.io/user/shalien</a>now gonna find all the book in the house to scan them

Sexybiggetje🐖Doing shared memory tricks in <a href="https://ieji.de/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a> to use as a cache is actually a lot faster than using <a href="https://ieji.de/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a>. Even while maintaining a registry to clear the cache on deploy/demand. Getting an almost free 30% perf increase. Adds a few lines of maintenance burden, but also saves us from running redis ofc.

Jesse SkinnerWhy is Redis just the absolute best glue between processes? Surely Linux/Unix has something just as good? But in my experience, there's literally nothing better for communicating between processes.Don't get me wrong, I love Redis, but I just wonder why the best solution ended up being a memory based database and not something in the operating system itself.<a href="https://toot.cafe/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a> <a href="https://toot.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Kushal Das :python: :tor:Update: I need more coffee, the error was not from redis at all :( Fixed now.Dear <a href="https://toots.dgplug.org/tags/rustland" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustland</a> <a href="https://toots.dgplug.org/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> folks in the timeline, in a simple <a href="https://toots.dgplug.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> / <a href="https://toots.dgplug.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> compose case, my rust <a href="https://toots.dgplug.org/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a> client can not connect to the redis server with the following error: `Error: Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }` I am using `redis://redis:6379` as connection string. It works via redis-cli command line in the same container. Any tips?

Tuxi ⁂Okay, ich glaube, ich habe die richtigen Einstellungen für das Zusammenspiel von <a href="https://anonsys.net/search?tag=MariaDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#MariaDB</a>, <a href="https://anonsys.net/search?tag=PHP-FPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP-FPM</a> und <a href="https://anonsys.net/search?tag=Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> gefunden. Der "Feinschliff" war nicht ganz ohne. Seit ca. einer Woche scheint es hier auf <a href="https://anonsys.net/search?tag=anonsys.net" class="mention hashtag" rel="nofollow noopener" target="_blank">#anonsys.net</a> rundzulaufen. Danke an <a href="https://missocial.de/profile/jools" class="u-url mention" rel="nofollow noopener" target="_blank">@jools</a>, <a href="https://friendica.opensocial.space/profile/raroun" class="u-url mention" rel="nofollow noopener" target="_blank">@raroun</a> und <a href="https://sekretaerbaer.de/profile/oldkid" class="u-url mention" rel="nofollow noopener" target="_blank">@oldkid</a> für den Input und die Unterstützung. 👍🍻 <a href="https://anonsys.net/search?tag=Friendica" class="mention hashtag" rel="nofollow noopener" target="_blank">#Friendica</a> <a href="https://anonsys.net/search?tag=FediAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediAdmin</a>

Boiling SteamValkey Turns One: Community fork of Redis: <a href="https://www.gomomento.com/blog/valkey-turns-one-how-the-community-fork-left-redis-in-the-dust/" rel="nofollow noopener" target="_blank">https://www.gomomento.com/blog/valkey-turns-one-how-the-community-fork-left-redis-in-the-dust/</a> <a href="https://mastodon.cloud/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.cloud/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://mastodon.cloud/tags/valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#valkey</a> <a href="https://mastodon.cloud/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a> <a href="https://mastodon.cloud/tags/fork" class="mention hashtag" rel="nofollow noopener" target="_blank">#fork</a> <a href="https://mastodon.cloud/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#community</a> <a href="https://mastodon.cloud/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a>

Pablo BraseroNew blog post: how we made more efficient use of a web app's database for a substantial performance boost 🚀 <a href="https://blog.pablobm.com/2025/05/28/batch-and-delay-db-writes-improve-performance/" rel="nofollow noopener" translate="no" target="_blank">https://blog.pablobm.com/2025/05/28/batch-and-delay-db-writes-improve-performance/</a>In short: 1. Group together sequential `INSERT` statements to the same table. 2. Temporarily store large blobs of data in <a href="https://metalhead.club/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> or similar, if storing in a relational database is only useful later and only in certain events.There, that's the meat of the article. I saved you having to read it 😅The specific stack was <a href="https://metalhead.club/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ruby</a> <a href="https://metalhead.club/tags/Rails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rails</a> <a href="https://metalhead.club/tags/Postgres" class="mention hashtag" rel="nofollow noopener" target="_blank">#Postgres</a>, but the technique was mostly technology-independent.(And because we have now come to this: no "AI" was used at any point in the writing of this article 🙄).

Kevin Karhan :verified:<a href="https://social.jacobian.org/@jacob" class="u-url mention" rel="nofollow noopener" target="_blank">@jacob</a> yes, and <a href="https://infosec.space/tags/OpenWashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenWashing</a> is a real issue not just with <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> as seen with <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> & others using <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> as a literal <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicense</a> which are just "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceAvailable</a>" instead of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>, but actual <a href="https://infosec.space/tags/donations" class="mention hashtag" rel="nofollow noopener" target="_blank">#donations</a>.and <a href="https://infosec.space/tags/contributions" class="mention hashtag" rel="nofollow noopener" target="_blank">#contributions</a>.<ul><li>Try to convince any C-level decisionmakers to donate even 1% of the equivalent of licensing the <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> equivalents of the <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> deployed will get one laughed at, and suggesting 10% threatened woth getting fired.</li></ul><a href="https://infosec.space/tags/AskMeHowIKnow" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskMeHowIKnow</a>…

seungjinI am back to Redis! `Redis is now available under the AGPLv3 open source license.` <a href="https://redis.io/blog/agplv3/" rel="nofollow noopener" translate="no" target="_blank">https://redis.io/blog/agplv3/</a> <a href="https://mstd.seungjin.net/tags/agpl3" class="mention hashtag" rel="nofollow noopener" target="_blank">#agpl3</a> <a href="https://mstd.seungjin.net/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a> <a href="https://mstd.seungjin.net/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a>

Carsten Rieger IT-Services 🔒Die <a href="https://digitalcourage.social/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nextcloud</a> Installationsskripte sind nun auch entsprechend des neuen <a href="https://digitalcourage.social/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a>-Server v. 8.0 (OpenSource) aktualisiert, getestet und veröffentlicht 👇 <a href="https://www.c-rieger.de/nextcloud-installationsskript/" rel="nofollow noopener" translate="no" target="_blank">https://www.c-rieger.de/nextcloud-installationsskript/</a>

Carsten Rieger IT-Services 🔒:nextcloud: NEWS :nextcloud: Unsere <a href="https://digitalcourage.social/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nextcloud</a> Installationsanleitung wurde hinsichtlich der neuen <a href="https://digitalcourage.social/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a>-Server Version 8.x (OpenSource) angepasst 👇 <a href="https://www.c-rieger.de/nextcloud-installationsanleitung/#c04" rel="nofollow noopener" translate="no" target="_blank">https://www.c-rieger.de/nextcloud-installationsanleitung/#c04</a>In Kürze wird auch das Installationsskript entsprechend aktualisiert...die Q/A erfolgt morgen.

Fossery Tech :debian: :gnome:(more FOSS news in previous posts of the thread)qBittorrent 5.1 released with security improvements, support for the Thunar file manager on Linux, support for the “eXact Length” parameter when creating magnet URIs, support for fetching the tracker list from URLs, announce_port support, drag support to the torrent content widget, ability to display the external IP address in the status bar etc.: <a href="https://9to5linux.com/qbittorrent-5-1-open-source-bittorrent-client-released-as-a-major-update" rel="nofollow noopener" translate="no" target="_blank">https://9to5linux.com/qbittorrent-5-1-open-source-bittorrent-client-released-as-a-major-update</a>Redis goes open source again (kinda), offers Open Source edition from version 8: <a href="https://alternativeto.net/news/2025/5/redis-goes-open-source-again-with-the-launch-of-redis-8-under-the-agplv3-license/" rel="nofollow noopener" translate="no" target="_blank">https://alternativeto.net/news/2025/5/redis-goes-open-source-again-with-the-launch-of-redis-8-under-the-agplv3-license/</a>UN ditches Google Forms for CryptPad, as part of their initiative to adopt FOSS technologies: <a href="https://news.itsfoss.com/un-ditches-google-form/" rel="nofollow noopener" translate="no" target="_blank">https://news.itsfoss.com/un-ditches-google-form/</a><a href="https://social.linux.pizza/tags/WeeklyNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#WeeklyNews</a> <a href="https://social.linux.pizza/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://social.linux.pizza/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://social.linux.pizza/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://social.linux.pizza/tags/FOSSNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSSNews</a> <a href="https://social.linux.pizza/tags/OpenSourceNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSourceNews</a> <a href="https://social.linux.pizza/tags/qBittorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#qBittorrent</a> <a href="https://social.linux.pizza/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#BitTorrent</a> <a href="https://social.linux.pizza/tags/Torrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#Torrent</a> <a href="https://social.linux.pizza/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> <a href="https://social.linux.pizza/tags/UN" class="mention hashtag" rel="nofollow noopener" target="_blank">#UN</a> <a href="https://social.linux.pizza/tags/Dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dev</a> <a href="https://social.linux.pizza/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://social.linux.pizza/tags/Database" class="mention hashtag" rel="nofollow noopener" target="_blank">#Database</a> <a href="https://social.linux.pizza/tags/DatabaseManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#DatabaseManagement</a> <a href="https://social.linux.pizza/tags/DBMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DBMS</a> <a href="https://social.linux.pizza/tags/NoSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#NoSQL</a> <a href="https://social.linux.pizza/tags/FosseryTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#FosseryTech</a>

Carsten Rieger IT-Services 🔒Gute Neuigkeiten! <a href="https://digitalcourage.social/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> ist jetzt wirklich Open Source 👇 <a href="https://www.golem.de/news/datenbanken-redis-ist-jetzt-wirklich-open-source-2505-195865.html" rel="nofollow noopener" translate="no" target="_blank">https://www.golem.de/news/datenbanken-redis-ist-jetzt-wirklich-open-source-2505-195865.html</a>

Stefano Zacchiroli<a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@jwildeboer</a> Amen. Also, it's much worse than just having to agree to those licenses. The <a href="https://mastodon.xyz/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> contributor agreement grants the company a sublicense right, making de facto the AGPL ineffective against them.

Jan Wildeboer 😷:krulorange:While I also welcome <a href="https://social.wildeboer.net/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> offering their code under the <a href="https://social.wildeboer.net/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" 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" translate="no" target="_blank">https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md</a>

Thierry CarrezI'm glad that Redis is open source again, but what prevents them from rug pulling the license in the future again?At this point it's a better choice to stay with the successful fork developed in an open collaboration under a neutral governance, Valkey.<a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://fosstodon.org/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a> <a href="https://fosstodon.org/tags/Valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valkey</a>

Boiling SteamRedis is Open Source Again: <a href="https://antirez.com/news/151" rel="nofollow noopener" target="_blank">https://antirez.com/news/151</a> <a href="https://mastodon.cloud/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.cloud/tags/update" class="mention hashtag" rel="nofollow noopener" target="_blank">#update</a> <a href="https://mastodon.cloud/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://mastodon.cloud/tags/release" class="mention hashtag" rel="nofollow noopener" target="_blank">#release</a> <a href="https://mastodon.cloud/tags/redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#redis</a> <a href="https://mastodon.cloud/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a>

Simon PhippsPleased to see <a href="https://meshed.cloud/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> returning to an <a href="https://meshed.cloud/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> license. <a href="https://redis.io/blog/agplv3/" rel="nofollow noopener" translate="no" target="_blank">https://redis.io/blog/agplv3/</a>

Björn Schießle :europa:Last year, <a href="https://social.schiessle.eu/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> changed its license to the <a href="https://social.schiessle.eu/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a>, which is neither an <a href="https://social.schiessle.eu/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> nor a <a href="https://social.schiessle.eu/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> license. This led to <a href="https://social.schiessle.eu/tags/Valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valkey</a>, a fork and drop-in replacement.Now Redis has decided to go back to a real Free Software license, the <a href="https://social.schiessle.eu/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://social.schiessle.eu/tags/AGPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPL</a>. This is a great decision, although it remains to be seen if they reverted their decision in time, or if it is too late and the community will continue with Valkey and not look back.<a href="https://redis.io/blog/agplv3/" rel="nofollow noopener" translate="no" target="_blank">https://redis.io/blog/agplv3/</a>

Recent searches

Search options

Administered by:

Server stats:

#redis