Even modern games replace distant geometry with billboards. Simplygon is one middleware that does this. The Remedy folks talked about how Alan Wake 2 used it at GDC last year or the year before.
The footnotes appear to the left of the main body of text around the position they appear in (viewing in a desktop browser). The article has grown a third note in the meantime and these are all visible now.
I get it, but also, it’s pretty amazing that it only takes 10 seconds to remotely activate and stream live video from a camera installed in a cat house placed on a sidewalk 6,000 miles away.
It is absolutely relevant. It is completely within the realm of feasibility that a foreign nation state would pressure a manufacturer in their jurisdiction to include a backdoor, or simply insert it themselves. Routers are in every home and office in the country, and can be leveraged for immense attacks. It’s a hugely attractive target, and it’s a reasonable security policy to try to limit our exposure to this threat. And it would absolutely make sense for adversaries to avoid buying U.S. made routers for exactly the same reason. Unfortunately this administration is generating more adversaries by the day.
I think you're responding to the wrong comment, or missing the nuance above.
Having state actors redirecting products after shipping, without telling the company or the client it's happening, and installing backdoors, has nothing at all to do with backdoors from manufacturers.
>a foreign nation state would pressure a manufacturer in their jurisdiction to include a backdoor
That absolutely is about jurisdiction and is a much bigger, more scalable attack than intercepting and installing implants. More to the point, it can be done at _any time_ not just the initial ship.
This is the problem with erosion of norms. We’ve all known for decades that consumer routers have shit security. We’ve all known about the risk of implants or intentional backdoors in the supply chain. And now when the FCC appears to be finally doing something about it, there’s a massive cloud of mistrust hanging over the whole idea.
The mistrust comes from those doing it, and the clearly corrupt ways they are operating. The maggot movement is basically rooted in a lot of very real frustrations from very real longstanding problems, but the only thing it offers as solutions is performative vice signalling.
People who care about the problems of digital security are not going to lean into the idea of simply banning devices based on where they were manufactured. Rather they would work at general standards and solutions to actually solve the problems - things like untying the markets for hardware/firmware/services, requiring firmware source escrow, mandating LAN protocols and controllers so every single IoT device isn't backhauling to its own mothership, and so on.
Likewise people who care about domestic manufacturing first and foremost are not going to champion applying steep blanket tariffs two decades after all of that industry has already left, or using regulatory agencies to shake down manufacturers for unrelated concessions.
You can fail to maintain a wiki written in any software. The value of Confluence is when everyone uses it, so there’s one place to find info to answer questions like “why the hell did we do it this way?”
Yes, but it's easier to fail when the markdown (or NIH markdown in the case of Confluence) is far removed from the code it describes. Which is why you should document closer to the products. Markdown files living by your code and even generated from code is way better than any experience I've had with Confluence (which is closing up on two decades soon enough).
I used Confluence a mere decade ago and, if anything, the 10 years after you used it only magnified its flaws relatively to what else was by then available so you didn’t miss much, and I suspect we haven’t missed much since, except more bloat.
reply