sgoto

Automatically verify email addresses with cryptographic proof rather than manually via OTPs

You should take a look at https://github.com/WICG/email-verification-protocol and https://github.com/w3c-fedid/FedCM ... they also share a lot of the historical lessons learned with Mozilla's BrowserID.

Live tweeting here: https://bsky.app/profile/sgo.to/post/3mge7u5pczk2j

https://code.sgo.to

Verify email addresses automatically

Yeah, websites can choose any other identity provider, and in fact, do.

This sounds super interesting! I'd love to beta test it if you are looking for people to try!

You can find me at:

http://twitter.com/samuelgoto

Own your own domain? Want to Sign-in to websites with it? Register it with the browser!

Instructions:

https://github.com/w3c-fedid/idp-registration/issues/2#issue...

At this point, wouldn't "email authentication" simply be OpenID?

https://code.sgo.to/2019/08/01/the-axiomatic-force-conjectur...

Fair point on the point on the term polyfill. Done, replaced it with "JS renderer" [1].

[1] https://github.com/google/typograms/commit/4270c0ad387a2b500...

Exactly.

Maintainer(!) here, reading the comments! Can you help me understand what you'd expect? I can't really find the "inductor" you are referring to and the "C" character that seems off to you. Care to expand a bit so that I can try to fix?

Neat! Want to send a PR with some of these diagrams as examples?

Many diagrams I am able to draw manually as I'm editing source code on emacs, but for more complicated ones I tend to use this: https://asciiflow.com . To each their own, so pick your favorite ASCII editor.

Done, merged a patch to clarify that it is absolutely the latter: this is an implementation from scratch with completely different rendering passes, design and SVG output structures.

Does that help?

https://github.com/google/typograms/commit/bdd329eaec7497b96...

What's the relationship between passkeys and OIDC/SAML.

Previously submitted in personal repo:

https://news.ycombinator.com/item?id=32133345

Now, officially open sourced:

https://github.com/google/typograms

A few early explorations on a similar idea:

https://code.sgo.to/2021/07/02/english--.html https://code.sgo.to/2020/08/31/syntactic-theory.html https://code.sgo.to/2020/09/16/semantics.html

Some of us are proactively working on this problem [1]. Not trivial, but I think we are making forward progress to reconcile and mediate login in browser UX.

[1] https://github.com/fedidcg/FedCM/blob/main/meetings/2021/Web...

Ok, submitted a quick fix here:

https://github.com/samuelgoto/typograms/commit/40829f6db1a21...

That looks like a bug, thanks for finding it!

You are welcome to send PRs if you have the inclination!

https://github.com/samuelgoto/typograms

Mine is a massive amount of fun to me. I learn a massive amount from it: https://code.sgo.to/.

Ha, interesting! Any chance you have a link handy with the problem? Can you expand on what you mean by "head and body tags around the appropriate sections"?

Ah, fair, will add that to the list. But, IIUC, isn't GoAT just a go port of markdeep (which I acknowledge in the related work section)?

On YAML-like diagrams, I think you are looking for mermaid [1]. I wrote down here [2] how typograms compare to mermaid [2] in terms of trade-offs.

[1] https://github.com/mermaid-js/mermaid [2] https://code.sgo.to/typograms/#related

I don't think I expect people to edit the diagrams on webpages, rather than locally using their favorite text editor.

Yeah, agreed that they are hard to edit if you working by yourself, but disagreed if you are working collaboratively.

On "may be like an IETF proposal."", that's precisely where I've been using them the most :)

https://fedidcg.github.io/FedCM

Not for everybody, I agree, but it is kinda of ironic that you mentioned "may be like an IETF proposal." :)

Also, technical blog posts, e.g.

https://code.sgo.to/2022/04/11/metamath.html https://code.sgo.to/2022/04/28/siop.html

That's precisely it. I wrote down a bit more down below.

"Why is it better to write diagrams by hand rather than use a tool (e.g. inkscape, google docs) and export as SVG?

Because it requires everybody that wants to edit the diagram to (a) use the same tool and (b) have access to the original source file (e.g. the google doc)."

https://twitter.com/samuelgoto/status/1548878038833692672

FWIW, I explained a bit why/how I've been using it here: https://twitter.com/samuelgoto/status/1548845628171722752