Network issues
Tags in Network
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
Network
(1) Because it doesn't actually solve the problem.
New[UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
there are tons of TLDs that are cheap I'm not even sure what you are offering after reading this, but cloud is an even harder sell becau...
YouTube is blocking GIF comments from desktop (since 14 October 2026). Help wanted.
i have been going thru this for years now and because this attaches to contacts i have literally destroyed my family life.
I did the same thing this year, and I agree it's been one of the best decisions I've made.
Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
If 30 years ago someone suggested breaking into your house to take away your Nintendo games or remotely disabling them by sending somethi...
(1) Because it doesn't actually solve the problem.
(1) Because it doesn't actually solve the problem. The registry operator for .COM is not historically trustworthy either. (2) Because DNSSEC is a nightmare to deploy. Leaving the IANIX-type operational stuff aside, it doesn't work on all network paths; plenty of middleboxes freak out when they see DNS packets with DNSSEC records in them. People see this and want a best-effort system that uses DNSSEC in the majority cases where it does work, but now you have a downgradable, strippable security protocol. (3) eMudhra is being murdered by the root programs as we speak, and when they're gone all we'll remember them for is as a WebPKI incident. The WebPKI itself will continue to function and nobody will care. That can't happen with .COM or .CO.UK or .IO; there's no accountability for those registry operators at all, let alone transparency logs to track what they're doing.
Comments (0)
No comments yet. Start the discussion.