Skip Navigation

Posts
10
Comments
1,253
Joined
2 yr. ago

  • It appears phones as old as the Android 8 era can support this and phones that shipped with Android 13 or newer always do. I had the impression it had been universal a little longer.

  • No, Google is also trying to stop hobbyists running custom builds from accessing services built on their software (the aforementioned SafetyNet). Hackers keep finding ways around this, but Google keeps trying to lock them out.

    That's a side effect. If Google really wanted to interfere with hobbyists, they would mandate hardware-based attestation and all the current workarounds would be broken. It would be much harder to create workarounds for that.

  • If manufacturers had their way, there wouldn’t be any phones for one side.

    There's nothing stopping manufacturers from permanently locking the bootloader. Some do and others don't suggesting that the industry does not have a universal preference.

    I do think Google wants it to be inconvenient enough to run a version of Android they haven't blessed as one's main phone that it has no chance to become mainstream, but that's about the prospect of an OEM not bundling Google's apps and store, not hobbyists running custom builds. If that sounds like an attempt to use market power to exclude competitors in violation of fair trading laws in a multitude of jurisdictions, you might be on to something.

  • This is usually coupled with the expectation that I'm going to use some special knowledge to do it rather than just pasting the contents of the error message into a web search and following the simple instructions contained in the first link.

  • Your point seems to be that the fine is about two days profit.

    If you did something illegal and got fined two days pay for it, that would probably get your attention. You might think twice before doing the thing again. If not, the EU can fine them a larger amount next time.

  • It is, and it looks like the bad press got to Google and it will soon be fixed on Play Store.

    I'd generally recommend getting things from F-Droid where possible anyway, but that could be a tech support headache for a larger institution using Nextcloud and requiring people to install the client.

  • I think this is a cooperative between the people who own the units in the building to handle building maintenance and the like, not a gang to bully neighbors who don't make the same landscaping choices OP would.

  • They probably will once it's not in early alpha as the readme says it is.

  • If you're hosting it yourself, ActivityPub is a separate component. If someone else is hosting it for you, they will have to add support.

  • It sounds like you want an RSS feed of the singer's events page on their own website.

    In 2025, they might not have one because social media has replaced that (poorly), but in 2010 they probably would.

  • Google could theoretically build a Google Messages counterpart to iMessage and skip the Carrier as the middleman, but then it wouldn’t be interoperable with iPhones since it wouldn’t be an “open standard”

    Google did that, in 2013. Hangouts was briefly the default SMS client on Android, and it would upgrade conversations from SMS to its protocol when available. It was available for iPhone, but couldn't be an SMS client there.

    Rumor has it, carriers whined about it, and Google caved out of fear they would promote Windows Phone devices instead. I think that was a foolish move on Google's part, but I think I'm glad Google doesn't own a dominant messaging platform.

  • It encourages hot takes over nuance, or awkward workarounds like replying to your own post a bunch of times if you actually have something to say.

    I still think it's a terrible idea for something like that to be popular and have an important role in society, though its addition of images and video mitigate the problems a bit. I don't know whether it significantly impacted the platform's success and eventual sale price. $44B is a lot of money, so I can't say it was a terrible decision from the perspective of its creators.

  • Twitter. I always thought a text-based blog-like thing with a short character limit was a terrible idea.

  • When I read "privacy nightmare", I think of a system collecting or revealing information without the user's knowledge. As I understand BeReal, the user understands exactly what information they're sharing, and with whom. That said, I'm puzzled by why anyone would want to participate on either side.

    Here are some things I might be doing in any random time window in which such an app might prompt me to share a selfie:

    • Eating food, usually not interesting food foodie friends would like to see
    • Walking, usually somewhere pretty boring
    • Sitting on the toilet
    • Writing code at my computer (often code someone is paying me to write and wouldn't like included in a social media post)
    • Picking dandelions to feed to the goslings at the park

    I don't want to share any of those activities with my friends. If we're catching up on life in person, I'm not going to talk about any of that. If any of my friends do want to see those moments, I'd find it weird and voyeuristic.

    The interesting moment I do want to share, and people might actually want to see is the close encounter with the wild gosling taking the dandelion leaf from me.

  • They bullied Syncthing the same way. Fortunately, Syncthing-fork is still developed and available on F-droid.

    I understand a well-curated app store (which Play Store is not) placing some limits on apps getting all files access. In a modern security model, that's not a permission most apps should have, however synchronization and file management apps obviously should have it.

  • Perhaps we should send powerful politicians who sexually abuse children there.