Recent submissions

Comment · 5 years ago
FWIW, you can write the conditional compilation example like so:

  fn read_keys(#[cfg(feature = "splitapple")]
               port: nrf52840_hal::pac::P1,
               #[cfg(feature = "keytron")]
               port: nrf52833_hal::pac::P0) -> Packet {}
I suppose the compiler could try to suggest that as a fix.
Comment · 6 years ago
Comment · 6 years ago
Comment · 6 years ago
Comment · 6 years ago
I think it's just more clear that they are listing pronouns, especially if someone isn't familiar with the practice or in verbal speech. Also note that some people use two sets of pronouns, with equal weight, and may list them such as "she/they".
Comment · 6 years ago
Comment · 6 years ago
> After our investigation, we immediately made a number of changes to this endpoint so that it could no longer return specific account names in response to queries.

Does anyone know what this actually means? If the contact discovery API doesn't return a username, what does it do? If the answer is that it returns a user ID now instead of username, then presumably that can then be freely queried for the corresponding username..

Comment · 6 years ago
Phone numbers are useful for exactly the reasons you find them frustrating: stability -- as you said, everyone and everything you associate with can and will store and contact you via your phone number indefinitely -- and portability -- everyone accepts and understands phone numbers, modulo international dialing.

Sure, something could and maybe should replace phone numbers, as the system is definitely messy wrt international dialing and countries changing numbering plans.. But the thing that replaces phone numbers in their usefulness will bring the same frustrations you express.

Email has mostly the same characteristics, especially for non-computer-people. My parents were paying $10/mo for dialup up to ten years after switching to DSL and Gmail, just to keep their old email address. I bring that up not to point out the extortion -- email could theoretically have had address providers decoupled from hosting provider through DNS, if it had been made user-friendly -- but to point out the value in the stable identifier. I know this is an anecdote, but the story of AOL email is similar, that 2.5 million people [1] were still paying $20/mo for their dialup and bundled email when "some of whom" (sorry there's no better information on this) had since switched to a different ISP, but kept paying AOL to keep the email.

> I even had to send them a government issued photo ID recently so I could keep the number.

Governments will always want to link users to their stable identifiers. It's in their policing interest, for better or worse. Switching away from phone numbers will just shift the problem.

[1] https://consumerist.com/2013/08/08/believe-it-or-not-2-58-mi...

Comment · 7 years ago
> ... do not make it explicitly clear that the final solution sends a hash-prefixed password

I'm not sure if you're actually talking about something else, but the paper says: "Post-canonicalization, the server calculates a computationally expensive hash of both the canonical username and credential password... This 2-byte prefix—while leaking some bits of password material—provides the client with k-anonymity over the universe of all username and password pairs."

IOW, the 3-byte hash prefix sent is of the username and password concatenated. (Note that Google seems to have added another byte to the prefix versus the paper).

Comment · 7 years ago
> 2. It is regularly carried on - not really, there's only one .org domain so one can't regularly sell it.

You're right. I misread #2 as the inverse so misunderstood what UBI was.

> 3. It is not substantially related to furthering the exempt purpose of the organization - that one would be the toughest to prove...

Kinda a moot point given #2, but the IRS elaborates (emphasis mine), "... only when the conduct of the business activities has causal relationship to achieving exempt purposes (_other than through the production of income_)"

Comment · 7 years ago
Well, reading the IRS guidelines on what qualifies as UBI, it seems like it might fall under that category, but I'm also not an expert, which is why I'm asking for a more qualified opinion. However, assuming it's UBI, it's pretty clear to me that having a large percentage of their income this year being UBI would be a red flag to the IRS.
Comment · 7 years ago
Comment · 7 years ago
Comment · 7 years ago
I see your point. Especially since cost-based KDFs rely on the predicted characteristics of future hardware.
Comment · 7 years ago
I think if my password is worth 17.5 trillion CPU seconds then I'm a very lucky person...

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton