debanqued
The cognitive dissonance in this
It seems you don’t know what that phrase means. It doesn’t follow from anything else you wrote why you think that.
You don’t think providing an email from a throw away service would strike the software as a malicious user/spam bot???
You don’t think that legitimate streetwise users secure themselves by supplying disposable email addresses???
You keep talking like you know everything
The post intends to solicit intelligent and civil discourse with logical reasoning, not the sort of ego-charged emotional hot-headed pissing contest you’re trying to bring here.
I’m not seeing how this is a good justification for login refusals to lack information and transparency. When you are denied a login, a well designed system tells you why you are denied and the rationale the server gives you should either include enough info to imply a remedial course of action (e.g. “re-apply and tell us more detail about why you like our node”), or at least make it clear that the refusal is final for reasons that are non-remedial. Users should not have to guess about why they are denied a login when countless things can go wrong with email at any moment. The denial rationale should be emailed and also copied into the server records to present upon login attempts.
The only exception to this would be if they really believe they are blocking a malicious user. Then there is some merit to being non-transparent to threat agents. But the status quo is to treat apps rejected for any arbitrary reason as they would an attacker.
I don’t want to be an enabler of the drivel, so without posting the full URL to that article that’s reachable in the open free world, I will just say that medium.com links should never be publicly shared outside of Cloudflare’s walled garden. I realise aussie.zone is also in Cloudflare’s walled garden, but please be aware that it’s federated and reaches audiences who are excluded by Cloudflare.
The medium.com portion of the URL should be replaced by scribe.rip to make a medium article reachable to everyone. Though I must say this particular article doesn’t need any more reach than it has.
Anyone who just wants the answer: see @souperk@reddthat.com’s comment in this thread.
I can’t watch videos but I will say that my biggest problem with the iME is not the security issue, but the anti-consumer aspect. Intel decided non-corporate consumers (who do not want or benefit from iME) can be disregarded marginalized. So disabling iME is insufficient and misses the problem.
The answer is to boycott iME CPUs. I never bought an intel CPU after 2008. I write this comment from a 16 year old PC just fine. I have pulled some more recent hardware out of dumpsters, ensuring I do not support anti-consumer products.