141–150 of 467 posts
Earlier quoted context omitted.
Not the worst choices!
Indeed. However, in terms of the independence, better choices exist.
Earlier quoted context omitted.
> The company making a device that is licensed by the FCC has to do everything that they can to mitigate the risk of an unlicensed broadcast on their devices. Where do you see this in the rules? The only thing I see that even comes close is the following sentence: "Manufacturers and importers should use good engineering judgment before they market and sell these products, to minimize possible interference" Maybe it's…
SDR for listening does not require a license. For transmission, depending on the power and frequency may require a broadcast license. https://www.reddit.com/r/RTLSDR/comments/dx5sln/do_developer... Depending on the power of the walkie talkie, it may require a license. https://www.rcscommunications.com/which-two-way-radios-requi... > MURS (Multi-Use Radio Service) – Two-way radios programmed to operate within the MURS…
Earlier quoted context omitted.
How much do you want to pay? Who will be paying? Big companies will probably laugh such an effort out of the room, nay, they will not even let you into the room to talk with them.
$10 million dollars per app. The creator of the new OS will pay. If you offer enough cash they will stop laughing.
https://tbot.substack.com/p/grapheneos-new-oem-partnership > GrapheneOS has officially confirmed a major new hardware partnership—one that marks the end of its long-standing Pixel exclusivity. According to the team, work with a major Android OEM began in June and is now moving toward the development of a next-generation smartphone built to meet GrapheneOS’ strict privacy and security standards.
Oh that's one of the best news in the smartphone world in a long time. It's impossible to escape the Apple/Google duopoly but at least GrapheneOS makes the most out of Android regarding privacy. I still wish we could get some kind of low resource, stable and mature Android clone instead of Google needlessly increasing complexity but this will over time break app compatibility (Google will make sure of it) Edit: I do…
0. A privacy first approach would be something like this:
`You+App --Read/Write-> f_private(your_data) Think of Yelp/Google Maps but with no _read_ permissions on location, functions can be run in a private middleware e.g. what's near an anonymous location or ads based on anonymous data. You can wipe your data from one button click and start again for EVERYTHING, no data is ever stored on a 3p server. Bonus: No more stupid horrible permission fiascos for app development that are just plain creepy.
1. An opensource data effort that can support (0) with critical infra e.g. precise positioning, anonymous or privacy preserving functions that don't reveal their data or processes to 3p.
Here is my favourite open source effort: Precise Location Positioning. A high recall, opensource, 3D building and sattelite-shadow Data-Infra effort[3]. This world class dataset on shadows and sattelites are a must. Most geo-location positioning tied to Radio signals is just a bandaid and fraught with privacy issues — thought there are heroic privacy first efforts in this direction[1][2] which though amazing will be playing catch-up with google already deploying [3].
[2] https://github.com/wiglenet/m8b
[3] https://insidegnss.com/end-game-for-urban-gnss-googles-use-o...
Earlier quoted context omitted.
Graphene uses the Google codebase, so Google is choosing its long-term development strategy and standards it will support. It's like choosing Chromium to escape Chrome.
The same can be said about the Linux codebase. Tomorrow Linus could private his branch and stop supporting public releases. If AOSP goes closed source then people can fork it and continue to maintain it.
Earlier quoted context omitted.
$10 million dollars per app. The creator of the new OS will pay. If you offer enough cash they will stop laughing.
Where do you think the creators will get this money from? Look at existing ones, they are cash strapped as they are, paying a million to get an app over beyond their budget, let alone 10 million
Earlier quoted context omitted.
You're getting a lot of indirect responses. If you've ever tried to mod your android phone the answer is simple. Its google play services and hardware attestation for things like banking websites. Its really easy to make a custom rom but hard to do serious "real life" stuff; companies don't want to make it easy. To most regular users, if they cant download apps from the google play store, and they can't use venmo\cas…
This just shows that the barrier of entry of a new phone OS is more than $0. You can pay app developers to port their apps off of play services, you can pay developers to add support for your attestation keys. Considering how many billions of dollars Android makes for Google, there is a room for a return on investment for an alternate OS to enable investments into a new OS.
We actually saw this play out twice with Microsoft's return to mobile (Windows phone) and web browsers, money is a pretty small part of it.
Earlier quoted context omitted.
This is really cool, but, longer term, what happens if Google makes android closed source? I feel this is a very real risk.
They won't because they literally control the mobile market by having Android open source.
Earlier quoted context omitted.
How much do you want to pay? Who will be paying? Big companies will probably laugh such an effort out of the room, nay, they will not even let you into the room to talk with them.
$10 million dollars per app. The creator of the new OS will pay. If you offer enough cash they will stop laughing.
Trying to get some scale, you're hypothesizing about giving 10 millions to HSBC to make business with your startup, when they're throwing away 500+ millions every year just to cover their money laundering.
https://www.investopedia.com/stock-analysis/2013/investing-n...
And we're discussing doing this for basically every major banks.
I notice my battery life is much better switching to graphine from the stock google rom.