

100% a trademark violation, and there’s nothing like an interoperability carveout for trademarks that could be used to defend it.
100% a trademark violation, and there’s nothing like an interoperability carveout for trademarks that could be used to defend it.
This isn’t really the same kind of bug. Those bugs made instructions emit the wrong answer, which is obviously really bad, and they’re really rare. The bugs in the article make instructions take different amounts of time depending on what else the CPU has done recently, which isn’t something anyone would notice except that by asking the kernel to do something and measuring the time to execute affected instructions, an attacker that only had usermode access could learn secrets that should only be available to the kernel.
I’ve got a textured PEI bed and when I’ve printed TPU, the adhesion has been perfect, i.e. good enough that the part wasn’t going to go anywhere unless I wanted it to, but still easy enough to remove when the print was done and the bed had cooled. I guess it could vary from filament brand to brand, so it’s possibly worth trying the same brand as I used, which was cheap Geeetech stuff. It’s £8 a roll, and I’ve used their cheap PLA for ages. I wouldn’t recommend their ABS+, though, as it seems to break down at the lowest temperature that gives reasonable layer adhesion.
Originally, that was from Dave, which is owned by the BBC.
Sveriges Riksbank Prize in Economic Sciences in Memory of Alfred Nobel winning economist. There’s no such thing as a Nobel Prize In Economics, and economists were upset by this and made their own prize with a complicated name that the media would shorten and muddle with a real Nobel Prize.
If it works like real WoW64, then 16 bit applications won’t work ever but 32 bit applications that don’t work will be because of fixable bugs.
That way they can sell it as Crab Product rather than the much less appetising Crab Flavour Fish Product.
AGPL is a full-on FOSS licence with strong copyleft requirements, not a measly open-source licence like Apache, which could be pivoted to proprietary at a moment’s notice. We’re communicating through an AGPL-licensed system right now as it’s what Lemmy’s licensed as. If they were going for a corporate-friendly licence, AGPL is the last thing they’d choose as it forces you to share source code with even more people than the regular GPL does.
You might find that your hardware exposes 3.2 features via Vulkan and that if you configure your machine to use Zink rather than native GL, you can get a 3.2 context.
Wikipedia management shouldn’t be under that pressure. There’s no profit motive to enshittify or replace human contributions. They’re funded by donations from users, so their top priority should be giving users what they want, not attracting bubble-chasing venture capital.
You can’t starve children to death in self defence.
It could still be to cover up war crimes that the BBC team hadn’t got quite close enough to discover yet, but the IDF were concerned that they might have if not scared away. It could just be for opsec, but them having been competent at stopping the BBC seeing whatever it was they were hiding isn’t proof that the thing being hidden was benign.
Variations of this meme get posted every week, but I’ve never experienced it, despite having had tens of grub updates murder-suicide the Windows boot loader and grub itself across five or six different machines. Thankfully, it’s pretty easy to rebuild a Windows boot partition, but the frequency that I’m hit with this problem is one of the major reasons I avoid using Linux. Eventually I’m going to have to switch, but that’s driven mainly by Windows getting worse rather than any of the pain points I’ve had when trying to switch full time in the past having been fixed.
Unfortunately, I’m not the right kind of software engineer to answer in more detail than that.
I think for something like this, you’d rent cloud servers as you’d expect the number of concurrent users to change over time and ideally would be able to spin up more capacity when you need it without having to have those machines available all the time. You still need some kind of system that decides when to order more capacity with enough warning that it’s actually available (you can tell AWS you want a VM immediately, but it still takes a couple of minutes to transfer your data onto it and boot it up, which is longer than people want to sit in a loading screen) and decides which servers to assign to which users.
There’s a strong argument that the server architecture needed to be better at launch, but then the game sold more than an order of magnitude better than it was expected to, so no one would have noticed that it scaled badly had the player count been in line with their design and testing.
This is a mod that only runs in a fan-made from-scratch recreation of the game’s engine. Morrowind modders have basically every other game’s modders beaten if you want to make it a competition.
Thermal problems are much less likely to kill hardware than they used to be. CPU manufacturers have got much better at avoiding microfractures caused by thermal stress (e.g. by making sure that everything in the CPU expands at the same rate when heated) and failures from electromigration (where the atoms in the CPU move because of applied voltage and stop being parts of transistors and traces, which happens faster at higher temperatures). Ten or twenty years ago, it was really bad for chips to swing between low and high temperatures a lot due to thermal stress, and bad for them to stay at above 90°C for a long time due to electromigration, but now heat makes so little difference that modern CPUs dynamically adjust their frequency to stay between 99.0° and 99.9° under load by default. The main benefit of extra cooling these days is that you can stay at a higher frequency for longer without exceeding the temperature limit, so get better average performance, but unless your cooling solution is seriously overspecced, the CPU will be above 99.0° under load a lot of the time either way and the motherboard just won’t ramp the fan up to maximum.
The last time they had plenty of stock and cards people wanted to buy at the same time was the RX 200 series. They sold lots of cards, but part of the reason people wanted them was because they were priced fairly low because the cards were sold with low margins, so they didn’t make a huge amount of money, helping to subsidise their CPU division when it was making a loss, but not more.
Shortly after this generation launched Litecoin ASIC mining hardware became available, so suddenly the used market was flooded with these current-generation cards, making it make little sense to buy a new one for RRP, so towards the end of the generation, the cards were sold new at a loss just to make space. That meant they needed to release the next generation cards to convince people to buy them, but as they were just a refresh generation (basically the same GPUs but clocked higher and with lower model numbers with only the top-end Fury card being new silicon) it was hard to sell 300-series cards when they cost more than equivalent 200-series ones.
That meant they had less money to develop Polaris and Vegas than they wanted, so they ended up delayed. Polaris sold okay, but was only available as low-margin low-end cards, so didn’t make a huge amount of money. Vega ended up delayed by so long that Nvidia got an entire extra generation out, so AMD’s GTX 980 competitor ended up being an ineffective GTX 1070 competitor, and had to be sold for much less than planned, so again, didn’t make much money.
That problem compounded for years until Nvidia ran into their own problems recently.
It’s not unreasonable to claim that AMD graphics cards being in stock at the wrong time caused them a decade of problems.
That’d be trademark infringement, not copyright infringement.
That’s not quite the same thing, and still isn’t because the keys are copyrighted. There’s Digital Rights Management software running on the Switch, and part of what it does is decrypt encrypted parts of games with the keys. Originally, Nintendo managed to keep the keys secret, but eventually people managed to extract them. The next line of defence is that under the DMCA (or equivalent law in countries with a trade deal with the US), it’s illegal to attempt to circumvent DRM, and as the keys are capable of doing that, they themselves might count as a DRM circumvention device, which would be illegal to own or share. It’s a legal grey area whether or not they’d really count - lots of companies claim that it’s illegal to have these so-called illegal numbers, but Wikipedia are confident enough that that’s not what the law really says that their Illegal Number page lists a bunch of them.
This gets even more complicated when it’s specifically about emulators, as the DMCA (or equivalent) have a specific carve-out for interoperability, saying you’re allowed to ignore parts of the DMCA if it’s specifically for the goal of making computer software work with computer hardware it wasn’t originally intended to. For the relevant parts of the DMCA that aren’t related to DRM, there’s case law confirming that it’s okay. However, no emulator developers have ever actually been sued for making an emulator for a system with any DRM (e.g. the thing with Switch emulators several months ago was settled out of court, and the threat was to sue them for things like illegally sharing games between developers, when they could have each bought their own copy, so weren’t protected by the carve-out). That means that this is a grey area, too.
If Nintendo wanted to shut down an emulator based on its use of their keys, they’d not only have to set a precedent that the keys really did count as a DRM circumvention device, but also that the interoperability carve-out didn’t apply to DRM circumvention devices. It would be a big, expensive case, and as there are well-funded organisations that rely on the precedent not being set against them in both directions, both sides would get interested third parties funding their legal fees. No one wants that, so Nintendo stick to claiming emulators are illegal on their website, not in court documents, and only go after emulator developers who’ve provably done a second illegal thing they can be punished for.