me.dm by Medium.com

Codeberg✅ Done: Migration from <a href="https://social.anoxinon.de/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> to <a href="https://social.anoxinon.de/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> for caches ⏳ In Progress: Migration from MariaDB to Galera Cluster

CodebergWe 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 <a href="https://social.anoxinon.de/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> / <a href="https://social.anoxinon.de/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a>, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).

Jakob Miksch<a href="https://fosstodon.org/@rnanclares" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rnanclares</a> I can also take a true <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> fork like <a href="https://mastodon.social/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> or <a href="https://mastodon.social/tags/valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valkey</a> I am rather interested in just using the software directly as WMS cache without any other tool in combination

whoI am unsure, whether i should migrate my <a href="https://social.tchncs.de/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> instances to <a href="https://social.tchncs.de/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> or <a href="https://social.tchncs.de/tags/valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valkey</a> ?Whats your favorite?

Fabio ManganielloTesting <a class="hashtag" href="https://manganiello.social/tag/platypush" rel="nofollow noopener noreferrer" target="_blank">#Platypush</a> with <a class="hashtag" href="https://manganiello.social/tag/valkey" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> and <a class="hashtag" href="https://manganiello.social/tag/redict" rel="nofollow noopener noreferrer" target="_blank">#Redict</a>, now that <a class="hashtag" href="https://manganiello.social/tag/redis" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> has decided to apply a weirdly restrictive license like SSPL. At a first impression, it looks like Valkey is more ambitious and willing to implement many new features and optimize Redis' data model, while Redict seems to stick to "let's do what Redis already does best and become great at it, without time-series, open telemetry and a lot of new whistles and bells". I also wish that these projects will soon make it upstream in the major package managers. As of now most of the package managers still provide Redis, which isn't full FOSS anymore, and none of its recent forks. If you are working on a project that relies on Redis, what options are you currently considering after Redis' SSPL migration?

Robert AlexanderExpanded the Always Open project with the details of <a href="https://indieweb.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenTofu</a> <a href="https://indieweb.social/tags/OpenSearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSearch</a> <a href="https://indieweb.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> <a href="https://indieweb.social/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> and <a href="https://indieweb.social/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyDB</a>. I was surprised that KeyDB doesn't appear to use the DCO or other formal contributor agreement.<a href="https://always-open.alexsci.com/project/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://always-open.alexsci.com/project/</a>

jolupa :fedora: :gnome:També he provat <a href="https://drslump.canpavon.cat/tags/Redict" rel="nofollow noopener noreferrer" target="_blank">#Redict</a>, funciona la mar de bé! i ara estic provant <a href="https://drslump.canpavon.cat/tags/Valkey" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> a veure que tal... Però sí, sembla que tots funcionen bastant bé com a canvis directes de <a href="https://drslump.canpavon.cat/tags/Redis" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> en cas de...

Nsukami _ | 巣神<a href="https://mastodon.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a>, <a href="https://mastodon.social/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a>, <a href="https://mastodon.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a>, <a href="https://mastodon.social/tags/Garnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Garnet</a> 🤔 :thaenkin: pick the one which best suits your goals <a href="https://youtu.be/r67MRruNhow" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/r67MRruNhow</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a>

Bubu :progress_pride:<a href="https://fosstodon.org/@drewdevault" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@drewdevault</a> <a href="https://translate.codeberg.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://translate.codeberg.org/</a> is now running on <a href="https://chaos.social/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a>. 🎉 (Switch was easy enough, no problems encountered: <a href="https://codeberg.org/Codeberg-Infrastructure/weblate-docker-compose/commit/7eefb48fed481ea10f5b1fe285ae737206e25dcc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/Codeberg-Infrastructure/weblate-docker-compose/commit/7eefb48fed481ea10f5b1fe285ae737206e25dcc</a>)

Fabian N. T.Forking is easy, ideas are cheap — but this blog post/announcement by <a href="https://floss.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> successor (more correctly: one of multiple free software Redis successors) <a href="https://floss.social/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> sounds really reasonable: <a href="https://redict.io/posts/2024-04-03-redict-7.3.0-released/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://redict.io/posts/2024-04-03-redict-7.3.0-released/</a>Focus on stability over new features (the production projects we use(d) Redis in required mostly 2015-era features; I bet that’s true for many users) to distinguish itself from and peacefully coexist and complement with other forks like <a href="https://floss.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> 👍

Robert AlexanderAfter the <a href="https://indieweb.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> license change, I'm rooting for the <a href="https://indieweb.social/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> fork. LGPL prevents Redis from merging redict commits into redis so redict and redis will be distinct forks. <a href="https://indieweb.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> seems promising as well, and I get why the tech giants like it, but the BSD license allows Redis to simply merge valkey commits into redis.

Trolli Schmittlauch 🦥I'm not really sure it's a good thing the <a href="https://toot.matereal.eu/tags/LinuxFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxFoundation</a> has now also forked <a href="https://toot.matereal.eu/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a>: Their fork <a href="https://toot.matereal.eu/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> is announced to be backed by major large companies like AWS, Google, Ericsson, Oracle (duh!), but of course keeps using a BSD license. <a href="https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community</a>This might make it a lot harder for the <a href="https://toot.matereal.eu/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a>, that changed to LGPL, to keep traction. But copyleft licenses are a necessary against projects going proprietary again just like Redis did.

Jonathan Wright :almalinux:That moment when you get quoted on LWN...😃😃😃😃😃 <a href="https://lwn.net/SubscriberLink/966631/6bf2063136effa1e/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lwn.net/SubscriberLink/966631/6bf2063136effa1e/</a><a href="https://fosstodon.org/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> <a href="https://fosstodon.org/tags/almalinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#almalinux</a> <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a href="https://fosstodon.org/tags/valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valkey</a> <a href="https://fosstodon.org/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> <a href="https://fosstodon.org/tags/keydb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keydb</a>

Seirdy<a class="u-url mention" href="https://fosstodon.org/@mdolan" rel="nofollow noopener noreferrer" target="_blank">@mdolan</a> Anybody know how <a class="hashtag" href="https://pleroma.envs.net/tag/valkey" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> compares with <a class="hashtag" href="https://pleroma.envs.net/tag/redict" rel="nofollow noopener noreferrer" target="_blank">#Redict</a>?

Jonathan Wright :almalinux:Another day, another <a href="https://fosstodon.org/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> alternative packaged for <a href="https://fosstodon.org/@fedora" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fedora</a> and EPEL.This time we have <a href="https://fosstodon.org/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> led by <a href="https://fosstodon.org/@drewdevault" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@drewdevault</a> <a href="https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc1</a><a href="https://redict.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://redict.io</a><a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a href="https://fosstodon.org/tags/almalinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#almalinux</a>

Erik C. ThauvinRedict: A New Still-in-Development Redis Fork<a href="https://mastodon.social/tags/garnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#garnet</a> <a href="https://mastodon.social/tags/lgpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lgpl</a> <a href="https://mastodon.social/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> <a href="https://mastodon.social/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a><a href="https://linuxiac.com/redict-a-new-still-in-development-redis-fork/?utm_medium=erik.in&utm_source=mastodon" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxiac.com/redict-a-new-still-in-development-redis-fork/?utm_medium=erik.in&utm_source=mastodon</a>

Jason Bowen 🇺🇦I really like <a href="https://mastodon.social/@andrewrk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@andrewrk</a>'s take on the Redis BS. In short: "Redis Renamed to Redict."<a href="https://andrewkelley.me/post/redis-renamed-to-redict.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://andrewkelley.me/post/redis-renamed-to-redict.html</a><a href="https://mast.hpc.social/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> <a href="https://mast.hpc.social/tags/redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redict</a> <a href="https://mast.hpc.social/tags/floss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#floss</a> <a href="https://mast.hpc.social/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a>

𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓯 𝓓𝓸𝓷𝓪𝓽<a href="https://me.dm/@viktor" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@viktor</a> <a href="https://hostsharing.coop/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> <a href="https://hostsharing.coop/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyDB</a> <a href="https://hostsharing.coop/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> <a href="https://hostsharing.coop/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://hostsharing.coop/tags/oss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oss</a> <a href="https://hostsharing.coop/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://hostsharing.coop/tags/gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpl</a> That's great, thank you. Does anybody know, what happened to Pedis (Parallel Redis)? It seems to be stalled.

Matěj Cepl 🇪🇺 🇨🇿 🇺🇦<a href="https://fosstodon.org/@drewdevault" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@drewdevault</a> Shouldn’t you mention that if anybody distributes a product based on the UNMODIFIED <a href="https://floss.social/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> they can satisfy all requirements just by pointing to <a href="https://codeberg.org/redict/redict" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/redict/redict</a> to make it clear they don’t have to be burdened too much? <a href="https://floss.social/tags/IANAL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IANAL</a>

Viktor Nagornyy3 serious forks of <a href="https://me.dm/tags/Redis" class="mention hashtag" rel="tag">#Redis</a> to watch:<a href="https://me.dm/tags/KeyDB" class="mention hashtag" rel="tag">#KeyDB</a>Mutli-threaded fork of Redis based on Redis 6. BSD 3 Clause license. Owned by Snapchat. <a href="https://github.com/Snapchat/KeyDB" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/Snapchat/KeyDB</a><a href="https://me.dm/tags/Redict" class="mention hashtag" rel="tag">#Redict</a>Recent fork by @drewdevault@fosstodon.org based on the last open source version of Redis 7.2.4. On Codeberg. LGPL 3.0 license. <a href="https://codeberg.org/redict/redict" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://codeberg.org/redict/redict</a><a href="https://me.dm/tags/Valkey" class="mention hashtag" rel="tag">#Valkey</a>Accepted by Linux Foundation. Started by former Redis contributors & AWS employees. BSD 3 Clause license. <a href="https://valkey.io/" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://valkey.io/</a>Boosts appreciated 🙏<a href="https://me.dm/tags/opensource" class="mention hashtag" rel="tag">#opensource</a> <a href="https://me.dm/tags/oss" class="mention hashtag" rel="tag">#oss</a> <a href="https://me.dm/tags/foss" class="mention hashtag" rel="tag">#foss</a> <a href="https://me.dm/tags/gpl" class="mention hashtag" rel="tag">#gpl</a>

Recent searches

Search options

Administered by:

Server stats:

#redict