I wrote my first paper (nothing to publich, just for university) ever and went from typst to latest last minute because I got scared and went with the template of a studi-colleague. I heard latex was bad, but it's much worse than I could have ever anticipated.
I took the time off uni to migrate back to typst because I refuse to submit to the psychological warfare that is latex ever again.
It's possible that it is, but if someone tried to prosecute it, state secrets privilege would like be invoked, as it has been in similar cases, so prosecutors don't even try.
This was civil injunction & damages case. For court to declare judgement against Google (or any other company) someone needs to sue them. That's expensive and people in EU are not nearly as sue-happy as people on other side of Atlantic. Many courts in EU also have loser-pays model so there is huge financial risk in suing huge multinational corporation whose final legal bill might be bigger than person's lifetime earnings. And depending on country they might not even have personal bankruptcy available to discharge that.
This also heavily relies on recent CJEU ruling (WebGroup/Coyote, 16 June 2026, C-188/24) which essentially opened up the E-Commerce Directive's liability shield that platforms have been relying on so far. Essentially it said that that platform's are not necessarily neutral hosting providers when they control the algorithms that determine the dissemination. So I would expect more rulings to come, but it will take time.
I kinda disagree. Authentication is at OAuths core. You still need to authenticate to obtain a token and in more complex setups you don’t use it for authorization at all because tokens are stale immediately after issuing them. It’s why things like Zanzibar and OPA have been made.
It’s really not. OAuth makes zero assumptions about how you login - granted, the client credentials flow is a form of authentication if you will, but for the user perspective, OAuth starts when you’re signed in. That’s also why you can easily combine it with all kinds of authentication providers.
> OAuth makes zero assumptions about how you login
Neither does OIDC: "The methods used by the Authorization Server to Authenticate the End-User (e.g., username and password, session cookies, etc.) are beyond the scope of this specification."
OAuth makes zero assumptions about a lot of things, like even how you "authorize". That doesn't mean that authentication doesn't play a crucial role. While it doesn't specify how you authenticate the user it still specifies that you must authenticate the user. Outside of the authorization code flow, other flows strictly mandate that you should authenticate the clients.
It seems when designing Unicode most energy went into emoji. And there was nothing left for fancy things like fixed-length string buffers. The only explaination why UTF8 Buffers aren't compatible with UTF16 Buffers... is a really strong emoji...
I took the time off uni to migrate back to typst because I refuse to submit to the psychological warfare that is latex ever again.
reply