News for hackers. Stuff that matters.

ucarion

Re:The Curse of the Corporate Headshot on Wednesday February 01, 2023 @04:27PM (#34618055)
yup, I got it backwards!
Re:The Curse of the Corporate Headshot on Wednesday February 01, 2023 @11:57AM (#34613405)
It's a bit outdated to think this rigidly about things, but when a subject has one shoulder higher than the other, tilting the head toward the higher shoulder is historically considered a more "masculine" pose, and toward the lower shoulder a more "feminine" one.

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...

The same CGPM 2022 conference also resolved to give standard prefix names for 10 to the 27 and 30:

    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)
Re:Using TODO For Everything on Monday May 02, 2022 @12:36PM (#31237407)
I'm skeptical of use of TODO in general, because we rarely know what the future portends. To say "TODO" is to assert what must be done in the future, when in reality all we can typically say is "NOTDOING". That said, "TODO" is well-understood by a lot of editors, so it's often useful to just drop that word in the source code to make it easier to find.

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.
Re:Global-Tz – 2022ag (Beta) on Friday March 18, 2022 @06:18PM (#30728273)
Some more details of the differences between this new db and tzdb are available here:

https://github.com/JodaOrg/global-tz#rationale

Having the option for users to exclusively belong to organizations would be nice. It makes implementing tenant boundaries, and avoiding cross-account broken access control, much easier.
Love this, and love that there's more going on in this space. Three questions:

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?

I'm curious what kind of tooling you developed as part of this process. It seems, from the linked YouTube video, like individuals were actively monitoring the data produced from the exfiltration attack. How did you go from the raw data to producing something that people could usefully monitor?
Re:What's New in ClickHouse 21.12 on Thursday December 16, 2021 @12:10PM (#29580592)
They may be working on it already. Such a product would take awhile to create. It was only in September of this year that Clickhouse was spun out of Yandex and quickly raised a Series A + B.
Re:An underrated idea: the priority view on Friday December 10, 2021 @12:27PM (#29512658)
Section 3 of the linked Parfit article touches on the notion that Rawls's distinction is mostly one of framing, not of actual recommendations:

"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.

Re:Umarell on Friday November 26, 2021 @12:29PM (#29352137)
There's a great Seinfeld cold open about the magnetism men feel toward construction work:

https://www.youtube.com/watch?v=rP8vExQYxus

Re:ClickHouse, Inc. on Monday September 20, 2021 @12:52PM (#28595902)
Might make more sense to link to the blog post, instead of its underlying markdown in GitHub?

https://clickhouse.com/blog/en/2021/clickhouse-inc/

Re:Missile Base for Sale on Saturday August 28, 2021 @03:45PM (#28340882)
Living in the middle of nowhere is probably a better survival strategy, FWIW. In the event that the US is attacked, ICBM silos act as a nuclear sponge -- things adversaries have to blow up, lest we fire back using them. ABMs are targets too, because they enhance the sponge.

So living far from silos (and their command centers), and far from the large cities that the sponge protects, is a better survival strategy. :)

Re:Missile Base for Sale on Saturday August 28, 2021 @01:01PM (#28339548)
It's an (old) ABM (Anti-Ballistic Missile), not ICBM (Intercontinental Ballistic Missile) silo. ABMs shoot down incoming ICBMs.
Re:Launch YC S21: Meet the Batch, Thread #4 on Thursday August 05, 2021 @01:04PM (#28076483)
What's the consistency model for operations against your API? When my backend grants a user access to some resource, will all subsequent permission checks immediately grant that access?

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?

Re:Unison Programming Language on Sunday June 27, 2021 @01:54PM (#27653633)
The (public) name of the implementation is the unique identifier of the contract in most systems, so I think your "Right Answer" is roughly the status quo?
Re:QUIC is now RFC 9000 on Friday May 28, 2021 @12:05AM (#27311624)
Perhaps I should clarify: rfc9001 normatively refers to rfc9000 (and vice versa). There are cyclical references between RFCs, so there isn't any topological ordering.

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.

Re:QUIC is now RFC 9000 on Thursday May 27, 2021 @10:08PM (#27310985)
Yeah, they form a "cluster" of documents: https://www.rfc-editor.org/cluster_info.php?cid=C430, so that the earlier-numbered RFCs can reference later ones. For instance, rfc9000 normatively refers to rfc9001 and rfc9002.
Re:REST vs GraphQL vs gRPC on Monday March 15, 2021 @05:57PM (#26469731)
> Of course, if the argument is simply that it tends to be more challenging to manage performance of GraphQL APIs simply because GraphQL APIs tend to offer a lot more functionality than REST APIs, then of course I agree, but that's not a particularly useful observation. Indeed having no API at all would further reduce the challenge!

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.

Re:The Railsification of SaaS on Tuesday March 09, 2021 @08:12PM (#26406615)
How do you square this:

> 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?

Re:Show HN: Diahook – Webhooks as a Service on Tuesday March 09, 2021 @05:13PM (#26405093)
This is a neat idea! Harder than it sounds, but y'all seem to have most of the aspects of the problem in mind already.

My employer (Segment) has something similar to Diahook (as I understand it) at its core: https://segment.com/blog/introducing-centrifuge/

Re:The reason Okta spent $6.5B on Auth0 on Friday March 05, 2021 @03:13PM (#26361454)
Let me make sure I understand you: I think you're talking about accurate attribution of clickstream analytics to particular users, in the face of spoofed data from clients?

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.

Re:The reason Okta spent $6.5B on Auth0 on Friday March 05, 2021 @02:47PM (#26361197)
Why aren't all the existing products in ETL-for-marketers space already the answer to the question you pose?

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?

Re:The reason Okta spent $6.5B on Auth0 on Friday March 05, 2021 @12:58PM (#26359786)
Okta and Auth0 have mostly been serving the opposite ends of enterprise login, with Okta starting to take on Auth0 (and not so much the other way around).

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.

Re:Dieter Rams Palettes on Tuesday March 02, 2021 @06:08PM (#26322452)
It's really hard to get the same perceived color out of a screen (which shines combinations of R, G, and B at your eyes) versus a physical thing (which reflects a subset of the sun's radiation into your eyes).

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.

Re:The Pretty JSON Revolution on Wednesday February 24, 2021 @04:48PM (#26256506)
Yeah. Maybe it was a bit unclear, but when I used the term "undefined behavior" I think I meant exactly what "free-for-all" means in your sentence.
Re:The Pretty JSON Revolution on Tuesday February 23, 2021 @01:22PM (#26240720)
Not exactly, unfortunately. The text you cite is in the introduction, which is non-normative. That text talks about the conceptual data model, but that's just to frame the reader's thinking.

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-4
Two questions:

1. Why use this over AWS Cognito?

2. Any intention to manage authorization as well?

Re:Anthony Levandowski Pardoned on Wednesday January 20, 2021 @01:54PM (#25850354)
The guidelines are pretty simple. Congress can admit a state by simple majority.

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:

https://en.wikipedia.org/wiki/Overseas_France

Older »