ucarion
Chrono-Compatible Low-Level Date Algorithms (2021)
Australia/Lord_Howe is the weirdest timezone
This isn't to reduce the notability of the article, but isn't BIPM's interest in any color-perception stuff basically limited to making lightbulbs roughly equally bright? (i.e. https://en.wikipedia.org/wiki/Luminous_efficiency_function) I guess I don't see how even nonlinearity in perceptual space matters for that purpose.
So if you're familiar with Okta's parlance, both "Attribute Statements" and "Group Attribute Statements" are returned to you in `attributes`.
[1]: https://ssoready.com/docs/api-reference/saml/redeem-saml-acc...
https://ssoready.com/docs/api-reference/saml/redeem-saml-acc...
Yeah, this is super important. No short answer here, it's just about doing the work and getting it right.
We're working with Oneleet for our SOC2 stuff (which we all know is largely theater) but also pretty thorough pentesting. I can email you their findings.
The reality is we're one of those companies that need to get this stuff right.
> Question: Will the free tier SSO have uptime guarantees, since it'll be a single point of failure for all your customers? For startups that decide they'd like it hosted for them, but need an SLA, do you expect to be able to provide that at a price doable by startups?
Our plan is to work out agreements on a case-by-case basis. It'd depend on exactly what you need. We take guarantees pretty seriously, so we're careful about what we promise.
We're not a services business. We don't want to make money off of "premium support". There is a modest price tag if you want an SLA.
> (Will a cloud provider pick up those customers using your software?)
Would you mind rephrasing?
Incidentally we just shipped something for this. Rather than having to make a 204-page PDF, you can go into SSOReady, generate a setup URL, and give it to customers. Customers can visit that URL and they get a self-serve UI for configuring their SAML connection to your product.
https://ssoready.com/docs/idp-configuration/enabling-self-se...
Take any language's biggest SAML implementation, and it's the same story of a library with some epic README covering dozens of public methods you may or may not need to use. People can't make heads or tails of this stuff.
Clarity and simplicity are the precursors to security. I'm pretty obsessed with making SAML clear and simple for folks.
Honestly IETF did a pretty good job with SCIM itself. It's not wacky in the way SAML is at all. In my experience the hardest part about integrating SCIM is setting up all the IDP-specific configuration around it. Like with SAML, it's a situation where Okta, Microsoft, OneLogin all have totally different terms for the exact same thing.
One thing I'm pretty excited about is that our SCIM support will also include a button where you can generate a setup link that you give to your customer. From that setup link they can self-serve configure their SAML+SCIM configuration.
We have that working for SAML right now, and it's nice because it means you don't need to write IDP-specific documentation walking customers through each product's weird terminology and quirky UI.
Launch HN: SSOReady (YC W24) – Making SAML SSO painless and open source
Hey everyone, I'm Ulysse, CTO at SSOReady (https://github.com/ssoready/ssoready).SSOReady is an open-source (MIT) service that lets you implement SAML single sign-on without ever touching SAML yourself. You just need to implement two API endpoints: one to initiate SAML logins and another to receive incoming SAML messages. And then you're pretty much done.Here's me setting up SAML...
https://ssoready.com/blog/engineering/xml-dsig-is-unfortunat...
Usually SAML happens because customers ask for it, OIDC isn't as widely implemented by IDPs as SAML is, so you end up implementing SAML and moving on with life.
XML Signatures are a bad idea executed even worse
https://buildwithfern.com/ https://liblab.com/ https://www.speakeasyapi.dev/
Between this and fancy API doc generators (Mintlify, etc.), I feel like we're finally getting close to being able to just go from OpenAPI to Stripe-level "polish".
Apply.
My gut tells me that it would often make sense to jump straight to shuffle sharding, where you'd converge on fair solutions dynamically, in a lot of cases. I'm looking forward to that follow-on article!
When I talked about Apex, I really mean the "scripting language that sees data mid-transaction" aspect of the language. Sounds like you're not really seeing the value there either? I totally agree that good old webhooks or some other trigger is seems almost always good enough if the API is fast.
Appreciate the suggestions re: comms and consent management. We're still not sure how we want to handle dialers.
Want to work on reducing bundle sizes. Just haven't gotten a chance to get to that yet. Totally agree that load times really matter here, I've been focused on that and still have a few ways to speed that up.