arthur_debert

In Brazil's case, as least, it's simpler than that.

Mosquito eradication used to be done at the federal level, with military like organization. It kept things in control.

A few years ago it has been re-assigned to municipalities. Not only are local authorities less equipped to handle it, but mosquitoes do not conform to city boundaries. If one city is doing a good job but it's neighbor isn't you're screwed.

There's probably lots to be done through technical advances, but most of this could be avoided using common sense.

Has nothing to do with Java. There's no stack. They're simply chose the best Javascript compiler available.

Pretty simple, really

You're 100% right. It's just that security is so hard to get right. Only (maybe not even) the paranoid survive on that front. All it takes is one tiny detail to screw everything up. Leaving development artifacts on your live server is not very tranquilizing on that front.

Sorry. Here's the dissonance: we're building tools (including secure messaging) that are government snooping safe. We care deeply about the privacy and security of our users. And the web page that tells us that has mixed content warnings on ssl.

Maybe nitpicking, but security and OPSEC in particular requires insane focus and attention to every little detail. If you can trip up on the small things, I could hardly trust you to get the hard things right.

Thanks, that's a start. And of course, sorry for the misspelling.

In all seriousness, it would be more helpful if you'd mention what's wrong with the original article.

Since you seem to be knowledgeable and active on the SEO front, would you mind explaining what happened to MetaFilter?

Anyone with any experience in the SEO world knows that dchuck doesn't have a fucking clue anymore. He's no different than a talking head reporting on the daily ups and downs of the stock market on your local news.

Ad hominem. If instead of saying "X is an idiot, anyone can tell " you'd say what's wrong with his argument, you wouldn't look like a talking head.

Not always, i.e. drag along rights. Depending on how you structure your deal investors can override founders on acquisition offers.

Pagination does have it's advantages, namely: - Linking - Easier to grok where you are in the result set ( 3 out of 5 instead of the scroll bar that changes height)

It is language and written language that enables people to be connected and share ideas. There's no reason to credit specific networks like www or the internet with connecting people, because someone else would have done it (possibly better) if they had not.

I'm definitely not advocating for people not understanding the problem they want solved.

That said, your post sounds empty. Can you elaborate on why your own scrapers that you write from scratch make it all better? How do you your scrapers deal with encode detection, broken html, content prioritization and so forth?

I don't like the current options we've got in pythonland, but just writing: "this sucks, so I write my own" sounds like an ego trip. Can you describe in detail what BeautifulSoup (or lxml which is usually a better option) is doing wrong at the lower level and how your scripts are making it better?

EXIF metadata is easy to automate. What if there is a logo of a local business reflected on a surface that most people barely notice. Someone recognizes this, tracks the person down. It's a bit over the top, but these things happen. If that exposes one of those underage girls, who is accountable? Leaking real world information can be done in many and subtle ways. There are times where people think the image origin is untraceable, but it isn't. Will reddit take the heat? The poster? The mod?

People have been able to track people and locations surprisingly little information.

What if those photos do leak information that could enable real-life harassement (like EXIF metadata, street sign, etc) . Can we trust the submitter to guarantee it never will? If it happens, who's to blame?