When leaving my grandparents' house for a long journey home, everybody was always instructed to give three rings when they get home safely. To this day I always let a phone ring three times before answering, partly in case it's an "I'm OK" message and partly because waiting for somebody to answer gives the caller time to think what they actually want to say.
My grandparents didn't have caller ID and so had no idea who was telling them they'd got home safely, but they could guess based on timings pretty well.
This works much less well in the days of digital call signalling. The "ringback tone" you hear -- the ringing in your earpiece when you call someone -- no longer corresponds in any way to the ring being generated on the other end. Ringback can start before or after ringing, so you can't even count on the number of seconds being the same, let alone the number of rings.
This also gives rsync, scp and all the other benefits of commandline ssh. Mintty was enough for me to be able to put off installing Debian for another month.
Don't worry about it, if a user doesn't know what Tweets or direct messages are then the service isn't for them. You'll struggle to get people to start using Twitter just to register domains when there's plenty of good registrars already, most people will have their favourite they use regularly.
I see this more as a service for power Twitter users so they can easily register new domains after having a drunken idea.
This app-in-a-day side project took slightly longer than it should have due to Heroku's recent problems with Amazon. Built with Padrino, Heroku and a Theme Forest theme, it went from idea to launch in just two days of work.
I believe this incident probably is the reason for the drop in price, along with the incident at Bitomat just before. It's just people reacting to vulnerabilities in the market though, so far there has been no evidence to suggest any of these bitcoins have been sold. If they were to be sold off in bulk then it would cause a much larger crash.
If they were to be sold off in bulk then it would cause a much larger crash.
Is there any reason why they couldn't just sit on them for a couple of month, and then start to sell them off slowly over the space of a few more month
On some badly configured Nginx servers the filename extension isn't parsed correctly. A php.jpg file will be executed as php because a badly written regex will match the .php.
Even if you don't have such vulnerabilities you probably don't want people to be able to upload images to your server. They could easily send you over quota on shared hosting and use your bandwidth for serving their own images (including child porn).
One hopes he is smart enough to have a solid legal argument for what he has done. If he loses the legal battle then it's going to set a bad precedent for all these academic document stores to continue keeping hold of this information. On the other hand, if he were to win then it may make it harder for groups like JSTOR to continue restricting access to their data.
A solid legal argument for switching your MAC address, hiding a laptop in a closet, and deliberately concealing your face to try to avoid recognition? He isn't going to win that defense.
Hypothetically: wiring closets are normal places for computers engaged in always-on network services. Putting a box over a laptop can keep it from getting stolen. Your bike helmet can end up in front of your face for a while while you're taking it off or putting it on. Switching your MAC address is reasonable if there's a MAC address conflict, or if you've gone and apologized to the network infrastructure guys for causing problems and they accepted your apology but didn't have the password for the DHCP server handy.
Try to remember you're seeing the picture painted entirely by the prosecution, without even the evidence that the grand jury saw to support it.
"...or if you've gone and apologized to the network infrastructure guys for causing problems..."
Read the indictment. He started on Sep 25th. He was blocked by IP on Sep 25. He switched his IP on Sep 26. The entire netblock was then blocked by admins. To try to turn the service back on for normal users, admins tried to block his MAC address on Sep 27, which worked until he changed it on Oct 2, and then added a second machine on Oct 8.
Your "hypothetical" defense doesn't even come close to flying. This isn't a little misunderstanding; this is network admins blocking access, and being circumvented, multiple times.
Thanks, but I know what the indictment alleges. But the facts of the indictment may be false, and there may be many other highly relevant facts that are omitted.
Find the Github account with the most forks and followers. That's probably the official repository and will link to the official website. They may not use Github of course, but there are other similar methods.
Other good signs are them being linked to from cdnjs, cached-commons or microjs. If I'm looking to solve a javascript itch I'll first browse these sites to see if there is a popular tool.
Also, if you're looking for jQuery then it's because you've read about it online somewhere. Simply go back and follow the links.
My grandparents didn't have caller ID and so had no idea who was telling them they'd got home safely, but they could guess based on timings pretty well.