shadowbanned4

6 ms·

1.
by shadowbanned4 3y ago
They do them with much less complexity than OIDC.
2.
by shadowbanned4 3y ago
HTTP basic auth, TLS with client certs.
3.
by shadowbanned4 3y ago
I hand-wrote the largest OIDC deployment in the world, after experimenting with other libraries. It is awful. Do not use OpenID, do not use OIDC.
4.
by shadowbanned4 3y ago
the same discussion is going on with rust. it lets the compiler enforce that you're actually using a tail call, instead of silently optimizing it when it sees it and otherwise being silent.
5.
by shadowbanned4 3y ago
This isn't worth the cost or effort. Shopify already has an internal tool with this functionality that they are planning to publicize.
6.
by shadowbanned4 3y ago
No, that gets you a lot of spam emails and the popup doesn't go away
7.
by shadowbanned4 3y ago
> The block is free to return from its enclosing method, which effectively pops multiple frames, including foo and possibly more, off the stack. As an aside, this is one of the key differences between a lambda and a proc. Last I checked,
8.
by shadowbanned4 3y ago
No. They used Oauth. I wrote their entire Oauth system. And it was a nightmare reading through Oauth/OIDC specs for something that could be handled trivially with http basic auth.
9.
by shadowbanned4 3y ago
I worked for the largest company in Canada who handled billions of dollars. You can make your decision but they won't do anything.
10.
by shadowbanned4 3y ago
This is practical, but awful advice. Auth (z or n) has been very badly over engineered. You don't need anything more than http basic auth, the rest is just people with too much time on their hands. Oauth particularly is a travesty that
11.
by shadowbanned4 3y ago
There isn't really any reason for this except Sam is a YC founder and OpenAI (whose name is a lie because they provide proptietary LLMs) is being hyped in the media. He is already rich. Getting fired means an early retirement in Bahama