HN user

arthur_debert

95 karma

http://www.stimuli.com.br -> personal website

Founder at https://www.loggi.com/ building the future of logistics in Brazil

Posts1
Comments42
View on HN

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.

While you're right that as a judge you must respect the law, we as a society must re-evaluate it's usefulness and purpose.

You're looking at this the other way round. It's not that privacy makes it harder to foster a civilized society, but removing makes it totally impossible.

Is amuses me that you would see this as post Snowden or even American issue. As a Brazilian I know our state is much more corrupt and inapt, and the risks are an order of magnitude higher for us, Snowden or not.

See here for some of the rational: http://www.thoughtcrime.org/blog/we-should-all-have-somethin...

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.

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?

Simple: public transportation sucks and will probably take twice the time to get to your destination. Motorbike: you have no idea how madly people drive down here, and how many motorbikers day each day. Also, it rains (heavily) almost daily from November to April - definitely not fun on a bike

I don't think the point is that they fail, but how easy for them it is to get money (then later valuations) without having users nor revenue. That is what worries people when they draw the similarities with the first bubble.

We at http://www.universalsubtitles.org/en/ have. The code is open source https://github.com/pculture/unisubs/tree/dev/media/js/widget . I'm writing a blog post about that should be up still today on our development blog. TL;DR It's full of good code, some interesting idea. But, tries to make Javascript feel like Java (annotated types, very verbose etc). Also makes it difficult to use other libs (specially with the compiler in advanced mode). I don't think it's a good option for most teams.

Also look that the stage (canvas) size for the demo (this used to make a big difference in older versions of the player at least).

I find it ironical to read this comment on HN.

What's the fuss about HN? What aren't we having this discussion on redit, or digg, or 4chan? Or metafilter?

Software and specially social software is not a list of features. You could replicate Twitter's functionality and that wouldn't make people leave twitter.

Instagram has build a solid community, and that is what social software is all about.

I think for the general case yes, but there are still some rough spots on certain hardware (e.g. power management on macbook pros and so on). Some other smaller things, like attaching an apple keyboard to ubuntu creates up with pretty weird mappings for a couple of keys. Configuring the keyboard under those conditions is pretty confusing.

The issue is not that one would like to tinker, but that without a significant time investment tinkering, you can't get the basics working.

Nothing precludes the OS from being tinkerable but mostly working out of the box.

It's possible but that probably doesn't mean integration is easy. Writing async code in python forces you to use the-twisted-way or the-greenlet-way. That is the problem with language / standard lib lack of support for async calls - that is part of the appeal of node.js.

I doubt just reusing the twisted code inside the django app makes much sense for that reason (nor does the other way round).

There are tons of goodies in there, and the author is doing a hell of a service to Emacs users.

That said, a part of my can't but sigh... Now we have new completion & new electric pairs. How is that going to propagate to other modes? Just the thought of new the work involved in diagnosing which mode is using what, and how to adapt for it gives me the chills.

The package manager looks nice, but how can it handle stuff hosted on a git rep? How are changes show? Without all of this sorted out, it's usefulness is severely diminished.

Honestly, I'm surprised how cheap that is. If you take into consideration that computers cost between 2x and 3x more, bandwidth 4x more, higher taxes and almost the same wages, it's a steal.

I expected it to cost between 2 to 3 times more.

Our current providers tend to cost 4x to 8x that, so I'm really curious to see how the market will behave.

It's not that much luck. I've decided to go with Django in 2006. Still going strong, five years later. You'll do fine going with Django or Rails, but the time when this decision would be more rewarding was 5 years ago.

I've done mostly flash for a living since 2001, in 2007 I decided to move on. It was obvious it wasn't going anywhere.

Balsamic is probably the only application written in Flash that I use regularly. A platform that has so few applications after so many years in development is clearly struggling.

Building Lanyrd 15 years ago

Django compressor has another issue on load balanced environments: the cached key uses the hostname of the machine , which really made it impractical for us. I promised Jannis a clean patch for this, but haven't found the time to do so...

In our case we have a utility machine that compiles media and deployes it but that machine doesn't even run a webserver at all...

https://github.com/jezdez/django_compressor/blob/develop/com...

Building Lanyrd 15 years ago

Of course, but when in development, we use the a template tag that inserts the original url (no commit hash mangling on MEDIA URL), which means that yes, for each deployment we nuke statics, but on our dev cycle that would happen any way (it's very rare to have a release that does not touch static files), so it's not an issue in practice