Stefan Peters

[This site](https://support.apple.com/guide/safari/prevent-cross-site-tracking-sfri40732/13.0/mac/10.15) says the following: > Unless you visit and interact with the third-party content provider as a first-party website, their cookies and website data are deleted. So that explains...

https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/: > If yours is among the few websites that still relies on third-party cookies in Safari and has not been affected by ITP in its previous iterations, here’s how...

It is already possible in login-client with `LoginClient.errors.ThirdPartyCookiesBlockedError`. This issue is about fixing the problem. I'm 99.9% sure that there is a solution since other services are doing it as...

Since Chrome (Chromium) also plans to abandon third-party cookies completely, we need to find an alternative, long-term solution for this issue. Here are some resources we might look into for...

If a user logs into an account which is not yet connected to an existing user account (i.e. a new account would be created), we could add an additional page...

Since this issue requires some changes in application flow (as mentioned in my previous comment), I would suggest moving it to 0.5.0 (or maybe to a 0.4.1).

I wonder if this is really necessary. It already says on the login page: > If necessary, a new user account will be created on first login. The only use...

Alternatively, we could add a `stats` property for the `/about` endpoint.

Currently, I have implemented it within `/about` like this: ```json "statistics": { "userCount": 4, "userCountByProvider": { "local": 2, "github": 1, "stackexchange": 0, "easydb": 0, "wikidata": 1, "orcid": 0, "testscript": 2...

Yes, it also applies to Wikidata, and yeah, that makes sense. I'm not sure about the application flow though. Also we'd need to have a way for the user to...