Dran @ Dran_Arcana @lemmy.world

Posts

0

Comments

472

Joined

2 yr. ago

There are a lot of moderates that are hesitant about AOC. She's expressed ideas like getting rid of the filibuster, which would be great while "your" party is in charge, but is one of the very few checks available for a minority party to halt truly controversial legislation. The extra steps are kind of dumb, but the foundational idea that legislation should at least require a 60/40 majority most of the time enforces an idea of compromise and representation in almost every bill.

I would shudder to think what a bad president could put through if unchecked by the opposition party in an essentially 50/50 politically divided populace.

I think that holds true in this case... but I'll be damned if the ltt screwdriver isn't the best hand tool I've ever owned.

When ML training farms run out of new text to train on, "they" may very well want your original writing too...

Me too brother, but I disagree with your assessment on value

An non-blacklisted residential IP address with reasonable throughput is valuable in and of itself. DDOS botnets, proxies to bypass geo blocks or to obfuscate illicit traffic, etc. Also your gaming PC could be used for distributed compute workloads of compromised, usually crypto mining.

Any hardware/connection has value if it's "free". It's just a numbers game beyond that.

For now, ctt winutil does a pretty good job at removing the cruft. I've long since switched to debian for my daily driver, but as a remote-access sunshine host for games that require kernel level anticheat, it's surprisingly usable.

For anyone looking to keep windows around in some capacity, I strongly recommend it. https://github.com/ChrisTitusTech/winutil

Every packet you send/receive relies on passive security. Your nic drivers, the driver kernel model, all of the userland applications that sit on top of it. I get that in practical terms, your firewall will do a lot of the heavy lifting but there are passive rce vulnerabilities in previous unsupported versions of Windows that are trivially exploitable today.

Even if you trust their intent to not misuse your data, there are now a lot of live rpc hooks into your operating system, controllable by anyone who can compromise their azure implementation, which has happened at least twice in recent memory. If the data never leaves your device, and they didn't have a way in, they wouldn't have those things to lose in the first place.

The interdependency itself, regardless of intent, is inherently more dangerous than the previous separate paradigm that used to exist.

Your dad probably got lucky, and your router's firewall probably did a lot of the heavy lifting. If you were to connect a win 2000/XP computer to the internet today without a firewall between, it would be compromised in minutes (there are loads of videos of people demoing this).

While I don't have proof that 7 would be the same, I strongly suspect it would be the same. 10 will get there soon too. Firewalls will stop most of the low hanging fruit, but an application that bridges connections through the firewall are that much more vulnerable to exploitations that won't be integrated by your running kernel.

They won't brick it, but you can bet that a lot of people are sitting on unreleased 0-days for win10. It will likely be dangerous to connect to the internet on day 1.

Thank you for letting me know what software not to use; good bot

Crossfading and normalization would both independently be dealbreakers for me. I can't go back

I would be genuinely surprised if fair use draws the line on format-shifted, legally purchased media, at "remote watch-together", leaving format-shifting and local watch-together in-tact.

If it were up to the studio's interpretation of the law, you'd need to purchase a license for each person during local watch-together.

RE: backups, I'd recommend altering your workflow. Instead of taking an image of a box, automate the creation of that box. Create a bash script that takes a base OS, and installs everything you use fresh. Then have it apply configuration files where appropriate, and lastly figure out which applications really need backup blobs to work properly (thunderbird, for example). Once you have that, your backups become just the data itself. Photos, documents, etc. Everything else is effectively ephemeral because it can be reproduced through automation.

Takes a lot less space, is a lot more portable. And much better in scenarios where something in your OS is broken or you get a new computer and want to replicate your setup.

agree in principal, but in practice:

1. parents who live across the state
2. plexamp for music

They are indeed just that keen on our data.

They know they can't get rid of it for all of their customers, but they do want to make it as hard as possible for random users to do so.

The problem with this is it doesn't work for home users that want to pay for their software. Crazy... I know... but those people do exist.

For people with "that one game" there is a middle ground. Mine is Destiny 2 and they use a version of easy anticheat that refuses to run on Linux. My solution was to buy a $150 used Dell on eBay, a $180 GPU to be able to output to my 4 high-res displays, and install Debian + moonlight on it. I moved my gaming PC downstairs and a combination of wake-on-lan + sunshine means that I can game at functionally native performance, streaming from the basement. In my setup, windows only exists to play games on.

The added bonus here is now I can also stream games to my phone, or other _{thin clients} in the house, saving me upgrade costs if I want to play something in the living room or upstairs. All you need is the bare minimum for native-framerate, native-res decoding, which you can find in just about anything made in the last 5-10 years.

+1 to all of this.

For ~3 years I ran a Debian system off of a raid 1 of 2 USB drives. I didn't have the spare drive bay slots in my cs24-ty and I didn't have the room for an expander.

SanDisk apparently didn't consider my use case "warranty-voiding" and were content to replace them whenever they failed. (I was honest during the first warranty inquiry about how they were used; I doubt you could get away with this with modern SanDisk though) I had a 3-year warranty on the drives, and checking my email, I replaced a total of 11 over the 3 year period. The first 7-8 were before I moved logging to a zfs dataset on the spinners, which helped a lot as those 7-8 failures were all in year 1 with the constant journaling, writing, and syncing of mostly logs.

TL/DR: great for testing if drivers and hardware work; don't do this in production

When I started learning Linux at work, the game I played with myself was i'd install Debian stable minimal on my primary workstation and I would not reinstall it ever. No matter what happened, I would always fix it.

I learned to install the basic subsystems to get a GUI and audio, learned the fun of Nvidia drivers to get xinerama and hw decoding working. In retrospect it seems trivial but as a new learner it was challenging and rewarding.

At one point I was trying to do something, and a guide online suggested installing some repo and installing newer libraries. I did so, and a week later I did a dist-upgrade (because I didn't know any better) and when I rebooted I was presented with a splash screen for "crunchbang" linux.

Figuring out how to get back to Debian without breaking everything probably taught me more about packages, package managers, filesystems, system config files, init (systemd wasn't really a thing yet) than everything else I had done combined.

For anyone wondering: 12 years into the project I had a drive from the mdadm mirror die, and while mdadm was copying to another mirror, the other drive died. I considered that a win but y'all can be the judge (no files were lost, 12yr into my Linux journey I had long since figured out automating NFS and rsync).

Can you think of a better proxy for financial stability that isn't obtrusively invasive?

I'm not saying it's perfect; I'm just saying I don't have a better idea. The intent is certainly reasonable.