Live data from Hacker News

Nitter is working again

github.com

101–102 of 102 posts

Re: Nitter is working again

#101
post #94
post #84

Earlier quoted context omitted.

They already have a device specific ID, this isn't asking for a new ID. See the link above. It's not considered a fingerprinting mechanism because it's only specific to a device/app-vendor pair, so can't be shared to fingerprint across apps. The problem is you can't use it for rate limiting because a bad actor could just generate a random ID and use that. That's why an endpoint for validating a given ID was issued fo…

Now you have Google dictating who can make Android phones that actually work. That has to be in violation of GPL somewhere.

Uh what? Nobody is saying Google needs to be in control. Where did you even get that from?

Re: Nitter is working again

#102

This is like the analog loophole. If data is transferred from Server to Client, it's always possible to scrape. Though Apple is trying to make this harder: https://developer.apple.com/documentation/devicecheck/prepar...

I am not an iOS dev. What is the significance of App Attest wrt the loophole used here?

With attest, Twitter can tell if there's an actual mobile device hitting Twitter with that bearer token versus today, you can spoof the client and unless they fingerprint the IP address or other subtleties, it's hard to distinguish fake traffic from real traffic.
Post reply on HN