L3Harris has been modernizing the communications infrastructure supporting the National Airspace System in close coordination with the FAA. With safety and reliability as our highest priorities, L3Harris, together with its telco partners and the FAA, has completed more than 70% of the planned airspace communications conversion from legacy copper wires to a fiber optic system. We are supporting the FAA in its investigation to understand the conditions that led to the Nov. 13 ground stop of our nation’s air travel. L3Harris takes the nationwide ground stop and its impact on travelers, airlines and air traffic operations seriously.
I think the problem is rooted in consideration of the architecture itself. The post mentioned one of the common patterns where people leave permissions too wide, suggestion is to let another LLM take a run at it to make some changes.
My personal reading is that people find it easier to put another bandaid on the top of existing one on the name of security. A sprawl of monitoring and automation tool give a sense of security while adding to the cost. It might be worthwhile to let it be visible to user, who can see the data, who can modify the data when it comes to self vs other and authenticated vs unauthenticated. And of course people are going to try to save money, these scanning features are going to show up as additional bill pretty soon.
We noticed that many projects come from earlier builds. Roughly speaking, building an insecure app is much harder today than 6-12 months ago. Agent will protest and try to suggest alternatives if the builder asks to have no security, for example. But some folks find it easier to build with no RLS and then add them later. But for a complex app, it's a hard task, things break etc. In our blogs, videos and office hours, I always recommend building with all security features on from the beginning, never trying to slap it on top after the fact
We are committed to keeping scanners free. A new UX for security rolls out soon (this month), will get a better understanding of what is wrong, who can see what and why important to fix.
Yes unfortunately security suffers a similar fate everywhere. For MVPs its a cost which is not tied to any revenue so it gets pushed on. Over the period of time you have built ecosystem of applications and services in a incremental way to provide features that customer asked for. Ironically no customer asked for the security explicitly, it was that non-functional requirement that exists in bare bones in some form. Its most likely not the part of architecture for sure in almost all the places, if an architecture exists.
The biggest revenue you will get is from enterprise customers and thats your biggest risk too if security goes south. You already have advantage of being close to customer stories and usage behavior. Some one within the company needs to build the platform again from grounds up with all these security requirements baked into the architecture, sort of parallel project one would say.
> We are committed to keeping scanners free.
This sounds like a good sentiment in theory, however this is a double edged sword. Scanning costs money to you as company and that cost is going to make it to the customer one way or another
Indeed, we are looking into having a path to take down apps that grossly violate privacy and data protection. It's a bit tricky legally so we need to find a good balance. Our thinking is so far: notification with ask to fix, grace period, if no action and no improvement - soft block until issues fixed.
Anyone [any hackers here perhaps] doing straight anonymous reselling of SerpApi Google searches, maybe $10 at a time? Like Kagi but minus most of the infra and team.
Also SerpApi results just as good as Google? Sometimes Google still beats Kagi (maybe I’m search bubbled despite light anonymity measures).
And, because this is HN, even though it is only 65":
Flanders Scientific: XMP651: 4k HDR @ 60 Hz (?? ms), up to 4000 nits QD-OLED, 1xHDMI ? (no HDCP) 4xSDI, OS: None?
I believe none of these have Wifi. None of them is perfect. Only the Flanders Scientific model has an OLED display, but it is roughly 10x the price of the others (this is a reference monitor, which is very much not targeted at consumers). It also only comes in sizes up to 65" and only has one HDMI port, which does not support HDCP at all. If you only need 55", they have a 2000 nit display (V550) that supports regular HDMI inputs (but is still quite expensive).
Of the remaining displays, the ViewSonic is the brightest, but does not have HDR support. The LG display supports the highest refresh rate and is probably the cheapest, but only has HDCP 2.0 (I think?), and runs webOS, which I view as the least trustworthy of the options. The Samsung display is the only one with built-in AV1 support (if that matters to you). They also have some older models (e.g., BE85FX-H), which may still be available somewhat cheaper, but I can find very little information on them. None of the displays appear to support HDMI 2.1 or 2.2, so 4k HDR is limited 4:2:0 chroma at 60 Hz. The ones labeled "OS: None?" clearly have an OS (the ViewSonic one advertises a 7 second boot time, for example, despite being labeled "OS-Free"), but it does not appear to be any of the major known-problematic ones.
I have no direct experience with any of these, so I cannot prove that they are not still spying on you.
Another dimension to consider might just be displays which are easily opened and the wireless hardware removed.
Unfortunately a lot of large displays really aren't safe to open -- you're likely to break the screen doing it. But I have seen some results on LG tvs that have the wireless hardware on a separate removable board that the TV runs fine without.
If the alternative is a commercial signboard display or a reference monitor though one might be better off buying N consumer TVs and accidentally destroying a couple. ... and the question of giving money to companies bundling spyware might be better addressed by spending the price difference funding efforts to stop the practice via other means (e.g. outlawing it... to the extent that its not already unlawful, lobbying state AGs to take action to the extent that it is...).
Just buy a consumer TV and don't connect it to the internet. Remove the WiFi board or desolder the chip if you must. It's better than paying five times as much for a worse display.
I bought an LG commercial display at the exorbitant $1k price point a few years ago and every single time I walk past it I feel good about the money I spent. Does it look worse? Probably?
Did I plug in a FireTV stick that is also spying on me? Yes.
But I still consider it to have been preferable to just have a (relatively) dumb display that does not know when I play a dvd or blu ray and can’t tattle on me if I connect the TV to my Game console and play something embarrassing like Train Simulator 17 Nerd Edition.
(Wish Apple had an incredible response to every single question, but while I’m still a fan, not going to use this comment as a plug… A little disappointed)
Working class buys cheapest available . Allow sale of new vehicles without seatbelts, airbags, etc. and that becomes the attractive thing to lease (assuming it can be insured). Allow, say… uninspected beef & dairy products instead and if those savings are passed on, that’ll be purchased by low-income folks too.
Motorcycles have a built-in discouragement from the cost-optimizing behavior: lack of those two extra wheels.
>Not quite---you can make a choice to endanger other road users, but never yourself!
Would be open to ways regulate enormous vehicles which’re dangerous to the public outside their cabins. Keep taxpayers alive + out of hospitals they might not be able to afford (cost passed on to me).
My point is more about the doublethink re: crash safety across various types of vehicles than the implications of actually trying to bring kei vehicles less than 25 years old to the US (in whatever form). Since you mentioned it, I would much rather we get serious about regulating huge, heavy personal vehicles than start worrying about regulatory carve-outs (or whatever) for kei vehicles.
But, (again) since you mentioned it---"new vehicles without seatbelts, airbags, etc." is a misrepresentation of modern kei vehicles. Kei cars sold new today have seatbelts, crumple zones, airbags, ABS, AEB, and so on. They perform well in crashes for their size---sure, they are small cars, but they aren't a scheme to foist unsafe-by-design shitboxes on people who can't afford something safer.
More recent kei pickups still use the cabover design which necessarily limits your available crumple volume, but even those have the modern safety systems. The imports you see in the US are 25+ years old, which affects their safety outcomes in the way you would expect. People here buy them despite the age and import rigamarole (arguably a terrible value on paper) because there is demand.
---
The Smart Fortwo is probably the closest thing to a modern kei car we've had in the US outside of imports. IIUC they made it work with our regs by designing to them from the start, but in practice its safety outcomes were apparently pretty similar to kei cars in Japan, and exactly what you'd expect: decent performance in single vehicle crashes, but they suffer in crashes with larger vehicles. They weren't sold on the cheap to lure cost-conscious buyers (neither are kei cars in Japan), and ultimately I guess Americans just didn't want to buy them. But they were solid runabouts for city dwellers and didn't feel unsafe to drive in that context.
tl;dr: If there was some viable scheme to sell new-ish kei vehicles in the US, I would not be terribly worried about the scenario you describe, and IMO implying some equivalence between e.g. a hypothetical moderate regulatory carve-out for such vehicles with abandonment of beef and dairy product inspections is utterly ridiculous.
Great answer. Excited to hear about the crumple zones. I'm going to watch some crash tests. Thanks for the Smart Fortwo comparison, a good reminder about that vehicle. I accept it as safe enough to sell and have probably changed my perspective for next time I see a modern kei.
You seem to be better at comparisons than me:
One note on selling new vehicles without safety features: that is an example of what might be made without regulation and what would definitely be purchased on both the new and later the used market by those who can't afford more.
On the beef inspection point, I wanted a random example to drive home that poverty stinks and in every single product category the absolute cheapest SKU has plenty of buyers. You well likely are able to offer a better example I could have thrown out?
Brown said everyone needed a better stereo in the 1990s. Factory radios were lousy. But the aftermarket stereos that people bought to replace the factory-issued ones could easily transfer from one car to the next. For example, if thieves steal the factory stereo from a Volkswagen Jetta, they're going to need a buyer with a Volkswagen Jetta, and all a thief can offer is the stereo the owner had to begin with.
The switch of car sound systems from a discrete unit that used a standard DIN form factor and connections to an integrated part of the dashboard from the mid '90s onward (and now into the complex "infotainment" system) kinda killed it as well. You can't just grad a single box out the dash and run. Does mean that car stereos are either un-upgradable, or require 3rd party kits to replace chunks of the facia nowadays though.
I feel like that would be implemented in a way that leads to parts being disabled due to bugs. “No the last guy didn’t pay his O2 sensor bill!”
Also worried in 50 years reviving old cars would be tough because some servers were down. Maybe a maker goes under and stops signing their parts?
Sure it could be implemented intelligently instead though. But maybe better to ensure all have superb education and employment opportunities at wonderful wages. (Prob cop out that one can say about any solution)
reply