my fairly complex alphanumeric+symbol password IS in the dump, though not prepended truncated with 0's and the other one I found, which my coworker admitted was too short and alpha only, was in the dump with prepended 0's.
This could validate the fact that the truncated hashes are actually already cracked.
Whoops.
At the very least, it should have been longer.
No, there YOU go doing it again. That comment was in a long thread of context, and you willfully ignored that. The comment was also non-actionable and was clearly political hyperbole.
> There's not much room to joke about assassination and lynchings in a country that has a very recent history of assassinations and lynchings.
Sure there is.
It's little thing called "the first amendment". Perhaps you've heard of it? Read it closely. It makes no reference to "...unless there were lynchings in the last century".
Not really, no. SOPA actually exists, and you joked about hanging its supporters. The only context that would have made it remotely appropriate is neutral one, in which it was clear to any observers that encouraging the hanging of SOPA supporters (even 'jokingly') was not your position.
> It's little thing called "the first amendment". Perhaps you've heard of it? Read it closely. It makes no reference to "...unless there were lynchings in the last century".
Then let me rephrase: There's no room to joke about lynching elected representatives (or anyone) in civilized mature discourse.
There is also a long history of case law that restricts "fighting words", despite the first amendment.
My only take-away from your repeated reference to assassination/lynching is that you're someone who is likely to incite if not participate in violence, and beyond that, you personally decrease the overall quality of rational discourse in US politics.
You may not be enough of a nutcase to try to assassinate a politician -- I'm honestly not sure, given your remarks here, and your ownership of the tools to do so -- but your seeming need to joke about assassination contributes to a culture of political violence that may very well incite someone to do what you won't.
Absolutely agreed.
If some nut case puts up a website with the home address of someone, rants about a bounty on their head, etc., by all means, have an investigation and perhaps charges.
...but there's a difference between saying "This SOPA bill is insane. Rope. Lampposts." and driving to a person's house with a noose in the back seat.
There's not much room to joke about assassination and lynchings in a country that has a very recent history of assassinations and lynchings.
It's in bad taste, it can incite violence, and given your statements here, as well as those you've made elsewhere, I'm unsurprised that the law came down on you.
It is rare that libraries get rewritten from the ground up, so this would be the perfect time to get the code right.
Microcontrollers are fair game.
I can't think of one.
1) There is very little chance of them closing their doors in the near future as they raised a large series A and have great growth.
2) Having personally talked with Tikhon on the subject and it's clear that they plan to make this a stable platform for the longhaul. I would not hesitate to build a project on top of Parse they are a great group and would not leave their users hanging.
3) If you're still hesitant keep in mind you can still keep mission critical stuff on your own Servers/APIs and use Parse for Push Notifications/Location etc.. There is nothing locking you into what parts of the Parse SDK you use.
4) You can always export your data.
Until/unless they get purchased. As you said, it was a large series A.
> 2) Having personally talked with Tikhon on the subject and it's clear that they plan to make this a stable platform for the longhaul. I would not hesitate to build a project on top of Parse they are a great group and would not leave their users hanging.
If they're bought, it won't be their decision.
> 3) If you're still hesitant keep in mind you can still keep mission critical stuff on your own Servers/APIs and use Parse for Push Notifications/Location etc.. There is nothing locking you into what parts of the Parse SDK you use.
Push, etc, is the easy stuff.
> 4) You can always export your data.
It's the continued functioning of the code that I'm worried about, not the data.
Of course Heroku and similar services get you most of the way there, but there are plenty of client-side devs who would rather not deal with backend code at all.
PostgreSQL 9.3 is installed on your database server, the source is available, and it isn't going anywhere.
If Oracle discontinued their database platform tomorrow (unlikely!), your licensed copy will remain valid for a long time up until you swap it out for another closely compatible database.
If Parse closes their doors or exits tomorrow, that's it.
Compare to AWS: If Amazon discontinues EC2, other virtual hosting services exist. If they discontinue Beanstalk, then at least you were coding to a commmon servlet API. If they discontinue S3, there are some compatible competitors, but hopefully you wrote your data layer to be S3-agnostic.
I think non-standardized AWS services are more risky. More standardized fare -- EC2, Beanstalk, etc -- less risky. Basing your entire code base on pervasive use of Parse -- very risky.
I see this fellow as no worse than, say, a telemarketer. In fact, that's probably a good analogy to draw... except that I typically get more annoyed at telemarketers who hijack my time and attention, than AOL management seems to be at the person who overstayed his welcome in their building.
It's possible that I'm only as sympathetic to him as I am because he committed his offense in the course of trying to create something. Telemarketers don't offend me because they're annoying and presumptuous, but because they're lazy and unnecessary. If every telemarketer dropped off the face of the earth tomorrow, life would go on for the rest of us. If every kid with a bit of hustle and debatable judgment dropped off the face of the earth, things would go downhill in a hurry.