Hacker News new | past | comments | ask | show | jobs | submit login

IMO Brave should remove this API, then.

- It's not likely to work anytime soon

- "The property doesn't exist or throws an exception or does something else that Chrom{e,ium} doesn't do" provides the necessary fingerprinting

- Adding the feature back later can just be chalked up to "growing pains", it doesn't really set especially unique precedent






Absolutely they should. But they haven't. Checking the UA string allows a developer to get around the issue, but once it's gone an individual developer will be powerless to fix the issue for their users.



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: