in Europe, they have to (albeit with an adapter) due to EC regulations. Seems like a positive use of government regulation, and with the amount of government interest in electric cars, my outsider view is that a federal standard for charging ports would not get an excessive amount of lobbying resistance.
iPhones don't utilize public roads and aren't really a necessity in getting to work. Cars are for most of those without a public transport option.
If I can't buy gas from Shell with an Exxon fuel filler of a particular model car and there are mostly Shell stations in my area, I'm not buying that car.
Standardizing will only benefit electric car manufacturers. Surely, they can all get together and agree to one standard as they will benefit from any third party willing to create a charging station franchise. IMO non-standard in this case is a very poor business decision.
My old geology teacher said that the test-ban-treaty was a huge boon to geologists, since there was now a bottomless pit of money to be used to build seismographs anywhere you wanted to build them.
An exploding buried nuke will send energy in all directions, thus the first movement of the ground is away from the epicenter for all measurement stations around.
An earthquake usually comes about because tension between different areas release, and in that case one part of the ground will start their movement away from the epicenter, the other part will start into the direction of the epicenter.
However, one might need measurement stations covering the whole globe to detect it this way.
edit: Hm, I can't find the image that I've seen in a plate tectonics book a year ago, but here's a plot from a model:
http://www.wlandry.net/Projects/Gamra
If you look at the arrows in light blue, you can see that some point into the direction of the epicenter while some point away, thus it's an earthquake and not a nuke.
Pretty! I had wanted to make something like this, but one feature I thought of and you didn't do: For the entered regexp, generate 20 random matches and show them to me.
Use case for this feature: You encounter an undocumented regexp in someone else's code and want get a few quick examples of what it matches.
Since I'm usually starting with a bunch of data I want to parse/match/chop, I like going the other way - pasting a couple of lines into Patterns ( http://krillapps.com/patterns/ ) and tweaking my expression until it looks right. This would be a useful addition to help debug in place.
Mechanism: I wrote myself a Google doc with my new year's resolutions and I'm going to set Astrid reminders to review them quarterly (let's say at the end of March, June, September, and in time for 2014's resolutions). I agree with @kator's comment that it's totally arbitrary. Maybe, but it's convenient!
Also I'm sharing it here to make myself feel like I'm obligated to someone. :)
The full doc would be boring to put here, so here is the tl;dr version:
1. Productivity
2. School
3. Fitness
Slightly longer version:
1. Productivity - primary goal: "I will be productive and inspired all the time." Practically, this means wasting less time, doing more personal coding projects, learning new skills, and other things.
My first task in this goal is to finish reading and start implementing GTD.
A couple of inspiring discussions:
http://news.ycombinator.com/item?id=4979938http://news.ycombinator.com/item?id=4982649
2. School (I am a master's degree student) - primary goal: "I will finish all my course requirements and at least 70% of my thesis research and writing". (The definition of 70% is "feels like 70%".)
Secondary goal: "My school time will be much more relaxed and awesome than it is currently, and I'll leave more time for side projects, side work, and personal stuff."
It seems its a can of worms right now and the suitable fix seems to be removing the storage limit on shared folders (shared to those individuals who do not own the original folders being shared).
First of all, in Dropbox's defense, I probably did not give you guys enough time to respond before going public with this (also, living in Israel I sometimes forget that Sunday is a weekend for most people in the world). I apologize for that. I am not a journalist/blogger, and I was driven more by my emotions than by "journalistic ethics" (?) when submitting to HN.
Second, according to your support email (updated the original post with it) it looks like my particular case is going to be resolved. However, it does not seem to resolve the malicious use case I hinted at (and which people on HN did not seem to want to discuss that much): Give someone a terabyte as a gift, and then delete their account. In fact, from the support email it seems like it's even worse: The support staff will need the team admin to approve the account re-enabling. In the malicious case, the admin would not approve.
[EDIT: Recalled a third point I wanted to make.]
Third, regarding what you said "it's not possible for us to differentiate between Team data and personal stuff in the same account". I simply don't understand why this is true. Maybe the general case is not like mine, but my Dropbox folder just has a bunch of subfolders, exactly one of which belongs to the "team". Is it possible that certain folders have mixed personal-and-team content? How does that even work?
If you saw my account (I don't know if you can... but your code can) it would be blatantly obvious which folders (all but one) are personal.
When migrating an account into a team, the account and all the data in the account becomes managed by the Teams admin (shared or otherwise). Letting an existing account to join a team lets us smoothly support the situation where a user has created a Dropbox account separately and needs to move that account into the team.
For most cases though, users should create a new account for the team. The Dropbox for Teams sign up process guides users towards creating a new account when joining a team for this reason.
From your reply, it sounds much worse than I thought. I had no idea my team admin could see all my data until now!
If joining a team account changed after your October changes, then maybe it's okay now. But I included in my post the email I got for joining the team, and it makes no mention of the fact that the team admin now owns my data. One would think this email should be less bland and more cautioning.
