ucarion
But no amount of inline docs in WorkOS.js's UI is going to get around the high-level guidance docs, both for your customers ("where do I even start") and your customers' customers ("how do I fit my IdP peg into your SP round hole").
One of the biggest pain points I've experienced with SAML is that people come to me asking for help, but only understanding their IdP; the only IdP I know how to use is Okta, and I don't have access to their IdP to test with.
I'd love it if WorkOS could give me documentation that I can give to my customers about how they can set up Okta/Azure ADFS/whatever with my product. I can edit those docs to account for idiosyncratic stuff my product does (e.g. requiring a particular SAML user attribute or format for user IDs).
Aside: the support burden of SAML is a big part of why the sso.tax exists. Nobody on the SP or IdP end knows how to set this stuff up!
To that end, any French company at risk of going under will be allowed to stop paying rent and taxes during the shutdown.
https://translate.google.com/translate?hl=en&sl=fr&u=https:/...
https://plainlanguage.gov/guidelines/audience/
IBM has some guidance on this too, as part of their design system:
https://www.carbondesignsystem.com/guidelines/content/genera...
Basically IBM's rule seems to be: there's never a need to be _formal_, but you should be less conversational on specific tasks, and more conversational on high-level docs and marketing material.
https://en.wikipedia.org/wiki/Scandinavian_Airlines
Again: I'm aware that you haven't said anything to the contrary. But it's useful context.
The IETF has the "Independent Submission Editor" stream of RFCs, which produces RFCs without getting IETF consensus. These RFCs are considered to be work "outside" of the IETF, but can still be published as an RFC.
A recent example is https://tools.ietf.org/html/rfc8674 from Mark Nottingham:
The mechanism described in this document does not have IETF consensus
and is not a standard. It is a widely deployed approach that has
turned out to be useful and is presented here so that server and
browser implementations can have a common understanding of how it
operates.Thanks for explaining!
I'm curious how you reached this condition as a requirement:
> The moral of the story here is make sure you pick a metric that reacts to the change in request rate as quickly as your request rate changes!
It makes sense intuitively, but I'm having trouble proving to myself that this is necessary+sufficient.
https://www.yelp.com/biz/legend-billiards-and-snooker-sf-san...
In the game of cowboy, which is sort of a novelty game that is intentionally quirky, you can score points merely by making a carom.
Here's an example I got by Google image searching: https://i.makeagif.com/media/10-30-2015/ODVWHH.gif
CBOR was inspired by MessagePack. MessagePack was developed and
promoted by Sadayuki Furuhashi ("frsyuki"). This reference to
MessagePack is solely for attribution; CBOR is not intended as a
version of or replacement for MessagePack, as it has different design
goals and requirements.
I fail to see what is wrong with having both CBOR and MessagePack, or with trying to bring a MessagePack-like thing to the IETF, if MessagePack's design (lack of extension points, etc.) was problematic for enabling future applications.Also: CBOR is not one person. The CBOR working group, and the IETF in general, put forward the spec. If you object to how the process went down, your quarrel likely lies with IETF, not any individual.
It seems like that works, but I'm also unclear if maybe each sub-span is better off as its own log line? But that carries its own problems.
[1] You do so by implementing this interface: https://github.com/ory/ladon/blob/master/warden.go
Globalization often has a way of dramatically centralizing wealth, and old borders might need updating.
This is relevant within this discussion because we were talking about filesystems, and Windows stores file names as an arbitrary array of 16-bit numbers, but UTF-16 has additional requirements that Windows file names do not satisfy.
When I say UCS-2, I just mean pretending that UTF-16 is short for `[]uint16`, and not worrying about surrogate pairs.
The GDPR is unlikely to be overturned, and there are plenty in the EU who are eager to enforce it. Just because it's not being enforced right this second doesn't mean the law won't catch up to offenders.
Especially if Margrethe Vestager replaces Jean-Claude Juncker as president of the European Commission, you can expect a ton of action on this front.
1. Facebook's "need" to prevent bots ought to be subservient to their need to acquire consent. GDPR requires such consent.
2. It seems quite likely that the persons giving this talk aren't on Facebook.
Facebook surely must be heavily fined and regulated for their misbehavior, because to fail to keep Facebook data safe is to put lives at risk.