Embed Notice

It was wise of @drewdevault to host redict (redis fork) on @Codeberg to maintain workflow parity with github and avoid any perceived conflicts of interest¹.

I wondered why LGPL and not of AGPL², which is also explained nicely: "but we want to make it as easy as possible for users to comply with the Redict license and we do not see any reason to discourage cloud providers from making use of Redict."

Hope other marquee projects follow suite.

¹https://fosstodon.org/@drewdevault/112167165399257154
² https://redict.io/posts/2024-03-22-redict-is-an-independent-fork/#why-lgpl