dracs @ dracs @programming.dev

Posts

0

Comments

112

Joined

2 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.

I they're going to need Mr. Squiggle to make those lines look like something coherent.

They do have e2e for emails. Any emails between Proton Mail users are always e2e encrypted, as are any emails others send you which they've encrypted with their own maio client. If someone sends you an email unecrypted (most email is), then Proton will encrypt it for you and put it in your inbox. They can't read it after that, but there is some trust required that they don't store/look at the unecrypted email before then.

I bought some gray imports a couple of months ago. Cost me about $100 more than Valve's official AU prices, for the 1TB OLED.

My partner and I have been playing them both pretty much constantly since then. Very happy with them.

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.

She'll independently recycle your matter into more coffee.

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.

It's a good game. Just don't take the content warning at the start lightly. I've tried to finish it twice but haven't been able to get more than a couple of hours in.

My bonus just came in today. Was planning to order one of these this week. Not sure of I'll wait to see what's happening at PAX. All they've said so far is that Steam will be there.

Probably don't need to scrape it. Just query WikiData for it

https://wikidata.org

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.

It's a bit similar. However this goes a bit further than I understand those projects do. They're creating a game like the original. With this decompilation project, if you use the N64 compiler you will get a ROM which is 100% identical to the original.

The ROM in this case is only used for game assets, like maps, models, and textures. All the game logic in native code. This allows is to be easily modified to add in new features without trying to hack it into a 20 year old game/console.