What made it confusing at the time is the join packet would sometimes be accepted and passed through to the game, so it prompted further digging into why.

Comments URL: https://news.ycombinator.com/item?id=47898593

Points: 6

# Comments: 2

It's a great start. What I can say is that granularity of CVE's in policies will become important for larger consumers. We have about 4.5mn artifacts so even getting CVSSv3 10's blocked was a challenge, let alone 9.8.

Part of the reason we pay the big license fee is so we have someone to turn to when it inevitably breaks because we’ve used it in a way nobody has before. In Jan last year we were using 30TB of artifact storage in S3. That’s 140TB today.

Where do you get your CVE data? Would built artifacts have their CVEs updated after the fact? Do you have blocking policies on artifacts based on CVEs, licenses, artifact age, etc?

What I’m personally missing is the social capital. “Just invite people to stuff” doesn’t work, because my prior in-person social network is fragmented over 3 continents and many more countries and time zones. Minting new social capital is difficult - joining social events requires an invite to a social event to meet other people to start the process.

I want to host my gas station network’s air machine infrastructure, and I only want people in the US to be able to access it. That simple task is literally impossible with what we have allowed the internet to become.

FWIW I love Cloudflare’s products and make use of a large amount of them, but I can’t advocate for using them in my professional job since we actually require distributed infrastructure that won’t fail globally in random ways we can’t control.

I get why the enshittification of IXPs is occurring. Over the years many small and careless ISPs have caused issues for IXPs (and peers) based on what I've seen on mailing lists. It's hard work managing many hundreds or thousands of peers, let alone the equipment cost with multi-100Gbit ports becoming the norm for larger providers.

This is the least bit surprising coming from a country that is in steady decline.

The title “DevOps Engineer” often fits a permanent role of sanctioned illegibility in large organisations. One cannot explain exactly what a “DevOps Engineer” does, because (a) you cannot _engineer_ a culture, and (b) largely these engineers do urgent and important work that cannot be planned, estimated, put into sprints, etc.

I’ve had this title through several of my roles at orgs over the years and I detest it, but nonetheless understand why it exists.

Digital identity is on the slightly more controlling side of this, but the article focuses entirely on the cynical perspective without considering the positives.

I purchased 10 genuine new from a verified vendor and 6 had to be RMA’d within the first year.

I recently switched from startup to $ENTERPRISE and the thing I’m struggling with the most is time zones. My manager is 11 hours ahead and infrastructure/security change approvers are 6 hours behind.

Now add the big shift back to on-premises infrastructure and it’ll be impossible to get anything done.