HNHacker News
TopNewBestAskShowJobs

laughinghan

2,942 karma · joined August 25, 2010

http://twitter.com/laughinghan

http://github.com/laughinghan

submissionscomments
laughinghan··on Debubble
I'm confused. In both Debubble and my vaguely sketched out proposal, you can't be forced into a debate with someone you have no interest talking to. You have to voluntarily start a conversation with them.

Surely there is at least someone in the world who, unlike your 3 examples of conspiracy theorists, you would consider a reasonable person, but who also disagrees with you about something important?

r/changemyview has the same problem I criticized Debubble for, which is not addressing the deeper problems that cause debates to be toxic. r/changemyview's only rules are basic no-trolling civility rules, whereas my proposed rules are MUCH stricter: during phase 1, you're literally not allowed to argue. Making arguments is banned, you're only allowed to ask and answer clarifying questions during phase 1.

In a discussion with someone who is reasonable but disagrees with you about something important, can you imagine a framework like that being helpful? How would you improve them?

(I also believe that, even if you couldn't possibly learn anything about 5G or coronavirus from someone who believes 5G causes coronavirus, you may be able to learn what causes someone to start believing such nonsense, and how we as a society can mitigate this kind of misinformation.)

laughinghan··on Debubble
Good point! I have no idea.

If someone specifically desires to shout into the void, I don't have any ideas on how to convince them otherwise. However, if they claim they want to actually convince other people to change their mind, maybe they'll both agree that this system will help frame the discussion.

After all, people already voluntarily put a lot of effort into heated Internet arguments already, I'm just hoping to nudge that energy in a productive direction.

If you have better ideas on how to motivate them, I'm all ears!

laughinghan··on Debubble
IMHO this largely only solves problems caused by Twitter's idiosyncratic design, and does little for the deeper problems that cause debates to be toxic.

Much more interesting would be a debate format in two phases:

Phase 1: just identify what we agree and disagree about. Are there things we actually agree about but are using different words for? Are we using the same words to mean different things? Are there two competing concerns we accuse each other of denying, when we actually both agree on them and are just valuing them differently?

The goal would be to create a document that outlines things we agree on and disagree on, and identifies whether the disagreement is factual/empirical, values, or logic (hopefully there will be zero of these, but it might be possible). We should be able to fully agree on the contents of this document. If there's ever anything you simply can't believe the other side disagrees with you about, try to clarify what the deeper disagreement is.

Important rule during Phase 1: no persuading. We're not allowed say anything to try to persuade the other side, we're only allowed to ask clarifying questions about the other side's position, and clarify our own positions, because the goal is not to change anyone's mind, only to understand, identify, and document what we agree and disagree about.

Phase 2: persuade away. It should be much easier to have a civil and respectful discussion if we each understand the other's side, their values, and what empirical facts they disagree with the evidence on.

(I do really like that Debubble doesn't allow bystanders to "cheer for their side", they can only star the whole debate—I'm stealing that.)

laughinghan··on Internet mob justice can easily destroy innocent lives (2019)
That article doesn't actually report an allegation that the incident was "unleashed by Oklahoma police officer", but this one does: https://www.news9.com/story/5efe6166c993e811aef887a0/norman-...
laughinghan··on Mozilla VPN
No, your premise is wrong, all major browsers have committed to removing third-party cookies, or have already done so. And after third-party cookies, your IP address is the next-easiest way to track you across sites.

that Facebook cookie works regardless of what your IP address is

Firefox has been blocking third-party cookies by known trackers, including Facebook, since last year [1]. Safari started blocking all third-party cookies (not just known trackers) in March [2], and Chrome committed in January to work towards removing third-party cookies [3].

And of course, all major browsers have provided the option to block third-party cookies since before IE6. I use this option, it rarely breaks things, and it's only getting rarer—and I don't use a VPN, so this would make me measurably harder to track across sites.

[1]: https://blog.mozilla.org/blog/2019/09/03/todays-firefox-bloc... [2]: https://webkit.org/blog/10218/full-third-party-cookie-blocki... [3]: https://blog.chromium.org/2020/01/building-more-private-web-...

laughinghan··on Zoom to bring end-to-end encryption to all users, including non-paying
Did we read the same comment? https://news.ycombinator.com/item?id=23553503

It explicitly argues that he's evil because he has a Chinese name and Wikipedia describes him as Chinese-American. There's no equivocating about the software being China-based, or him having close family in China for the CCP to threaten.

And discriminating against people for national origin is considered so bigoted it was explicitly included in the 1964 Civil Rights Act. Your reasoning is sound, but you should seriously reconsider your basic ethical principles.

laughinghan··on Zoom to bring end-to-end encryption to all users, including non-paying
Did you read the comment he's replying to? https://news.ycombinator.com/item?id=23553503

It's entire contents is an argument that Zoom is evil because Eric Yuan is Chinese-American. It doesn't say a single one of the things you're saying.

laughinghan··on A Facebook crawler was making 7M requests per day to my stupid website
Your blog is awesome! I'm really glad you commented here, or I wouldn't have found it. I even forwarded your most recent post to some friends.
laughinghan··on A Facebook crawler was making 7M requests per day to my stupid website
That's amazing. Any idea what piece of middleware on your own server was doing that?
laughinghan··on Ruby vs. Crystal Performance
That was an example, I was trying to offer chrisseaton a different notion of "similarity".

Another example: if 0% of Ruby code works in Crystal unmodified, but for 90% of code the transformation was extremely simple and mechanical like using curly braces {...} instead of begin...end and prepending $ to all variable names like Bash and PHP, they would still feel extremely similar in practice, albeit obviously less similar than the above example.

By contrast, Java and JavaScript are widely described as having very similar syntax, but it is rare to translate code from one to the other without require fundamental rethinking, because the relationship between JS objects, functions, and prototypes is so different from between Java objects, methods, and classes.

laughinghan··on So You Want to Build an End-to-End Encrypted Web App
> this basically boils down to TOFU (trust on first use), but the trust does not perpetuate across uses, so it’s more like, TOAU (trust on any use). The trust is ephemeral, the meeting is ephemeral, the ID is ephemeral. For a lot of meetings, this is perfectly acceptable.

I think I would call this TFSU (Trust For Single Use). Trust On Any Use sounds like complete and total trust.

laughinghan··on Ruby vs. Crystal Performance
>> and are also semantically very close

>Sorry I super disagree with this. They look similar. Dig into it just below the surface? Start to model it formally? Not at all.

I think you're missing the point. If 90% of Ruby code works in Crystal unmodified (even if it's because the standard library had to be rewritten from scratch), then the programmer experience may well be quite similar, regardless of how fundamentally different they are if you model them formally.

Are Newtonian mechanics and Einstein's theory of general relativity "similar"? If you model them formally, they look nothing alike. But in 99% of practical situations in every day life, and even in the most precise experiments we could conduct for hundreds of years, they're so similar we can't tell the difference.

laughinghan··on Blur Tools for Signal
Good point, I'd be surprised if lighting and orientation doesn't overwhelm all other information at this level of blur.

But I've been surprised by impressive digital forensics before—what if you can determine lighting and orientation from the rest of the photo, and then simulate them on each passport photo/mugshot? I'd still feel much more comfortable if they pixelized and color-discretized before blurring, and I still think the aesthetic effect would be much the same.

laughinghan··on Blur Tools for Signal
They're not using random noise in place of the face, they're using a 25px Gaussian blur: https://news.ycombinator.com/item?id=23415600
laughinghan··on Blur Tools for Signal
Yes, they are using a 25px Gaussian blur, they are not overlaying a different image on top: https://news.ycombinator.com/item?id=23415600
laughinghan··on Blur Tools for Signal
You should also discretize the pixel colors.

Note that if you blur the pixelated region, it'll be just as aesthetically pleasing as the reversible Gaussian blur.

laughinghan··on Blur Tools for Signal
But a bad blur doesn't. That's why your parent comment asks what kind of blur they use.

Edit: Turns out it's a 25px Gaussian blur. There's some downsampling beforehand, but not much, and no color discretization. In other words, they use a bad blur, but compensate with a large security margin. I wouldn't be surprised if this was vulnerable to "if I have a thousand photos of faces and I think one of them matches the blurred face, I can figure out which one with high confidence", and they can get basically the same aesthetic effect if they heavily pixelate and discretize colors before blurring.

https://news.ycombinator.com/item?id=23415600

laughinghan··on Blur Tools for Signal
There's another concern—even if I can't usably invert the convolution, if I have photos of a thousand people's faces and one of them is that blurred face, can I figure out which one with high confidence?
laughinghan··on Blur Tools for Signal
Just blur the pixelization and it will look similar to the human eye, but with guaranteed information loss. Note that you should also discretize the colors of the pixels, which otherwise have 24 bits of information each; and maybe 2x2 pixelization might be a better idea.
laughinghan··on Trump signs executive order targeting protections for social media companies
Aren't you just talking about the volume then? You could be screaming the most wholesome things about unicorns and rainbows and still be loud enough to be a public nuisance, and loud enough that authorities will have the right to ask you to pipe down.

In America, no matter how big of a community mall, management can always remove you for good reasons (using racial slurs, even at normal volume), silly reasons (they didn't like the color of your hat), or no reason at all, as long as it's not for a prohibited reason (because of your race). Whereas authorities cannot remove you from a public square for no reason or silly reasons, only for good reasons specifically identified by law (like public nuisance).

laughinghan··on Practical privacy tips for your business
I've heard that upvotes don't count if they're from people who followed a link directly to the story. And you're not supposed to solicit votes in the first place. Just say "Join the discussion on Hacker News". :)

Great article, by the way! People need to put more thought into this kind of thing.

laughinghan··on Practical privacy tips for your business
Do you have website visitors in Europe or California? If so, you better be documenting what you're doing with those IPs much clearer than "might help finding offenders".

Under Europe's GDPR, IP addresses are explicitly classified as personally identifiable information, and must not be recorded except for clearly identified and documented valid purposes that you communicate to your visitors and regularly review: https://ico.org.uk/for-organisations/guide-to-data-protectio...

California's CCPA currently doesn't apply to smaller companies, but imposes similar requirements: https://secureprivacy.ai/what-is-ccpa-and-how-to-become-comp...

Security is explicitly a valid purpose, but I doubt "might help finding offenders" is clear and specific enough to be compliant. I'm not a lawyer, but ethically, you need to explain to your visitors how long you're storing IPs for, what you do with them and what you promise not to do with them, who you share them with, why you need raw IPs and not just salted hashes, etc.

laughinghan··on Facebook executives shut down efforts to make the site less divisive
That's not a counterargument. Nuance doesn't contradict the black-and-whiteness of the situation. Sometimes nuance just means there are many shades of black.

The same thing can also harm the same people, or a different set of people, or the company, in a way that's impossible to disentangle from the good.

It might be impossible to 100% disentangle. But it is nonsense to suggest it could ever be impossible to >0% disentangle. And they have a moral obligation to prioritize disentangling them, to maximize the good and minimize the harm, and to structurally incentivize themselves to succeed at that.

But your attitude creates the exact opposite incentive: the more entangled the good with the harm, the more defensible it is for them to passively enrich themselves thru their inaction.

Don't fall for it. Demand more.

Demand structural changes that incentivize real fixes, for example, pledging that ad revenue from hate content and fake news be returned to the advertiser and the same amount also donated; or pledging that feelings of community vs feelings of divisiveness affect executive or company-wide bonuses. These particular ideas might be stupid, but don't let them get away with not even trying.

laughinghan··on Facebook executives shut down efforts to make the site less divisive
If you restrict yourself to 2 bad choices, then you can only make bad choices. It doesn't help to label one of them "artificial" and imply the other choice isn't artificial.

It is, in fact, not just crude but actually quite artificial to measure likelihood to interact as a single number, and personalize the list of discussions solely or primarily based on that single number.

Since your chosen crude and artificial indication turned out to be harmful, why double-down on it? Why not seek something better? Off the top of my head, potential avenues of exploration:

• different kinds of interaction are weighted differently. Some could be weighted negatively (e.g. angry reacts)

• [More Like This] / [Fewer Like This] buttons that aren't hidden in the ⋮ menu

• instead of emoji reactions, reactions with explicit editorial meaning, e.g. [Agree] [Heartwearming] [Funny] [Adds to discussion] [Disagree] [Abusive] [Inaccurate] [Doesn't contribute] (this is actually pretty much what Ars Technica's comment system does, but it's an optional second step after up- or down-voting. What if one of these were the only way to up- or down-vote?)

• instead of trying to auto-detect party affiliation, use sentiment analysis to try to detect the tone and toxicity of the conversation. These could be used to adjusts the weights on different kind of interactions, maybe some people share divisive things privately but share pleasant things publicly. (This seems a little paternalistic, but no more so than "artificially" penalizing opposing party affiliation)

• certain kinds of shares could require or encourage editorializing reactions ([Funny] [Thoughtful] [Look at this idiot])

• Facebook conducted surveys that determined that Upworthy-style clickbait sucked, in spite of high engagement, right? Surveys like that could be a regular mechanism to determine weights on interaction types and content classifiers and sentiment analysis. This wouldn't be paternalistic, you wouldn't be deciding for people, they'd be deciding for themselves

laughinghan··on What developers should know about TCP
But in the meantime, won't the vendor keep adding more broken devices to the public internet, making the problem worse?

The longer it takes for this problem to become public, won't the more harm be caused when it does become public?

laughinghan··on Let's guess what Google requires in 14 days or they kill our extension
Unfortunately, information that helps the good guys get their extensions past the audit check is exactly the same information that helps the bad guys get their extensions in too.

This is just an assertion I'm wrong. It can't possibly persuade me or the people upvoting me. Would you be persuaded by me just asserting you're wrong?

In terms of Google already auditing every app, [e.g.] the source code for Dark Reader [is] fairly complex.

Firstly, Apple is able to do it, there's no reason to make excuses for Google. See anecdotes elsewhere in the thread about how Apple attaches screengrabs, explains rejections by phone conversation, even decompiles apps to point to exact methods/lines of code in apps they reject from the iOS App Store, even small free ones: https://news.ycombinator.com/item?id=23170498

And anyway, without reading a single line of Dark Reader's source code, I can deduce plenty of permissions it shouldn't need, e.g. "cookies" (which it doesn't ask for). Without reading a single line of PushBullet's source code, one can easily deduce it shouldn't need access to "https://*/*", and indeed, it doesn't, yet it asked for it.

Can you explain concretely (not just by pointing to unnamed "no-no's") how could harmful side-effects result from Google telling PushBullet that "https://*/*" specifically was in violation?

If you release a list of known no-no's, the bad guys just get smarter and avoid them.

Firstly, isn't bad guys avoiding no-no's exactly what we want?

If you're saying that there may be some, probabilistic red flags that Google uses to find possible bad guys—sure, that could be true, I have no idea and you don't either, you admitted it was speculation. But in this case, "Request access to the narrowest permissions necessary to implement your product’s features or services." is not a probabilistic red flag, it's a hard rule.

Again, concretely how could harmful side-effects result from Google pointing out the specific violation?

laughinghan··on Let's guess what Google requires in 14 days or they kill our extension
> If goog did provide guidance on permissions, goog would literally have to audit every app in the store, or come up with a way to separate bad actors from good ones.

This makes no sense. For the sake of the grandmas, Google already needs to audit every app in the store and separate bad actors from good ones.

How in the world would making it more clear how to write more secure extensions possibly worsen the extension store's malware problem?

laughinghan··on Let's guess what Google requires in 14 days or they kill our extension
I don't understand what you're talking about. If the scanner looks for extension with permissions for all your web browsing activity, so malware authors stop asking for permissions for all your browsing activity...isn't that great news?
laughinghan··on Let's guess what Google requires in 14 days or they kill our extension
Most of the discussion on this link is about how Google is being developer hostile. I think that's getting plenty of attention.

You are certainly within your rights to state things divisively if it pleases you. I was merely suggesting how you might make your point in a way people will agree with you.

If they've flagged this through user reports of the permissions being too wide then they may not actually know which permissions need to be changed.

Even if this were true,

1) what about the update that narrowed the permissions, surely Google knew which permissions remained in violation? Remember, it was the rejection of that update that prompted this post

2) user reports of permissions being too wide should also be required to identify the specific permission that is in violation. That would not only help the developer, but also help Google make the decision on whether to ultimately ban the extension

3) Google should have clearly stated in the initial message that they hadn't actually verified that the alleged violations are occurring

laughinghan··on The modern HTTPS world has no place for old web servers
I think the suggestion is to skip a web server at all and go "serverless" with Cloudflare Workers, which are free for up to 100,000 requests/day: https://workers.cloudflare.com/

If your Worker code hardcodes the Dark Sky domain, the worst an attacker could do is either use up your free worker quota from Cloudflare, or hammer Dark Sky at the Worker ratelimit (1,000/minute, which Dark Sky should easily handle).

AWS, Azure, GCP all also have free tiers for their serverless services. RunKit (http://runkit.com) might also work.

These are all likely to be HTTPS-only, but hopefully at least one of them supports TLS v1.1, rather than being 1.2-only like apparently is the problem with Dark Sky.

← PreviousPage 4 of 27Next →