bmitch3020
Joined 9 years ago
Joined 9 years ago
Of course they'll be more than happy to break the law themselves. They'll investigate themselves and find no wrongdoing. And I'm sure the officer will claim they smelled something giving them reasonable suspicion.
[0] https://infosec.exchange/@harrysintonen/117489564359709891
[1] https://infosec.exchange/@harrysintonen/117489801970908776
[0] https://infosec.exchange/@harrysintonen/117489564359709891
[1] https://infosec.exchange/@harrysintonen/117489801970908776
[0] https://infosec.exchange/@harrysintonen/117489564359709891
[1] https://infosec.exchange/@harrysintonen/117489801970908776
The first time I was forced to use a passkey implemented within the vendor's app (3rd party password managers were not an option). I quickly closed that account.
The second time was an app that popped up a passkey opt-in in the middle of a bunch of transaction screens. I quickly realized the error, but there was no easy undo. The opt in was one green button in the middle of the screen. Turning it back off required digging through settings to find the security option to disable, and then confirm my choice multiple times. That process also signed out all my other devices.
The fact that companies are resorting to dark patterns and forced requirements, where my money is held hostage, should be pretty good evidence of how poorly the passkey rollout is going.
1. It's opt-in, anyone that doesn't want to receive these reports, or has reasons to not want AI used on their project gets that by default.
2. It's free for OSS projects, many of us won't spend money for a hobby we work on in our spare time and give away.
3. The reports go back to the maintainer, and not to potential attackers.
I would like to see more locally run models in this space, breaking the dependency on SaaS vendors. Even though those local models can't be controlled and would therefore be used by attackers. At some point, we'll get past this wave of newly discovered issues that have been lurking in the code for years, and the scans should run like any other linter or dependency checking tool.
The question for me isn't "is this a bubble", it's "how many of these companies will be left after it pops". The few companies that remain are likely worth their current inflated value. But I'd want to see the back of the envelope math showing that all of the companies together will be able to earn the necessary profit to justify their valuations, how much revenue would that require, and how does that compare to the current tech purchasing today.
1. Address lookups. Many of the buildings in OSM have yet to get street addresses added, so navigating to an address is a bit hit or miss. This gets fixed with time as people update the maps and wouldn't be a show stopper.
2. Real time traffic and detour navigation. This is really needed when navigating around busy cities where a wreck on a major highway can result in significant delays. This needs a combination of an external service (separate from OSM) but also one that has enough adoption to have usable data.