GeertJohan

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

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.

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..

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.

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 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).

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..