• 4 Posts
  • 551 Comments
Joined 4 months ago
cake
Cake day: June 9th, 2024

help-circle
  • “Debian is too far behind! Packages are too old!”

    The best rule of thumb I’ve ever heard regarding Debian Stable is that if the kernel in stable’s default repo fully supports ALL your hardware, and the software in stable’s default repos fully support your workflows, it’s fine.

    If those are NOT true, then you probably don’t want to use Stable, because you’ll either end up fighting it via manually compiled and installed software, or you’ll venture into so many 3rd party repos for updated packages that updating it later becomes problematic and prone to making the whole system catch fire and burn down.


  • But consider that if you get a more powerful card at the same price you don’t need as much upscaling or frame generation. FSR being sightly worse is irrelevant if you can run the game at native.

    I’m on a 3080, and if I’m getting 40fps in a title at settings I’m happy with (which is ending up more common than I’d like), not even a 7900xtx is going to give me the 90fps I’d much prefer. And, lest you think I’m being vastly unfair, I’ll also say there are no nVidia cards that will do so either. And yes, this is entirely dependent on your resolution, but the ultrawide I’m quite fond of is essentially the same pixel count as 4k144, which is a lot of pixels to attempt to draw at once.

    The only way to get there (at least until the 5090 shows up, I guess?) is to do some sort of upscaling. And, frankly, FSR is - subjectively - not ‘slightly worse’ but rather such a artifact-y mess (at least in games I’m playing) that I’d rather have 40fps than deal with how ugly it makes everything.

    XESS is a lot better, and works fine on AMD cards, but until FSR gets a lot cleaner, or everything starts supporting XESS, DLSS is still the best game in town.

    As for NVENC, you’re absolutely right, unless you’re using it for streaming, and have a hard cap on upper bitrates because you’re not Twitch royalty. I’ll admit that’s an edge case that most people don’t have, or even need to consider, but if you do need low-bitrate streaming, and don’t want to deal with x264 doing it in software, well, it’s NVENC or sub-par quality from AMF. I’m honestly surprised they haven’t invested time in fixing the one real use case that hardware encoding still has (real-time encoding of low bitrates), but I suppose someone somewhere has an excel sheet that shows that the market that cares about it is so small as to be of no value to spend time on.


  • You know, the older I get the more I respect the people who come out and say ‘I’m not going to learn that, and I don’t want to.’

    It’s a LOT better than dealing with someone who half-asses and kinda wishy-washes around and says they’ll maybe do something but then doesn’t and well, wasn’t ever going to.

    If you’re not interested and won’t, say so up front so you don’t waste your or my time trying to get you to do something.


  • Have some stuff on a VPS, some stuff hosted as static pages at Cloudflare, some stuff hosted at home too.

    Depends on if 100% uptime is required, if they’re just serving static content, or if they’re in some way related to another service I’m running (I have a couple of BBSes, and the web pages that host the clients and VMs that host the clients run locally).

    Though, at this point, anything I’m NOT hosting at home is kinda a “legacy” deployment, and probably will be brought in-house at some point in the future or converted to static-only and put on Cloudflare if there’s some reason I can’t/don’t want to host it at home.







  • That’s a very rosy picture, but they skipped a very important detail, alas. Or well, a few.

    First, selling your power to the power companies in Texas is great! Except the amount they pay you is always going to be substantially less than the price you’re going to pay later to import a kwh.

    We have the Freedom™ to pay two seperate charges for power: the delivery cost, and the power cost. This is a great Freedom™ because it lets the power company pay you the power cost for your exported power, but you get to pay both halves when you no longer have that kwh in your batteries later.

    Also this is just an attempt to get someone else to pay their CapEx to catch extreme usage events, and the incentives being paid out to people who have spent tens of thousands of dollars is still tilted in the power company’s favor. The article itself even says it’s helping them make a bigger profit: if it was a fair set of incentives, well, then that wouldn’t be what’s actually happening, would it?

    And, worse, any non-Texans might not catch how unlivable shit gets if your A/C starts screwing with the set temperature when it’s 110F outside. The article says it turns it ‘off’, but the impact I’ve seen from some friends who have one of these plans setup is that it simply sets the temperature to something like 86; high enough to stop the usage, but not quite enough to kill you or your pets if you’re not aware it’s done it. Still, not the most pleasant.

    Still, it’s a good idea and a step in the right direction, but we need (lol, lmao) actual real regulation around this and the incentives to be a little less… lame. They’re very much structured around the ‘well, what else are you going to do with your excess?’, rather than with a real intent of fair dealing.



  • You have your coworkers on an unmanaged machine with a foreign OS on the guest WiFi with custom networking.

    Which, at any of my last few corporate jobs, would be grounds for termination, if not immediately throwing you out of the building and telling you if you come back we’re calling the cops.

    You really don’t bypass controls in a corporate environment like this if you like working there.

    (And yes, not EVERY job will react that way, but any that’s got any compliance requirements absolutely will.)








  • It’s serious, but seems like a wonky attack vector for most.

    Yeah, it’s super trivially exploited, BUT it requires you to do a series of dumb things or let an attacker have access to your LAN which is one of those you-have-bigger-problems moments anyways.

    And then you have to use their added printer (though there’s an exploit path that may be usable to over-write the printer you already have configured, if the attacker knows what that might be) to print something before anything happens.

    Dude who found it seems to have overhyped it just a little bit (while being a huge dick about it), but I could see how you might exploit this in certain circumstances.