I’ll bet 1 internet point that they never vote anyone but republican for the rest of their lives even after this. The ones who don’t get deported of course.

Smaller cells have less energy to expend if something goes wrong, making it easier to control thermal runaway.

Part of the problem with other OEM vehicles is they are using large pouch cells which are prone to being damaged by their very nature, and if something goes wrong there’s significantly more energy per cell to deal with.

People don’t really care about the cells in their car, but they should.

I’ll never own a pouch cell vehicle. Prismatic or cylindrical only.

Edit: and the only reason people were using them years ago was there was no other options with enough supply. It wasn’t because it was the right choice. Many OEMs are now moving away from them.

Ice agent threateningly approaches person holding camera yelling at them to stop recording. While waving his hands around in anger his arm touches the camera person.

Charge: Felony assault on a police officer.

checks post, 9h

sets VPN to UK

I support Palestine Action

I have a lot more faith in SaskTel succeeding here than if its been given to Rogers or Bell.

All push notifications go through APNS on apple. That’s Apple Push Notifications Service.

APNS requires the device to authenticate with it and can uniquely identify the device by an id. Its how it sends messages to devices.

Firebase cloud messaging acts the same way for true push notifications.

You don’t need to audit a device using APNS or FCM on Android to know that it is not anonymous.

Ya, for sure. My beef was just with people saying you can roll your own, but glossing over the reduced user experience and reliability if you do.

With those trade offs it’s absolutely doable and makes sense for certain situations.

Ya, it can be brutal on battery.

I worked on an app once where delivery was critical, so we gave them the option of the active service+websocket, but for them the trade off was acceptable.

Pushes can be pretty flakey given all the shenanigans OEMs do on the device, even when marked as high priority correctly.

And the even worse part is when OEMs reset battery saving flags the user had set to help pushes get through and they stop working one day because of it.

Every few trips to Costco already seems too often, but it is delicious.

They don’t treat their people like shit, they treat them like slaves. In countries outside China at that.

https://www.bbc.com/news/articles/c3v5n7w55kpo

It’s actually not possible to build a push service like FCM or APNS on Android and have it function at the same level as FCM. FCM has special permissions to bypass certain device states on the device to ensure message delivery that nothing else can match.

The best you can do is approximate it with an always active websocket and a foreground service always running with battery optimizations disabled, but good luck not having that foreground service shut down on occasion as well. Devices are hostile to them for battery saving purposes. You’d have the best luck with a Pixel device though for something like that. You could also do some sort of scheduled background polling, but the device can be hostile to that as well, and it would eat more battery.

You don’t even need to audit a closed source app to know that Apple knows which devices its sending pushes to. It works because they know.

I think he thinks HE had to store the information, and if he isn’t the one storing it, it’s anonymous.

Except, on Android, you can also do it where only google stores the information and he doesn’t have to store any. And there are no user name or passwords or accounts involved to listen to specific channels like he claims.

You can collect this information, and you’d be able to write a more custom push service, but it isn’t needed at all, but Google and Apple will always know who is getting the messages.

Now GrapheneOS the privacy based Android OS is calling them out

https://bsky.app/profile/grapheneos.org/post/3lt2prfb2vk2r

He really must be thinking just about himself, and not that Apple had the info.

There was an issue with running the dock on anything but their cable or something like that ya.

You left off the part where after you finish the bag of skittles the lay you off again.

Any of the games that aren’t fully on the cart, require a download to even function in the first place.

It’s looking like (TBD) that this is how a very large portion of the games are going to be delivered.

When the physical games require downloading to start using them, I think that starts crossing lines into bricking territory even if it’s not entirely accurate.

Just figured I’d add Apples own documentation as well

https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns

Apple Push Notification service (APNs) must know the address of a user’s device before it can send notifications to that device. This address takes the form of a device token unique to both the device and your app. At launch time, your app communicates with APNs and receives its device token, which you then forward to your provider server. Your server includes that token with any notifications it sends.

No, you’re right, GOOGLE will take the device identifier, but him talking about how he would need to store it, and especially for channels where he talks about user names and passwords really makes me think that he thinks he personally has to do it, with his own backend storing it. (edit: The point is, that he doesn’t HAVE to do it this way. You can, and it gives you more control, but you can let Google do it all. It’s never anonymous with anyone though.)

Apple knows which devices have the app installed. They would be able to link that back to the device if it was demanded, even if it is a bit more obscured.