ucarion

8 ms·

61.
by ucarion 2y ago
Anticipated audience: NOBUS
62.
by ucarion 2y ago
I don’t really have much an opinion on the what, I think I just know how I want this to feel. My preference is whatever works, and then making it obvious how it works. Mystery meat config files feel like the opposite, but I totally acknowle
63.
by ucarion 2y ago
This is really cool. Is the "standards" thing basically some sort of LLM prompt? Like, do I just say in words "use slog, discourage logrus"?
64.
Show HN: Hyrumtoken – a Golang package to encrypt pagination tokens(github.com)
3 points by ucarion 2y ago|0 comments
65.
Chrono-Compatible Low-Level Date Algorithms (2021)(howardhinnant.github.io)
1 points by ucarion 2y ago|0 comments
66.
Australia/Lord_Howe is the weirdest timezone(ssoready.com)
4 points by ucarion 2y ago|0 comments
67.
by ucarion 2y ago
> Consequently, we need to adapt how we model color differences, as the current standard, ΔE, recognized by the International Commission for Weights and Measures, does not account for diminishing returns in color difference perception. T
68.
by ucarion 2y ago
Yeah, we have this -- if you check out the docs for the endpoint where you accept a SAML login[1], there's an `attributes` (map<string, string>) that SSOReady returns to you. That contains the contents of the relevant SAML assert
69.
by ucarion 2y ago
The interface between your app and SSOReady is entirely over an HTTP API. We codegen SDKs for that HTTP API for Python and TypeScript, and will add more, but in the meantime the docs show you the curl you'd need to port: https:/&
70.
by ucarion 2y ago
I think the reality is that the category of software we're open-sourcing isn't very big. We're gonna make our money doing other things, not all of which will be open-source.
71.
by ucarion 2y ago
My personal phone number and email is in the sidebar of app.ssoready.com for this exact reason.
72.
by ucarion 2y ago
> Question: For the free hosted SSO, how well are you going to be able to secure that, so that your customers aren't compromised through you? Yeah, this is super important. No short answer here, it's just about doing the work a
73.
by ucarion 2y ago
I've written one of these 204-page PDFs before (I think it was more like 20 pages though). The IDPs don't exactly make it easy on their customers to set this stuff up, and the burden ends up on the SP (i.e. you) to document to fol
74.
by ucarion 2y ago
OIDC2 is the better protocol, don't get me wrong. But lots of companies run on SAML, and it's the thing customers explicitly ask for.
75.
by ucarion 2y ago
Most folks will read that README and conclude SAML isn't going to happen for them today. Take any language's biggest SAML implementation, and it's the same story of a library with some epic README covering dozens of public me
76.
by ucarion 2y ago
Yeah SCIM is coming up. Auto-deprovisioning and stuff related to seat management are the big motivators I've seen. Honestly IETF did a pretty good job with SCIM itself. It's not wacky in the way SAML is at all. In my experience th
77.
Launch HN: SSOReady (YC W24) – Making SAML SSO painless and open source(github.com)
317 points by ucarion 2y ago|98 comments
78.
by ucarion 2y ago
It's hard to answer questions like this in the abstract. The details matter.
79.
by ucarion 2y ago
Agreed. XML Signatures is the worst part of SAML. It's a spec that's basically begging to be done wrong. I remain confused as to what W3C were thinking. https://ssoready.com/blog/engineering/xml-dsig-is-u
80.
by ucarion 2y ago
Is anyone going around choosing SAML today, though? XML fever has come and gone. 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 wi
81.
XML Signatures are a bad idea executed even worse(ssoready.com)
7 points by ucarion 2y ago|0 comments
82.
by ucarion 2y ago
The US has 400 land-based nuclear weapons, not thousands upon thousands. They're there to be a better thing for our enemies to aim at than our cities.
83.
by ucarion 2y ago
Lots of these have been popping up lately, they all seem really good. This is the first one I've seen with an answer for "I want to customize the output by hand", which is neat. https://buildwithfern.com/ ht
84.
by ucarion 2y ago
I was in the last batch. The average is probably ~28 years old, but there are plenty of founding teams in their 40s and on. Plenty of folks with families. You wouldn't be a dinosaur. Apply.
85.
by ucarion 2y ago
Makes sense! 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!
86.
by ucarion 2y ago
This is pretty fancy stuff! Sorry if I'm just not reading carefully enough, but does this approach account for tenants whose messages take longer to process, as opposed to a tenant that sends a larger volume of messages?
87.
by ucarion 3y ago
Thanks! Yeah, we all stand on the shoulders of the giant that is Tailwind UI :)
88.
by ucarion 3y ago
Task management, lists/views, and general "journeys" management are all on the roadmap. There's a lot of stuff you need to do to be generally competent in this space, we're definitely launching very early here. When
89.
by ucarion 3y ago
Salesforce is where the money is. There's plenty of competitors.
90.
by ucarion 3y ago
Definitely going to add the hotkeys-for-objects feature! That's on my to-do list. 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

More ›