I have a RAM 1500. Even on the lowest setting, the AEB is terrible. It usually only activates when the vehicle in front of me is turning onto a side street and they will clear the shared lane well before I reach them. Even if they magically lost all momentum and came to a dead stop, I still have enough time and space to manually brake. Sometime I need to get around to unplugging the sensors in the bumper.
Only because we don't have many choices to choose from. This phone expands that pool to choose from. The next project/company will then be trying to aim for a subset of existing iOS, Andoriod, and Librem 5 users.
It'seasier to criticize anything for its shortcomings, rather than recognizing what it does better:
This is a phone that respects the user - not Samsung, Apple, Google, etc.
Reading all of the negativity, it sounds like people are implying we should never try because the first or second attempt will never have secondary features as goof as the mass market phones.
Remember: the primary feature is a phone that you truely own and can trust - you can't do that with the others.
The thing is that these aren't volume manufacturers with carrier buy-in we're taking about. The price is the work that went into the product. It's the same with say MNT. I'd love to get the Reform Next, but it costs more than a ThinkPad I know I'd use for a decade to come and has truckloads of battery life - or three second hand ones. Just the way she goes. Boutique vs. mainstream.
I've lost track of how many people said that about Brave re-instating or continuing support for Manifest V2. Turns out, no, the code base being open source is not enough to be able to maintain the changes your company needs
Especially if you're with fighting Google over their own code base
Brave wrote their own content filtering engine in Rust, it's more performant than uBO and other JS-based adblockers, so it pretty much eliminates the need for MV2 in Brave. Firefox doesn't have a built-in adblocker, so it makes sense for Mozilla to keep supporting MV2.
This is the key thing. Since practically nobody uses MV2 Brave does not really have a company need to support MV2. This means there is going to be less resources invested towards making sure it works and fully supported.
A hostile change can also be an API that apps start depending on.
You can of course re-implement the feature so it’s less hostile. But then again, why keep fighting an OS that is designed by someone who doesn’t have your best interest in mind?
>A hostile change can also be an API that apps start depending on.
That's already happening. Apps are using the Play Integrity API to block GrapheneOS. But GrapheneOS and their users have convinced some apps to officially support GrapheneOS. Roblox, for example, officially supports GrapheneOS.
AOSP is not anti privacy. They're adding helpful permissions like the local network just recently in Android 17.
>why keep fighting an OS that is designed by someone who doesn’t have your best interest in mind?
Most of the things people object to are not AOSP, but things from GMS (Play Services). AOSP does a much better job protecting the user via its security and privacy than other Linux distros.
Graphene can barely get the code (Google releases it less and less frequently). Being "open source" doesn't mean much when the copyright belongs to Google.
GrapheneOS only supports devices with an isolated cellular radio. Strong isolation for each of the radios is part of the hardware requirements for GrapheneOS. Connecting a radio via USB provides far weaker isolation and security than a mainstream device. Cellular radios in most mainstream devices are much better isolated than that already.
USB has a lot of complexity and immense attack surface in the Linux kernel. By default, GrapheneOS blocks new USB connections while locked at both a hardware and software level followed by disabling USB data at a hardware level when existing connections end. It would be a problem if internal components used USB. It's theoretically possible to rewrite all the Linux kernel USB controller, protocol, peripheral and gadget drivers in Rust along with isolating those but it hasn't been done and it's a massive amount of code riddled with vulnerabilities.
Isolation for the cellular baseband is an industry standard feature and has been for a long time. Mainstream devices have much better isolation for this than connecting it via USB. Even the earliest devices supported by GrapheneOS including the Nexus 5 had isolated cellular. Nexus 5X and the first Pixel phones began properly isolating the Wi-Fi/Bluetooth baseband too. Isolated radios are part of the hardware requirements for GrapheneOS supported listed in the official requirements:
The openness which allows you to do so imparts a certain level of trust in itself. People with stuff to hide don't tend to open source their work.
There's no way you can check everything, but you can check some things, and others will check elsewhere directly or indirectly. You'll never get to 100% certainty, but you can move a long way from 0% certainty.
There have always been cameras all over the place. Traffic cameras, wildfire cameras. Since the actual camera is doing the exact same thing as these other camera (filming in public) there is nothing illegal about them. To make them illegal would also require anyone pulling out there camera and saving a private video illegal. Look the public should assume they are always being watched. If they don't want that, stay in private areas. I would rather not just get downvoted for this unpopular opinion but debated - but with merit. We're not going anywhere if we just say boo hoo you suck and downvote. These cameras are legal (right now).
Flock does not merely sell or lease cameras, it operates them. In that respect, they are acting as an agent of the government, and hence could be seen as being party to fourth amendment violations (assuming one could successfully argue that such violations exist). Of course, first you need someone with standing to sue...
A better example would be if you are served with a restraining order by your ex-spouse, but then hire a private detective to follow them around in public.
The private detective isn't breaking any laws (assuming they're doing their job correctly and legally), but you are certainly violating your restraining order.
And as it should be illegal. Using a proxy for your illegal activity is generally also illegal because the law recognizes how dumb it would be if it weren't.
In many case, no, Flock is an active participant in it.
In many states, agencies can't contract with Flock to have them initiate certain data sharing (i.e. build out cameras and connectivity).
In some cases, though, if Flock "just so happens..." to have that data available, then the agency is free to contract with them, and then can have access to it - they just can't be the one to request it.
So, while yes, the agency still holds the burden, there is a lot of "nudge nudge wink wink so if we just get set up here through someone else, you could then sign a contract with us!"
We've already seen city meetings where there are cameras and no-one knows (or seems to know) who the actual agency-of-record is for a given installation.
reply