Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D
Posts
0
Comments
79
Joined
3 yr. ago

  • The reason that Google got ruled against originally was that they were paying and offering incentives to developers to keep them from releasing their apps on other app stores.

    Google also doesn't support a user installing the Play Store themselves (and the required Google Play Services dependency). So phone manufactures have to choose to include it on everybody's phone from the get go, or their users won't be able to use it at all.

  • The UnifiedPush server is intended to be a single source your phone can keep a persistent connection open to, rather than needing a connection per service/app (this is how Google's Firebase notifications work too).

    As Signal doesn't support UnifiedPush, MollySocket keeps a permanent connection open to Signal's servers to listen for new activity and forward them to your UnifiedPush server. This saves your phone keeping a permanent connection open to Signal's servers and draining your mobile battery more.

  • I'm self hosting both too. MollySocket's docs are pretty clear that it never gets an encryption key for your account, so it can't read your messages. It only gets/forwards alerts that something happened on your account AFAIK. So I'm not sure what data it has that's worth encrypting.

  • For Signal/Molly, it's less that the notification is encrypted as I understand it. It's more the notification content is just "Hey! Stuff happened" for Signal. The app then reaches out directly to the Signal servers to see what's new. So the message content is never sent via the push notification service (UnifiedPush or Google's service).

  • I've got a few old PCI cards around somewhere. I should pull one of them out and give them a try at this.

  • That would require a lot of data privacy concerns to be addressed. Even if it's an explicit opt-in. The current method uses sample text which can't include PII. Using user supplied text would almost guarantee they'd get names and other PII in their data set.

    I also imagine it's harder to train the model when you don't know exactly what the user was trying to type. I.e. Was the swipe detection wrong, or did the user delete the word because they changed their mind on what to write?

  • The issue isn't a big deal for the average user. The vulnerability required them to first get your username and password, physically steal your Yubikey, spend half a day using $10-15k worth of electronics equipment to repeatedly authenticate over and over, they then could potentially make a clone of the key.

  • I'd say it's worth doing this regardless to help determine if it's an application or system issue causing them not to go off.

  • When I migrated emails last time, I setup my old email to automatically forward to the new email. Then on my new email, I setup an automatic label for any email that was addressed to the old address. Every week or two I'd review what was sent to it and either update the email address used or unsubscribe. Eventually it got to a level where I wasn't getting much at the old email anymore and finally deleted it.

  • I'm just using Mozilla's Multi-Account Containers extension. In my work's infinite wisdom I have a total of five "single sign on" accounts. So I have different containers for each account so I avoid the endless "which account would you like to use" and "this account doesn't have access to this resource".

    The extension allows me to set specific domains to always open in container X. That covers 90℅ of my use cases. Some sites I need to use different accounts with and for that I have to select which one to use each time.

  • The page says it captures game audio only by default. But you can switch it to all audio if UPI want to capture something like external voice chat.

  • I know GrapheneOS implenents Contact Scopes so you can choose which contacts an app can see.

  • Bridge doesn't support the calendar yet from what I've heard.

  • You can get notifications in other profiles. However it'll be a generic "Profile X has a notification". Tapping it will swap profles, but not exactly seamless.

  • It's not that it's closed, it's more that none of the exiting email protocols support a server which can't read your email (as it's all encrypted). They do offer Proton Bridge which you can run locally which will handle all the decryption and local mail clients can talk to that as the would any other mail server.

    I don't know off hand if it supports calendar syncing though.

  • Removed

    FUTO Keyboard app

    Jump
  • I'd say the main benefit Futo has over Heliboard is that it has native swype typing with its own model (and also own voice typing model).

    Still a bit light on customisation (certainly compared to Heliboard), but a nice first release certainly.

  • Proton is not the same as a VM. It has direct access to your filesystem. It could delete your entire home directory if it wanted to.

  • Another vote for Immich. It's a really nice experience on both the web and app.

  • Ah, so it isn't just me. I had noticed this myself recently.