HN user
OpenBSD isn't trying anything along those lines. The author is. Your statement comes off as an odd and disingenuous conflation. They are just file system attributes shared alike with Linux and a few other operating systems.
If I learned anything from fighting with MicroPython on far more powerful "limited environments" it would be that this is just a curious study, not a feasible choice.
As do theirs ;)
Not sure if you reflect at all over your own texts. You come off as projecting, incoherent and cognitively dissonant.
I have high hopes Ladybird will remain truly neutral and avoid any infringement on user integrity/privacy. Please never let the money dictate.
The tutorial is really thorough.
Maybe it's that I'm not rested right now but I find it hard to follow this train of thought because your reasoning is kinda wide, lofty and out there but I think OP means that it's irrational to throw Bill Gates entirely to the side based only on -another person- he associated with. Like how picky and fussy people refuse to touch something clean and unspoiled just because it sat next to something else that happened to be gross and smelly. I know it's clean but eww, icky. That kind of guilt by association.
Epstein's lawyers and his realtor, his tailor and his golf partners also associated with him but they don't appear at all to be desirable targets to debase with the same treatment and that's probably because they aren't rich or powerful or influential. And I'm certain that's what's tripping you. It's not just OK but maybe even preferential and encouraged by you to take a dump on certain people when a tiny vague chance presents itself only because the person is powerful.
I found this earlier comment from you on this topic which is a bit funny given your statement. To me youre kinda describing yourself.
HN is pretty divided about Stallman. Bringing up the things he actually at one
time said, even if later he said something different, results in a lot of
downvoting and toxicity. You can't talk about him without it devolving into
binary thinking and binary debates. Same as everything else in 2023 I guess.Update for those who were curious:
Roughly one hour after I e-mailed @elithrar who kindly reached out and offered to expediate the issue, the broken DNSSEC records were partly fixed. The domain once again resolved through all major DNSes, and public access was restored. At that point dnsviz.net told me that A, MX, etc. records were "insecure", though name resolution worked fine. A few minutes ago I took another look with dnsviz and it's now telling me that all records are secure. Everything looks normal again.
Thanks a bunch for helping out, @elithrar. I really appreciate that you were proactive.
If the problem had somehow fixed itself or if the support ticket had gotten any attention or feedback at all within a day or two instead of just being "snoozed" by support staff, I wouldn't have made any noise about it. After four days of complete silence a bit of "cry-baby consumer activism" seemed like the only resort.
If CF reconnects to me with an update on why the domain dead-locked and why it took 4 days to untilt everything I'll add that info as well.
I've been OP and this has been an update about my domain woes.
That would have been very helpful. The [Enable DNSSEC] button in the control panel is very assertive and confident through its casual and innocuous appearance.
Source: me, having lost access to my domain for 4 days for reasons that are not yet fully clear to me.
Which is a bit strange. I would have guessed that the support ticket system would be prioritized by staff.
I'll be back.
For any form of business endeavour that would be the obvious lowest starting point. For private users a $20/mo. price tag for registering one or a few domains would turn effective TLD pricing on its head. Suddenly owning a single .net domain is no longer $20 per year like it is with all the other thousand registrars, but instead it would be $260 per year.
Cloudflare's kind policy of zero markup on domain registrations on a free plan is remarkably generous. OK, sure, the traffic data has an obvious value to them, but maybe the support environment could improve with, I dunno, a tiny 5% markup.
I figured it would work since there were no problems for the handful of my domains using DNSSEC with the previous registrar. Maybe the button should come with a warning label. I'll certainly be a bit cautious from now on.
CF's authorative servers ("hasslo" and "crystal") respond correctly when queried directly, but that doesn't really help the situation.
Why do you presume the issue would have gotten immediate attention for the sum of $20? Customers don't make Cloudflare's terms, and customers didn't decide for Cloudflare to offer a free plan with zero markup for their registrar operations.
There is by users' own hands no way out of domain registration issues like these, sooner than 30-45 days when the domain can be transferred once again. Those who decide to offer registrar services, even for free, must hold some liability towards the users and the ecosystem and offer some support to make sure their product actually works.
My domain and users have ended up in limbo beyond anyone's but Cloudflare's control. I cannot transfer it back to the working registrar, or I would without being "angry at some free service". Why do you think berating me with snide remarks is helpful?
Thanks for the info, I'll keep it in mind for eventual future transfers. But shouldn't I be able to disable DNSSEC regardless, instead of the domain being stuck in limbo and hijacked by what appears to be a deadlock type of bug?
Thank you for the attention, e-mail on its way.
Yes. It had DNSSEC enabled for over a year when it was with the old registrar.
Can you please explain why DNSSEC was a bad idea in the first place? It worked perfectly fine with the old registrar.