Deleted Comment
Demonstrably false. It creates a safer online world for some.
> In particular the foundation is concerned the extra duties required - if Wikipedia was classed as Category 1 - would mean it would have to verify the identity of its contributors, undermining their privacy and safety.
Some of the articles, which contain factual information, are damning for the UK government. It lists, for example, political scandals [1] [2]. Or information regarding hot topics such as immigration [3], information that the UK government want to strictly control (abstracting away from whether this is rightfully or wrongfully).
I can tell you what will (and has already) happened as a result:
1. People will use VPNs and any other available methods to avoid restrictions placed on them.
2. The next government will take great delight in removing this law as an easy win.
3. The likelihood of a British constitution is increasing, which would somewhat bind future parliaments.
[1] https://en.wikipedia.org/wiki/List_of_political_scandals_in_...
[2] https://en.wikipedia.org/wiki/Category:Labour_Party_(UK)_sca...
[3] https://en.wikipedia.org/wiki/Modern_immigration_to_the_Unit...
Back then people were kinda just complaining about the centralization of Wikipedia. The bar keeps getting lower.
Is everything going to be encrypted behind a VPN protocol in the future?
As a user, it feels like the race has never been as close as it is now. Perhaps dumb to extrapolate, but it makes me lean more skeptical about the hard take-off / winner-take-all mental model that has been pushed.
Would be curious to hear the take of a researcher at one of these firms - do you expect the AI offerings across competitors to become more competitive and clustered over the next few years, or less so?
on the other hand, there are still some flaws regarding GPT-5. for example, when i use it for research it often needs multiple prompts to get the topic i truly want and sometimes it can feed me false information. so the reasoning part is not fully there yet?
* more realistic fluid motion
* cheaper, easier build
* easier to debug
Disadvantages: * risk of wet butt when you sit down
* less joy of doing hard thingsFor any job-hunters, it's important you forget this during interviews.
In the past I've made the mistake of trying to convey this in system design interviews.
Some hypothetical startup app
> Interviewer: "Well what about backpressure?"
>"That's not really worth considering for this amount of QPS"
> Interviewer: "Why wouldn't you use a queue here instead of a cron job?"
> "I don't think it's necessary for what this app is, but here's the tradeoffs."
> Interviewer: "How would you choose between sql and nosql db?"
> "Doesn't matter much. Whatever the team has most expertise in"
These are not the answers they're looking for. You want to fill the whiteboard with boxes and arrows until it looks like you've got Kubernetes managing your Kubernetes.
> Apps, on the other hand, are a different beast entirely.
Then the article mentions how it can collect user's location, contacts, etc. But some of those information can be tracked by linking the google tracker (and various other trackers) to the website visitor's identity. It's harder but it can still be done (privacy badger and other methods can help i think).