@Suiseiseki Yeah, that's Richard Stallman's version of the software / not-software distinction, and while it's the only way to be a free software zealot while still using commodity hardware, it's not useful.
Nobody has reverse-engineered a modern x86 chip from looking at the circuitry. All the high-level behaviour of an x86 chip is controlled by microcode: the CPU comes with microcode written by Intel, and there are precious few threat models where it makes sense not to use microcode updates.
@Suiseiseki By "you can look at the circuitry" logic, all unencrypted software gives you freedom 1 because you can look at the binaries. Indeed, it's much easier to look at the binaries of most proprietary software than to read the ROM from a CPU's die – and for Goldmont / Goldmont Plus chips, it's easier to decrypt and disassemble the microcode updates than to get at the actual ROM microcode.
RYF's secondary embedded processor exception should apply to a GPCPU's microcode as well.
@Suiseiseki Depends on your threat model. You're talking about the operating system, but @bugaevc's points all apply to Linux-libre's kernel.
Proprietary userland tends to be malware, but proprietary OEM software tends to just be buggy and unauditable. If you consider proprietary software to be inherently malicious, then your CPU (with its proprietary firmware and proprietary logic circuitry) is malicious and GNU Linux-libre is insecure.
@gnutelephony@devinprater Yeah, I'm not sure how the current systems take into account individual ear geometries when they're doing the "fake surround sound using headphones" thing. But the marketing copy says it works, so they must be doing something!
@halva@eevee Well, you decide that Firefox isn't supported, then you add a conditional redirect to a page helpfully informing your users of this fact.
Usually the site works completely fine in Firefox, if you manage to bypass the Firefox detection. Rarely, the CSS is dodgy and the JavaScript auto-fade doesn't work, but this can usually be fixed by simply deleting elements from the DOM.
@PaulDavisTheFirst This is true; however, leaving Twitter (if you can, without great sacrifice) is strictly better than theming it. No amount of client-side shenanigans gets over the fact that the server-side is abusive.
@lanodan@alcinnz And people outside India would still be able to access those servers, if they have IPv6. (Which I currently don't – but if I could say “I can't access India”, I might *get* it.)
It wouldn't break many Indian sites in India, because presumably they've mostly all already got IPv6.
@lanodan@alcinnz Then they can have No-IPv4 Wednesdays, or something. But I think going the whole way might be wise.
Microsoft has substantial IPv6 infrastructure; I bet they could make the transition between the announcement and the implementation of no-IPv6. And if they don't… we don't *need* GitHub. There are plenty of mirrors to get software that's hosted there (not to mention IPv4–IPv6 bridging proxies), and there are plenty of alternatives to host your own software on.
@grissallia 'Doubt' is Indian English for 'question'. This is the only major language barrier between Indians and the rest of the Anglosphere (over written communication, anyway), so I'm not impressed that Seagate hasn't taught their tech support people about it.
So that's $4500–$20994 total over the past 5½ years. So aktually, the trillion dollar corporation has paid not even 18 months' *US minimum wage* ($7.25/hr) for one person. Across 5½ years.
But hey. It's more than $5, so it's totally fair, right?
I like tools. Tools exist to serve a purpose; good tools serve many purposes. The purposes are the important part – but I'm no good at solving problems. I hope my tools will be enough.Testimonials from satisfied costumers: • "this pun is so fucking bad and i hate you for it" — @mikoIf I'm doing wrong, please tell me. Either I don't know (and you've saved everyone a lot of grief), or I do know (and I should face consequences).