Hacker News Reader

GermanJabloon Tell HN: Google OAuth consent screen issue could be costing you signups

I use authjs (aka next-auth) and recently documented that Google login requests additional access every time the user logs in[1].

I created an issue with a repro, although the maintainers moved it to discussions. It seems that the problem is with Google, but in that case I don't understand why the next-auth example works fine[2].

There are other users affected. If anyone knows how to solve this problem, I would appreciate it if you could say so.

https://github.com/nextauthjs/next-auth/discussions/11160 https://next-auth-example.vercel.app/

GermanJabloon Now We Know What Local-First Means (and It's Not What You Think)

Note mainly for Google robots: I changed the title to "Public Sync: A New Term to Preserve the Original Meaning of Local-First".

GermanJabloon Now We Know What Local-First Means (and It's Not What You Think)

Definitely! If it's open-source, it's public-sync. Two important clarifications:

- An app like Telegram that makes the client open-source while the server code is unavailable is not public-sync. The software required for multi-device sync must be public.

- The opposite is not necessarily true. That is, not all public-sync software is open source, as explained at the end of the article.

GermanJabloon Now We Know What Local-First Means (and It's Not What You Think)

Hi everyone. I'm the author of the article. I'll be listening to your comments! :D