ampersandy

Would love to see the article expanded on with a legal analysis of the situation.

Where does the post say anything about it being disabled for those languages or that Chrome "specifically" ignored this on ProtonMail?

It just says they had to turn off the suggest translations feature, which would apply to all sites/languages.

Your attitude on this entire thread has been incredibly condescending. Why don't you try and think of why these problems are hard instead of just assuming they are all easy, as you've done so far?

I challenge you try and think through why your simple spam filter and human appeals process will not scale to Twitter's size. What kind of throughput can it handle? What happens when there is more content being appealed than the review team can handle? How do you prevent attackers from maliciously flagging other users' content? How do you handle advanced threats where attackers compromise existing accounts then begin to spam, thus bypassing any "easy" checks like looking at account age? How do you classify "hateful" speech? How does it scale to foreign languages, slang, etc?

They have a separate section on their website describing their Microsilk, which is being used to produce ties.

https://boltthreads.com/technology/microsilk/ https://ties.boltthreads.com/

FB uses Phabricator, which was spun out into an open-source project:

https://www.phacility.com/phabricator/

It seems you do care, since you've commented twice now claiming the author has ripped off your work, without any evidence whatsoever. Perhaps you should contact them privately if you feel that you've been wronged here?

Publicly claiming someone has ripped off your work is a pretty strong allegation and I don't see any basis for it.

If a problem can be summarized in a few simple steps, then how different do you expect any posts about the topic to be?

As you said, what cle described is a gradual rollout. You can do both at the same time though -- simply start your test on X% of the population and then roll it out to more people as you run your test. This is also a great way to run long-term holdouts.

I used to work on the Site Integrity team at Facebook. It's really challenging to fight spam at scale. We've accidentally blocked many top domains in the past -- mistakes happen and we work to fix them as quickly as we can.

I can tell that you're trying to be sarcastic, but I've heard enough good things about Slack that it was hard to catch.

If you're not being sarcastic... well, I think Shank summed it up pretty well.

I feel the author has chosen poor examples for illustrating 'bad code'. Does he really think so little of the id software team that they aren't aware of these things? There's no mention of the fact that in the real world, all the patterns and weird tricks there are won't save you from compromising on a perfect design to get stuff done & shipped.

This post doesn't address the most important thing: when can we actually expect all of the government's websites to start using these common patterns?

Creating a library/set of guidelines that you expect other developers to use is great and all, but not impactful in and of itself. Right now it looks like the library's authors are more focused on making their library useful than used, which is a thousand times more important.

The root of these bad host stories seem to be that the guests arrive and don't immediately contact Airbnb about issues with the rental. Because of this, Airbnb just denies any liability and puts the blame on the renters instead of the host.

This seems trivial to solve -- Airbnb should make check-ins a mandatory part of all stays, and any issues with the accommodations would obviously be included in this initial check-in. There would be no chance for a host to move you across Barcelona before realizing you've been totally screwed or before Airbnb starts denying any and all responsibility for the problem.

Don't forget that Twitter has a comprehensive advertising platform. The partnerships, sales, tooling, and ad auction system themselves are likely just as complicated (or more so) than the basic Twitter product.

Instagram has only recently started to monetize the product -- it's almost unfair to compare the size of the engineering teams supporting the systems.

Any particular recommendations?

I find it ironic that you are berating JustGotHere for sharing his experiences, but feel that it is inappropriate that you were downvoted for sharing yours.

Your anecdote isn't relevant, because I don't know what hardware you run, and it's likely that most other readers aren't using the same hardware. Your time would be better spent filing a bug report.

This is the (jsbeautified) source of the script from your article (http://pastebin.com/kvvYXKKX). I'll wager grammar_costs is just a metric used by graph search and not your friends' coefficients.

The last paragraph sums it up:

    He says he can envision a consumer-level app in the future that could be installed on phones by individuals. Although such an app wouldn’t have all of the same functionality as the robust firewall has, it would still be able to alert you to a rogue cell tower. There are currently no plans for an app, however.

Looks like you'll need 10 million users in order to have that much space, though.

Personally, I'm totally ok with more prominent job postings from affiliated startups. As long as there aren't, say, more than 3 posts at a time I'm fine with them sitting at the top of the front page.

If the people that you are no longer friends with have your contact information (email, phone, etc.) and sync their contacts to Facebook, and you have the same details associated with your new account, then a relationship can be inferred and Facebook could show these people as suggested friends.

I used to work at Twitter, so I was able to request it internally. As I mentioned, you were only able to request a handle that met some strict 'inactive' policies.

I left in 2012, so I don't have much context since then. The root problem is that you want to give handles to people who will genuinely use them. But if you open up any system for reclaiming handles, it's just going to be abused by people trying to snag and sell handles (just like domains). Since there was no obviously correct way to ensure only people who would use the handles got them, it was just done internally for people who requested it (and their friends).

What does this have to do with Facebook and the acquisition? Anyone working at Instagram pre-acquisition would also have been able to reclaim inactive handles.

Twitter does this as well and that's how I got my current username. There are a couple of things that are required before you could reclaim a handle (I forget the exact timespans, but it was close to this):

    * Has not logged in for one year
    * Has not tweeted in a year and half
    * Does not any have applications linked to Twitter

If Instagram has a similar policy, I really don't have any sympathy that the username was taken.

StartSSL's denying free cert revocation does not make them untrustworthy from a technical perspective. The onus remains on the site owner to implement their site security properly and pay any fees necessary to do that. So the only issue here is a moral one and whether you believe they have a responsibility to revoke these certificates for free.

I think that given the extenuating circumstances, they probably should revoke the certificates if requested, but I have no right to demand that they do so.

The most annoying thing about internships are smug comments like this about interns.

Thank you so much for posting this! This was the list where I originally found the Mother Earth Mother Board article, but I only just remembered that after seeing your post.

If Microsoft's entire child-security protections don't work; I'd say that's fairly major. What might have been a very compelling feature for parents has been shown to be ineffective (if your kids know about the vulnerability, which for young children is admittedly unlikely).

They paid him at all, which is good, but it also shows that there's no reason they couldn't have authorized a bigger payout. It's still, at most, $350. Why not free Xbox Gold for life instead of one year? There's no cost to Microsoft.

I think this is a more plausible approach (and likely cheaper resource-wise to implement). Though, if the authentication requests somehow identify the Android app in question, it might be easy for Amazon to then perform a follow-up and download the app to verify their suspicions and avoid false-positives.

To be fair, revenue could have kept growing with the old design; you still don't know if you've achieved more with the new one!

It seems like you said that disdainfully/sarcastically, but if you had metadata about thousands of experiments and the ability to do a meta-analysis on that data; wouldn't you? It seems like a great opportunity to identify potentially destructive trends in the way your company runs experiments.

I can't believe they're still running this crap - I it's been a year and a half now? My opinion of Microsoft took a complete nosedive after seeing this campaign.