I think that it’s an underlying Spotify issue for sure, namely that an album is often present as an explicit and censored version. But I feel like Zotify should be able to deal with this.

While songs show up in Zotify with the [E] you usually just see multiple copies of the album without any identifiers. One of these will be the “real” album, but there doesn’t seem to be a way to filter the others.

There is this thing that I feel is most prevalent in the USA, to call any attraction to a girl under the age of 18 pedophilia. Because that’s the age to star in porn. The term should truly be used for attraction to children. I think it’s an extension of the “pedo panic” where every man is assumed for some reason to be a child rapist now.

As such almost every young man could at some point be caught as a “pedophile”- 17 year olds sneak into clubs all the time, for example. 20 year old hooked up with one? Now he is considered a pedophile even if the actual age of consent is lower.

Meanwhile the porn industry glorifies “barely 18” girls as something highly desirable. It’s a little messed up to say the least.

Actual pedos who are into kids should be put in mental institutions. But I would strongly suspect that 15% stated just includes honest young men and creepy old men, none of which are truly pedophiles. That number is way too high.

Don’t forget classics like Fuck_this_shit1! Fuck_this_shit2!

Militants specifically use these pagers for security and stealth. Everyone else just uses phones.

It’s a brilliant way to target only combatants, and also expose them to their friends and neighbours. This attack is incredibly disruptive with very little collateral damage compared to alternatives.

And yes, it’s terrorism, an attack meant to inspire terror and disrupt communication networks with a chilling effect much larger than the actual damage. However it’s interesting as unlike most terrorism it does not target civilians.

It’s also terrifying to think we are living in a world where a malicious component attack is a legitimate concern. This is one of those moments that change the world - I’m sure every industry is thinking about the danger of their foreign supply chain right now.

So uh yeah as we all know a lot of amphetamines have already been “open source” for a long time.

And we also know the DEA really doesn’t approve of private production… Vyvanse itself only really was created as a produg because of their control of the amphetamine market and their desire for products with lower abuse potential.

If we could get the DEA out of the way anyways, it would make more sense to just make dextroamphetamine as it’s simple, cheap and effective.

This is a pretty good idea, my wife dual boots and I’ll suggest it to her as Windows keeps trashing the EFI partition.

This would work but assumes the primary use of the machine is Windows and derates your performance under Linux significantly due to USB speeds. Even if you’re storing your data on the Windows HDD, NTFS drivers are dog slow compared to EXT4 and other *nix filesystems.

Also some BIOSes are a pain to get to boot off removable drives reliably so it really depends on what your machine is.

I’ve used Linux as a primary dev system for well over a decade now, and with the current state of Windows I’d really recommend just taking the leap, keep your Windows box if you need Windows software and build a dedicated Linux workstation.

You’re missing one:

• dedicated, air-gapped Windows box used for legacy industrial software

Aside from “lightweight apps in VM” this is the only solution I use now. (Unless you count Proton, but having Steam games Just Work barely feels like a “solution” as it requires zero effort on my part)

I don’t even trust Windows to dual boot off a separate disk without trying to break something anymore.

That’s a valid point, the dev cycle is compressed now and customer expectations are low.

So instead of putting in the long term effort to deliver and support a quality product, something that should have been considered a beta is just shipped and called “good enough”.

A good example I guess would be a long term embedded OSS project like Tasmota, compared to the barely functional firmware that comes stock on the devices that people buy to reflash to Tasmota.

Still there are few things that frustrate me like some Bluetooth device that really shouldn’t have been a Bluetooth device, and has non-deterministic behaviour due to lack of initialization or some other trivial fault. Why did the tractor work lights turn on as purple today? Nobody knows!

My type is a dying breed too, the guys who do their best to write robust code and actually trying to consider edge cases, race conditions, properly sized variables and efficient use of cycles, all the things that embedded guys have done as “embedded” evolved from 6800 to Pic, Atmel and then ESP platforms.

Now people seem to have embraced “move fast and break things” but that’s the exact opposite to how embedded is supposed to be done. Don’t get me wrong there is some great ESP code out there but there’s also a shitload of buggy and poorly documented libraries and devices that require far too many power cycles to keep functioning.

In my opinion one power cycle is too many in the embedded world. Your code should not leak memory. We grew up with BYTES of RAM to use, memory leaks were unthinkable!

And don’t get me started on the appalling mess that modern engineers can make with functional block inside a PLC, or their seeming lack of knowledge of industrial control standards that have existed since before the PLC.

You can also swim at the pool, that sounds like fun

Great to hear this story of success. That plus

$266.99 per probe for the original proprietary one

Reminds me of Schneider’s stupid proprietary dongle for programming their PLCs. It’s just a CH341 in a funny shaped case that fits into the funny shaped slot on the PLC, where it plugs onto an ordinary 0.1" pin header to talk logic level serial.

Plus it has a custom USB ID of course. Probably costs $2 to manufacture, sells for almost $300 as well.

Just bought and installed 20kWh of gently used AGM batteries, hopefully by the time they wear out they’ll have been the last lead-acid cells I own. Nice to see sodium actually hit production.

The claimed 10x C rate of lithium would be insane as lithium already has great power density. At that point it’s practically a capacitor, and could even be used to replace the much hated automotive starting batteries. Wonder how it handles low temperatures.

There’s a reason I farm with old relics, they aren’t “optimized” like the new stuff but they’re cheap and reliable to keep running.

Most of my implements don’t even have an electrical connection and some of the tractors have literally a starter motor, alternator, battery. Maybe lights if you’re lucky!

Some of the concepts in this book really stuck with me, but I had no idea what the title was! Thanks!

“Some days you’re the original, some days you’re the copy” or something like that

Oops my apologies, lol I checked and I must have installed the upstream NewPipe repo so long ago that I forgot that I even had it in my sources list. Literally my only repo other than Fdroid main.

No reason not to use it, though, it’s the official NewPipe repo:

https://archive.newpipe.net/fdroid/repo?fingerprint=e2402c78f9b97c6c89e97db914a2751fda1d02fe2039cc0897a462bdb57e7501

Refresh your repos, I literally just downloaded and installed it

Out on Fdroid now and working

I feel the OOP debate got a bit out of hand. I hate OOP as well, as a paradigm.

But I love objects. An object is just a struct that can perform operations on itself. It’s super useful. So many problems lend themselves to the use of objects.

I’ve been writing a mix of C and C++ for so long I don’t even know where the line is supposed to be. It’s “C with objects”. I probably use only 1% of the functionality of C++, but that 1% is a huge upgrade from bare C IMO.

I was more referring to the fact that everything is immutable by default. As someone who’s just starting to get old (40) and literally grew up with C, it’s just ingrained in me that a variable is… Variable.

If I want a variable to be immutable I would declare it const, and I’m just not used to the opposite. So when playing with Rust, the tutorial said that “most people find themselves fighting with the borrow checker” and sure enough, that’s what I ended up doing!

I like the concepts behind it, it really encourages writing safe code, and I feel like it’s not just going to be a fad language but will likely end up underlying secure systems of the future. Linux kernel rewrite in Rust when?

It’s just that personally I don’t have the flow of writing code like I would in C/++, just not used to it. The scoping, the way you pass variables and can sort of “use up a reference” so it’s not available anymore just feels cumbersome compared to just passing &memory_location and getting on with it, lol