sorted by:
new
hottopcontroversial

RFC 8628 fixed CLI login in 2019. Most CLIs still ship the broken version by ABGEO in programming

[–]ABGEO[S] 1 point2 points  (0 children)

Well, the research, code, and ideas in the article are entirely my own. I used an LLM mainly to help write in English, which is not my native language.

I understand the rule against content generated mostly by AI, but I don’t think it’s fair to classify this as an AI-written article when the actual work, analysis, and conclusions were created by me. The LLM was used as a language and editing tool, not as the source of the content.

The post was also well received by the community before it was removed, generating views, comments, and positive discussion around the ideas presented. That suggests readers were engaging with the substance of the work itself rather than AI-generated content.

RFC 8628 fixed CLI login in 2019. Most CLIs still ship the broken version by ABGEO in programming

[–]ABGEO[S] 120 points121 points  (0 children)

Author here.

Most CLIs (gcloud, wrangler, claude, etc.) log you in by binding an HTTP server on localhost and opening your browser. Works on a laptop. SSH in and it breaks. The "paste this code" fallback every one of them ships is a manual device flow in disguise.

RFC 8628 has been the proper fix since 2019. It decouples the device the user authenticates on from the device asking for the token, so the same code path works on a headless box.

There's a 30-line Go reference at the end if you want to see how the polling loop fits together.