That's a great list. I've just opened a pull request on the minio repository to add these to the list of alternatives.

https://github.com/minio/minio/pull/21746

I believe the Minio developers are aware of the alternatives, having only their own commercial solution listed as alternatives might be a deliberate decision. But you can try merging the PR, there's nothing wrong with it

While I do approve of that MR, doing it is ironic considering the topic was "MinIO repository is no longer maintained"

Let's hope the editor has second thoughts on some parts

I'm well aware of the irony surrounding minio, adding a little bit more doesn't hurt :P

The mentioned AIStor "alternative" is on the min.io website. It seems like a re-brand. I doubt they will link to competing products.

I used bubbletea for a while but quit it because of inconsistencies in the design. Went to ratatui and never looked back. Go and Bubbletea are nice, but rust is much more suited for building tuis.

I'd love to hear more about those inconsistencies. Would you be willing to share?

I built RatatuiRuby recently, and I'm currently building Rooibos, its MVU framework to compete with BubbleTea. I'd love to avoid repeating Charm's mistakes.

Ratatui dev here. We love both Bubbletea and Textual (though I'm personally not a huge fan of either Go or Python). They're inspirations for us to make good looking stuff.

This is awesome! I love ratatui, having it available on embedded is very cool! I wonder if it will work with async on embedded e.g. embassy..

absolutely, it will work with any other embedded Rust application. The backend only provides a bridge between the embedded-graphics library and the Ratatui widget renderer.

They are great, although I wouldnt use the articles advice on using hashtext to get a number for the lock. This may cause collisions, especially when used with a large number of locks.

In a project Im working on we have a single go package that holds a list of all advisory lock numbers as constants.

The EUPL isn't as explicit as AGPL.

> — ‘Distribution’ or ‘Communication’: any act of selling, giving, lending, renting, distributing, communicating, transmitting, or otherwise making available, online or offline, copies of the Work or providing access to its essential functionalities at the disposal of any other natural or legal person.

I believe there is a problem/conflict with the networked-software clause and the EUPL's compatibility clause. It allows anyone to fork a project under the GPL license. When someone makes a fork of an EUPL project under the GPL license, they are then bypassing the extra conditions set out in the AGPL. I believe this to be a mistake/loophole in the EUPL. But I am not a lawyer so I really hope an actual legal expert can weigh in on this.

> I don't think there's ever been a double-bird-strike incident, though.

The most well known double-bird-strike incident is probably the one where Sully landed a plane on the Hudson River.

https://en.wikipedia.org/wiki/US_Airways_Flight_1549#Takeoff...

-edit: ok, everyone had the same thought, haha -

I use TrueNAS Scale as root OS and have it run a Linux VM, which is easily done via their 'Virtualization' feature. No need for Proxmox. Afaik it works a lot better to give zfs direct access to underlying hdds. TrueNAS also has an 'Apps' feature, which are basically glorified helm chart installs on k3s that TrueNAS installs for you. But I prefer more control so I have k8s on the Linux VM. Whats also great is that the k8s on the Linux VM can use the TrueNAS storage via democratic-csi.

https://github.com/democratic-csi/democratic-csi

I was using Truecharts before k8s was deprecated.

The deprecation caused me to move to something more neutral and stay away from all 'native' apps of TrueNAS and migrated to ordinary docker-compose, because that seem to be the most approachable.

I was also looking into running a Talos k8s cluster, but that didn't seem to be as approachable to me and a bit overkill for a single-node setup.

I run Proxmox on the bare metal and pass the HBA through to the TrueNAS VM (so it gets direct access to the attached drives).

It feels as if the text on top of the device is upside down.. Should be directed at the user of the device, who sits behind the device (on the side of the small screen)

I recently switched my system to the S2 app and protocol. I was still on the old S1 app for the past years which worked fine, but I wanted to add new Sonos devices that only supported the S2-protocol/app.

I had checked the compatibility lists and found that one of my older sonos devices wouldnt be supported. But I accepted that as I really wanted to get a new Sonos Sub 4 (S2-only) to connect with my existing Sonos Playbar (which supports updating to S2).

The upgrade process was bad, had to restart and reset devices a couple of times.. but after a while I got all my existing Sonos devices onto S2.

When I added the Sub to the system, the app told me that I couldnt pair it with the playbar. The app adviced me to get one of the newer Sonos soundbars..

I'm very disappointed that they did this.. I fully understand that some devices dont work with a new protocol, but after consulting the compatibility list I expected my Sonos Playbar would be able to pair with all other S2 devices.. what is even weirder is that it is possible to link the playbar with the older Subwoofer devices on the S2 network, so why couldnt a newer device be able to do the same thing..

I returned the Sub and will be ditching Sonos (and probably any other system where you "buy into" the system only to be left with uncompatible gear after a while..

I think from now on I will separate the "smart" from the "hifi" so I can combine and upgrade as I please.. will probably give Dante a try for networked audio, they have a good track record with quality and compatibility. Its quite prosumer though. Perhaps not as user-friendly as Sonos (was).