Exactly. Case in point: https://lemmy.zip/post/71167170

Honestly, I’m surprised this isn’t common behaviour with all Smart TVs these days. It is trivial to probe a LAN network.

Thanks for the explanation, much appreciated.

Ah, that makes more sense. At least they’re retraining the staff, but I have to wonder if they offered the factory as part of the sale to TCL (If they did, why did TCL decline? If not, why not, if they’re now needing to retrain and repurpose the plant?)

So, they’re producing over 200 million discs a year, with 50% of that being for Playstation and 20% new orders currently, but want to kill that market? The projections of reduced disc production seem to be a clear result of Sony’s decision to stop making games on physical media, not a dying market. I have to wonder if the problem is that the market isn’t growing fast enough for Sony.

Ironically I wasn’t able to get EAC working on my Windows 10 installation due to the WinFSP clash, whilst CUERipper errors out on WINE (something to do with how it interacts with the ODD).

However, CUETools works fine and so I was able to compare the same CD ripped by CUETools/CUERipper on Windows with EAC under WINE. I used an ABBA CD as the test case (100+ matches in CTDB, 10+ in AccurateRip).

The CUE sheets are functionally identical (barring the differences in extra metadata stored between the two, as CUERipper included the IRSC where EAC has a Composer comment instead) – the gaps and indices are all the same. The raw rip itself is also identical - I ripped the CD to a disc image (with offset correction in both cases) and the md5 checksum of the WAV file from both applications is the same.

In both tools the rip validated against AccurateRip and CUETools DB as well. I double-checked the EAC rip afterwards using CUETools (again under WINE), as a further test.

Finally got around to testing out EAC on WINE (prompted by my previous comment a few hours ago).

It seems to work without major issues on WINE 11 in a 32-bit prefix (at least on LMDE 7). Plugins need dotnet20 and dotnet48 installed, otherwise only the in-built AccurateRip meta engine shows up. I’ve only tested ripping to WAVE and FLAC, though.

In short, I’d say it’s worth a try now.

I’ve been looking into this myself recently. EAC still seems to be the top option (followed by CUERipper/CUETools). CUETools itself runs under WINE, but CUERipper doesn’t (at least for me). Haven’t tried EAC on WINE yet.

https://wiki.hydrogenaudio.org/index.php?title=Comparison_of_CD_rippers

Exactly. The fact that “AI” has now been almost completely associated with LLMs is incredibly frustrating.

Hibernation technically does this to any SSD. It’s not just Windows 11.

Writing the entire contents of RAM to disk increases the wear on the SSD. The risk goes up if your SSD is nearly full and wear-levelling has to move more data around: https://en.wikipedia.org/wiki/Write_amplification#Wear_leveling

I’ve been using it for years too. Can recommend.

Good to know, thanks.

You can indeed: https://tailscale.com/docs/integrations/identity

That sounds like it may be a good fit for my use case, then. Thanks again and I’ll definitely look into it!

Thanks for the suggestion. I’m trying to move away from Google, but the idea of a shared account for tailscale (which seems to support a lot of different SSO options) may be useful.

Good to know, thanks. Not keen on Cloudflare, so it’s good to see that there’s now multiple recommendations for Pangolin and Tailscale in this thread.

Thanks - appreciate another recommendation for Pangolin + crowdsec, plus I didn’t know about authentik (which sounds super useful if the services behind it are compatible). I’m thinking I need to have a play around with tailscale and then Pangolin to see how they work and whether either will be appropriate for my use case.

I agree completely. But as a first step (especially since they do seem to have a keyword filter in place), “no restrictions” (or “no censorship” as the case is for the last image) seems like a very obvious phrase to include.

I agree that that’s the likely trigger - which makes me wonder why instructions to ignore censors or have “no restrictions” aren’t immediately blocked by a filter prior to passing the prompt to the image generation. I’d have thought this was a foreseeable exploit.

I’m referring to the last image that they produced combining the two methods – a graphically mutilated corpse.