ucarion
This webpage is a good articulation of the classic way of thinking about portraiture, but I should clarify that I disagree with the entire premise of rigid "masculine" and "feminine" posing:
https://www.spencervillebearcats.com/userfiles/88/my%20files...
power prefix symbol
10^27 ronna R
10^−27 ronto r
10^30 quetta Q
10^−30 quecto q
c.f. https://www.bipm.org/documents/20126/64811223/Resolutions-20... (Resolution 3, English version on page 23)A more reliable approach is to:
1. File a ticket, and
2. Leave a comment in the code linking to it:
// This code does X, but it'd be better to do Y. At the time of writing
// fixing this doesn't seem to be an issue worth fixing.
//
// See: https://bugtracker.example.com/...
It's very difficult to write code that correctly predicts the future, but it's easy to write code that accurately describes the status quo at time of writing.1. SAML?
2. SCIM?
3. In your domain model, do users belong-to organizations? Or is it a has-and-belongs-to-many sort of deal? Can I configure that?
"Third, Rawls regards Utilitarians as his main opponents. At the level of theory, he may be right. But the questions I have been discussing are, in practice, more important. If nature gave to some of us more resources, have we a moral claim to keep these resources, and the wealth they bring? If we happen to be born with greater talents, and in consequence produce more, have we a claim to greater rewards? In practical terms, Rawls's main opponents are those who answer Yes to such questions. Egalitarians and Utilitarians both answer No. Both agree that such inequalities are not justified. In this disagreement, Rawls, Mill, and Sidgwick are on the same side."
That said, to your original point, Rawls does espouse maximizing for the least well-off ("maximin"). The "priority view" doesn't need to be so extreme. It can simply be biased toward improving the lot of the badly-off, rather than putting an absolute priority on the worst-off member of the population. They are definitely related, but it's muddled by Rawls's (somewhat inconsistent) rejection of a consequentialist framing.
So living far from silos (and their command centers), and far from the large cities that the sponge protects, is a better survival strategy. :)
If not, how are user signups supposed to work? If I create a user and set up their permissions in Warrant, will my users' first-time experience consist of a permission denied error?
It works out because RFCs convey ideas, not code. The authors and editors take care to make sure the cyclical dependencies don't imply circular definitions or other incoherences.
On their own, such arguments are indeed not useful. But if you can further point out that GraphQL has more functionality than is required, then you can basically make a YAGNI-style argument against GraphQL.
> You can’t share a Zapier integration universally.
With then plugging Autocode? How is an Autocode integration any more universal than a Zapier one?
Also, how are you building the code for the various integrations Autocode supports? Is there some underlying interlingua that you codegen from?
My employer (Segment) has something similar to Diahook (as I understand it) at its core: https://segment.com/blog/introducing-centrifuge/
And then, connecting the dots a bit, spoofed clickstream events could trigger some sort of marketing campaign event or other "action" that can become a vector for security issues, such as Eve figuring out what Adam has in his shopping cart by manipulating a cart-abandoned campaign to go to Eve's email instead of Adam's?
If so, this is usually addressed by server-side analytics events. I fail to see any mechanism by which this could be solved client-side, nor any useful way for any vendor to make this process meaningfully easier. Analytics events are basically as easy as console.log with most vendors.
Most companies have a users table, and there are a ton of products that can, without code, ETL a users table into all sorts of tools. There's no redundant work -- in fact, for developers there may not be any work to do at all?
Okta mostly handles being the "enterprise database of users + gateway to your enterprise apps", i.e. it's an identity provider (IdP). ActiveDirectory and PingIdentity are competitors here.
Auth0 mostly handles the other end of the line: they help companies be "a thing you can log into using an IdP", i.e. they help companies be a service provider (SP). Custom SAML/OIDC implementations are the biggest competitors here. Okta has increasingly been competing with Auth0 in the space of SaaS SP solutions.
So it's in the latter half -- service providers -- where the two compete. You may have been looking in the wrong place. Plus, not all companies are service providers, and many companies that are service providers roll their own implementation of the relevant protocols.
The way we do this only works for humans, incidentally. Most of the time, different things only appear to have the same color because they happen to map to the same "point" in color perception space, not because they actually produce the same light distribution.
The normative text has the "real" answer, and the real answer is that it's basically undefined behavior. It starts by saying "The names within an object SHOULD be unique", and then elaborates:
An object whose names are all unique is interoperable in the sense that all
software implementations receiving that object will agree on the name-value
mappings. When the names within an object are not unique, the behavior of
software that receives such an object is unpredictable. Many implementations
report the last name/value pair only. Other implementations report an error
or fail to parse the object, and some implementations report all of the
name/value pairs, including duplicates.
JSON parsing libraries have been observed to differ as to whether or not they
make the ordering of object members visible to calling software.
Implementations whose behavior does not depend on member ordering will be
interoperable in the sense that they will not be affected by these
differences.
https://tools.ietf.org/html/rfc8259#section-41. Why use this over AWS Cognito?
2. Any intention to manage authorization as well?
https://www.law.cornell.edu/constitution/articleiv#section3
As to what you consider a "false positive" state, that's a political question, and apportionment is not the only political consideration. Congress is just about the best option we have for settling such complex, interstate questions.
Moreover, the US has always had lopsided state populations. The 65:1 apportionment population ratio between California and Wyoming (https://www2.census.gov/programs-surveys/decennial/2010/data...) is definitely big, but it's still within an order of magnitude of where we started in 1789.
The first (pre-Census) apportionment, hard-coded in Article 1, Section 2, had a 10:1 Virginia:Rhode Island ratio in the House:
https://www.law.cornell.edu/constitution/articlei#section2
After the first Census, the largest difference ratio of apportionment population (i.e. population after implementing the 3/5 compromise, excluding "Indians not taxed", etc.) was about 11:1, between Virginia and Rhode Island:
https://www.census.gov/history/pdf/ApportionmentInformation-...
If you were to undo that 3/5ths slavery effect, the Virginia:Delaware ratio becomes closer to 12.5:1.
FWIW I agree Puerto Rico ought to be admitted, just as the Virgin Islands, Guam, and Mariana Islanders ought to be as well. France's DOM-TOM system seems like a better model to follow than America's, and it could still happen within our lifetimes; France made major reforms here within the last few decades: