There was a whole term called “branching strategy” to handle things way more complex than a quarterly release - this is about nothing more than control. Bet it will be one to zero releases next year. They’re speed-running enshittification before a worthy open replacement can be written.
Add-on: cell phone nerds that test carriers for sport.
No worries, and no neg either. This is where this timeline sucks. Quick Share is a great upgrade to the standard Bluetooth file sharing that existed for 20+ years as it adds in WiFi, but corps are all so walled-garden-metadata-stalking vampires. These companies are so stupid. Conflict too, in that sharing files easily can “make money” for them, but they’d rather fight than have standards.
I miss standards. Plugging a POTS jack in a wall and getting a dial tone was so simple. Now, everything, even “cable TV”, is JSON shitting around the Internet, but heaven forbid it’s the same JSON.
You should see them with a kerosene lamp.
Bloody game changer, that. Been little by little whittling away at apps until the Play Store can GTFO for good.
Google Fi definitely has a smooth experience, even to/from pSIM, eSIM, and no real need for special SIM features. They implemented that very well. Now, every tier 1 carrier in the US, eeeeeeek!
Requires Play Services.
Surprisingly, Apple. https://www.apple.com/diversity/
Not trying to sound pro-them, to be clear. I just use that page as a Fascism canary.
Until you have to move them to another phone. Especially if there is special provisioning on the SIM that you have to call the carrier to provision every time a new eSIM is issued, since few scenarios let a direct eSIM copy occur. (Apple may be the only one.)
including on the recently revived file-sharing service LimeWire.
Interestingly enough, the article fragment in the post explains that part. But yeah, had the same reaction initially.
Web scraper sues web scraper, “we were here first, waaah.”
EDL (Emergency DownLoad) mode on Qualcomm chips, I’m sure other chipsets have a similar mode. The chipset actually does it, the hardware manufacturer just has to support it.
It is a pretty cool fallback mode.
If only tech companies weren’t assholes and actually developed desired features instead of the shit they have wasted our time with…
They know they are the only choices, and so they shall work together to maximize that revenue stream.
GrapheneOS, the privacy and security focused aftermarket operating system, has received an experimental build for the Pixel 10 series
Received? GrapheneOS are the authors of their software, they don’t receive. Curious how they got the binary blobs to get it to function.
That “article” is terrible, and doesn’t even touch on the crucial issue - the crux, as it were. Android is one thing, hardware support is the magic piece Google is trying to remove to close their borders and kill creativity forever.
Rooting for Pixel 10 native support over here, but was it an employee leak? Similar hardware driver copypasta with modifications? Did Google just finally share the necessary binaries legitimately?
This whole thing is so vague.
They’ve woven Android so deep into open-source projects, there are likely legal commitments they have to slowly back out of, similar to how Qualcomm once drove CodeAurora Forums (https://bye.codeaurora.org/). Don’t worry, they’ll get there. This time window has to be used for designing an escape hatch to something just Linux-based.
My favorite part is claiming such horse shit on the heels of dragging every general on planet Earth to Washington DC just so he can masturbate in front of them.
Wow, that’s an interesting one, thanks for that. That would be quite annoying to deal with.
In that case, since the 2FA is coming from the carrier, if you can disable 2G and 3G on your handset, the air link on LTE and above is AES-based encrypted at least, if the carrier configures it correctly, even though the channel itself often isn’t. Or if very paranoid you can use WiFi calling in airplane mode on a burner so the carrier sends the message over the wifi calling IMS-encapsulated-in-VPN-connection over the Internet.
The chance of someone being able to intercept that 2FA code in a way that could get into your bank account is pretty much absolutely scant.
Not trying to change how you do things either, though. Just knowing how terrible some banks can be at writing software, I’d be more apt to trust “weaker” methods versus apps. The future is quite exhausting.
They don’t need your permission to gather all sorts of data from most modern smartphones, nor can you really deny some of it. (Some you can, like camera, and microphone, allegedly.) Part of the whole banking<->handset manufacturer agreement also frequently allows “special access” outside of the traditional user-permission security model. For…“security” to “prevent fraud”.
I never mentioned horses. You also never mentioned rotary phones. Knowing how to grout bricks would also be on the table, and those are everywhere in European towns.
Also, if it wasn’t clear, both @OneWomanCreamTeam@sh.itjust.works and myself were just making an “obvious” joke of sorts. It isn’t to insult people that do not know things, it is just a statement of: “obviously people that never used a thing have no idea how to use it.”
I would actually prefer all people can learn and know stuff. I like that I know how to start a crank-start tractor and also how to shut it off by shorting out the magneto (although I hate transient energy from the spark going through the body). I don’t use it as a joke or something I talk about, I just know it because I happened to learn it.
Want to learn some techniques to split wood with an axe? I can teach! I also can teach how to mess with a JSON API on a web site to get the data I want when the vendor doesn’t know how to use documentation, or flash firmware on obscure hardware, or set up a mesh network, or build a ham radio antenna from random metal, or cross-compile an open-source CPAP analysis app using old QT APIs and modifying them to support modern platforms, yet can’t find contact info with the vendor to let them know how to do what I did so they can compile for ARM Macs. Knowledge flows both ways.
TL;DR: Was a joke.