here in Seattle: the at-large City Council seat (district 8) between Tanya Woo and Alexis Mercedes-Rinck
Woo ran for a different city council seat a year ago, and lost. in the same election, a sitting city councilmember (Teresa Mosqueda) won an election to the King County Council, so she resigned her city council seat. to fill that vacant seat, the other newly-elected city councilmembers appointed Woo, even though she had just lost.
by the rules of the resignation and temporary appointment, the next regular election (now) elects a permanent replacement.
this leads to an unusual scenario - normally, Seattle (and all of Washington state) holds its municipal elections in odd years. the current mayor was elected in 2021, the most recent city council election was 2023. this leads predictably to much lower turnout for the municipal elections, which leads in turn to conservative business interests having an easier time buying the local elections.
Woo is aligned with the “business-friendly”, conservative (by Seattle standards) councilmembers who were elected in 2023. Mercedes-Rinck is significantly more progressive.
based on the primary results and subsequent polls, Woo winning seems pretty unlikely - but the margin of Mercedes-Rinck’s victory will still be interesting, because of what it says about Seattle politics in elections with high turnout. voter turnout in the 2023 elections was a dismal 36%. this year is likely to be in the ~80% range.
it’s also an opportunity for something very funny to happen - Tanya Woo may set a record that will likely never be broken, becoming the first candidate in city history to lose 2 elections in consecutive 2 years, for a seat that normally gets elected every 4 years.
hello Cleveland Beehaw! happy to be joining this pleasant little corner of the internet.
good news: I’m in the process of buying a house, after renting my whole life up to now. got lucky that the first home I toured in-person (after viewing probably 100+ homes on Zillow) I liked enough to put in an offer, and had the offer accepted. now I’m just going through inspection and mortgage approval crap.
bad news: I broke my big toe. not broken broken, apparently just a tiny chunk of bone flaked off where the ligament is attached. I put off going to the doctor about it, because I woke up with my toe swollen and painful, Dr. Google suggested that it was probably gout, and I didn’t want to bother with a doctor visit if it was just going to be a lecture about eating healthier. so I hobbled around on a broken toe for almost 2 weeks before going in for X-rays and getting told it was broken. now I’m crossing my fingers that it’ll heal up on its own in the Fancy Medical Shoe they gave me, and I won’t have to have surgery on it. and it’s a good reminder that sometimes I need to push past my ADHD and medical anxiety and go to the doctor anyway.
it might be more complicated than you’re looking for (requires a self-hosted server instead of just a desktop app), but take a look at the ecosystem surrounding Subsonic
Subsonic did some licensing shenanigans, but there’s an actively-maintained GPL3 fork called airsonic-advanced
there’s also alternate implementations, Gonic and Navidrome, that maintain compatibility with the original Subsonic API
because they all work with a common API, there’s a variety of clients that can work with the backend.
I’m also a big fan of Beets for music organization, it’s not tied in to the Subsonic ecosystem so you can use them completely separately if you want. it handles tagging, can fetch lyrics, and can also transcode the library (or an arbitrary subset of it) if you want to send it to a portable device. (not sure if this is what you mean by compatibility)
I currently have Beets organizing everything, run Navidrome on my server pointed at the Beets library directory, then Ultrasonic on my phone, and the Navidrome web interface on my desktop. the combo is especially nice for streaming to my phone - Navidrome will transcode FLAC to Opus on the fly, and Ultrasonic has an option to cache those files locally, and to pre-download them over wifi instead of mobile data. so I have my full collection available on my phone, can stream it from anywhere, and the songs I listen to frequently are already downloaded and I don’t have to waste mobile data, or wait for them to load if I have poor cell signal.
you read a post about how awesome C is, asking why more people don’t use it and instead gravitate towards replacements.
you ctrl-F for “security” - no mention
“buffer overflow” - nope
“memory safety” - nothing
“undefined behavior” - nada
this is sort of a reverse Chesterton’s Fence situation. the fence is getting replaced, and you’re talking about how great the old fence was, without understanding any of the actual problems it had.
you wrote some C and found it simple? OK, great, congratulations.
go work on a C codebase that spans 100 or more engineers all contributing to it.
go write some C code that listens on a TCP socket and has to deserialize potentially-malicious data received from the public internet.
go write some C code that will be used on an aircraft and has to comply with DO-178C.
and so on. after you’ve done that, come back here and tell us if you still think it’s “simple and effective” and “applicable everywhere”.
there is a reason C has stood the test of time over many decades. but there is also a reason it is being replaced with more modern languages.