They are probably too busy fighting against their own users and subreddits that keep them afloat. Too much ideology in there to make sense, business wise.
Planting false evidence is getting a new twist here. The attacker doesn't even have to make a report! The victim's computer does it for him. Disk encryption malware may have new successor. Effective and scalable extortion as a service.
I thought an SRE is contacted when your house burns down due to for example scaling and to improve operations where much more load/customers are expected, no? Where the house is expected to fall but where it is not allowed to happen.
Deciding what to focus on yourself instead of the app showing you random screens which the developer thinks are currently important. The tool being out of the way and only the important things in-front of you. Where only you yourself decide what is important.
> It’s important that creators always have detailed knowledge about who is claiming content in their videos, where it appears, and what they can do to resolve the claim. That’s why all new manual claims will require copyright owners to provide timestamps to indicate exactly where their copyrighted content appears in videos they claim, and we’ve updated our editing tools to make it easier to automatically release a claim.
Is it a bug with Youtube or do they not follow this policy (consistently)?
Your point makes totally sense. Though I also like to be able to bring up (and destroy) my servers, with a single command, when needed. Going through the same ui every time is a little annoying.
Maybe it makes sense for development, short-lived resources or cattle. Don't start about cross-cluster use though, having to think about where a resource is defined/used is a mess.
The same issue is with Service Catalog and the open service broker model. AWS ACK is way better in its expressiveness, in comparison. (one crd per resource) It is more difficult to generate them though, compared to simply adding existing brokers.
Assigning programs/roles to certain screens helped me there. For example the left monitor is the browser, the center the editor and the right for consoles.
Though when a task only needs one screen for more than a couple of minutes to stay focused shutting off the other screens does help.
That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added.
Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though.
Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on Go/pkgsite (haven't checked whether they do)