Here is a short list of things that Play Services do:

1. Scan for active malware
2. Nearby Share
3. App attestation (Required for banking apps)
4. Encrypted backup of your data
5. Autofill
6. All push notifications
7. Find my device
8. Basic telemetry (talked about elsewhere in this thread but it’s telling Google who you are and where you are)

Even if you remove all telemetry you’d need to have the services running 24/7 in the background maintaining a socket connection to push notification services.

CMV: all Linux files should be case insensitive, displayed as lowercase and mandatory snake_case.

Steam is not a publicly traded company, so they don’t pull this kind of skullduggery in service of the shareholders.

They’re a company full of people who, gasp, like video games: unlike the average navel gazing, brainless, Harvard Business School CEO.

Given their track record they’ve been more consistently “pro gamer” than other companies and are given a lot of leeway for that.

It’s a dangerous command - I’d rather not run it by accidentally hitting the f key a second time.

If it’s not using GCM then it must be long polling, unless signal servers are set up to use a 3rd form of push (APNS for iOS, GCM for Android)

You missed the point:

The original creator of a thing does not control the current usage.

It’s analogous.

Theory is fine but in the real world I’ve never used a REST API that adhered to the stateless standard, but everyone will still call it REST. Regardless of if you want it or not REST is no longer the same as it’s original definition, the same way nobody pronounces gif as “jif” unless they’re being deliberately transgressive.

403 can be thrown for all of those reasons - I just grabbed that from Wikipedia because I was too lazy to dig into our prod code to actually map out specifics.

Looking at production code I see 13 different variations on 422, 2 different variations of 429…

403 is a category, not a code. Yes I know they’re called http codes but REST calls are more complex than they were in 2001. There are hundreds of reasons you might not be authorized.

Is it insufficient permissions? Authentication required? Blocked by security? Too many users concurrently active?

I’d argue the minimum for modern services is:

403 category
Code for front end error displays
Message as default front end code interpretation

As json usually but if you’re all using protobuf, go off King.

I’m a professional android dev so I popped over to their open source project to see if there was any UI changes I could make to help out the cause.

… The whole fucking project is lua.

So I can’t help them: they appear irredeemable tbh.

They wanted to make one UI for all platforms. That will always cause issues.

TIL KOReader.

I think staying with Kobo is a solid idea but it depends on if you’ve liked your device or not.

I like my 5 year old Kobo Libra H2O - it looks like the new color Kobo Libra is a pretty big upgrade to that that looks like it’s in your budget.

Q: What’s less funny than an explained joke?

A: Someone bitching about explaining jokes

Such cringe behavior

Ahhh pre-fent cops were still blaming drugs for their unseemly public panic attacks

1. Tiktok is a company comparable in scale to Google. 130Bn in revenue last year.

2. Patreon is nowhere near the scale of YouTube. But I also think it’s the only viable solution to privacy and supporting creators.

It’s impossible to do without exposing a private signing cert to everyone, yes. That’s the issue.

You can’t do asymmetric key signing anonymously and with a central issuer.

So either you have to just trust the assertions (0 security) or you have to have a trusted issuer (not anonymous)

A pseudonym issuer is a trusted issuer. There’s no way to do it otherwise. You have to trust someone to make this kind of system work.

Agreed that law enforcement should not be involved but the quote I posted was also from the article and it seems impossible.

Most of these make sense and are definitely blockers for this ever releasing but -

Remove the concept of the Pseudonym Provider and ensure pseudonyms are generated and stored locally without the possibility of linking back to real identities.

Correct me if I’m wrong but this data all has to be signed somewhere right? Like the eID contains cryptographically signed assertions about the user in some standard (JWT?) format.

What use is signing the assertions locally? There would be no way to tell if the citizen actually had any valid id at all. A pseudonym provider is the privacy layer that allows for signing of new tokens after ensuring the validity of the old.

How could you sign an anonymous token using a valid one without it being linked back to the valid one? It seems like impossible constraints.

Am I totally off base here?

Prompt engineering isn’t a real field bro

It’s unclear if the current models can reach that level though. They seem more like they’re asymtotically approaching their limit.

Maybe I’m wrong and GPT 5 will be the end all and be all - but I don’t think generalist models will ever be consistent enough. Specialist generators focused on specifics, trained to output very defined data seem more likely to be useful than this attempt to make a single catch all LLM.

Gpt 4 premium pictures still have these major issues.