731 karma · joined October 2, 2013
Not sure what you mean about putting state in the repo. It's possible of course since you can stuff anything in there, but what would be the advantage? It wouldn't integrate with GitHub any better and it would throw away the real-time updates, queries, etc., available thanks to Firebase.
As for GitHub integration, I agree it's not ideal but it's the best their slightly brain-dead review API will allow. Getting the whole team to adopt the tool is much better, but is obviously quite a bit harder. Though that's probably why I'm seeing a lot more success in the enterprise space, where top-down diktats are par for the course.
So my advice would be to look for a co-founder, sure, but don't discount the option of going it alone. Remember that good co-founder > solo >> bad co-founder!
Yet another way in which the traditional publishing structure actively harms science.
I made a similar decision with much less of a financial cushion (and without moving away from the west coast) and it worked out OK. I'm happy now and don't regret giving up the millions. YMMV, of course. One tip: make it your goal to get to ramen profitability ASAP, not in 2-3 years -- it has a wonderful way of focusing your work.
Good luck whatever you choose, and keep in mind that either decision will remain reversible for at least a few years. If you go out on your own, I don't think having "I tried to run my own startup, failed, and learned a lot" will be a negative when seeking another tech job, and you can always move back.
That's actually an interesting question, I think: should we assign (formal, legal) fault to self-driving cars based on their actual capabilities, or on the capabilities of an average human driver in similar circumstances? What do we currently do when humans of very unequal skill (e.g., a race car driver vs daily commuter) have an accident -- does the race car driver potentially shoulder more of the blame? If not, should self-driving cars be treated differently?
Honest questions, I'm not sure how I'd answer them myself.
- Incorporate your business outside the EU.
- Have no offices in the EU.
- Reside outside the EU.
- Not visit the EU (?).
- Not employ any EU residents.
- Not target any advertisements about your business to EU countries.
- Only offer your site in your local language and/or English.
- Don't register your site in an EU TLD.
At that point, as far as I can tell (and of course I'm not a lawyer), you have no EU presence and even the GDPR admits that it doesn't apply to you. Presumably these conditions apply to the vast majority of small businesses where dealing with random claims of extra-territorial jurisdiction is just a waste of time.
This being HN, I'm sure somebody will be ecstatic to correct me if the above is wrong.
...
> it is still unclear who won
AFAICT, the GDPR consider an IP address to be PII. So collecting visitor logs or sticking an analytics script on the page -- even without asking people to sign in or otherwise identify themselves -- would fall under the purview of the GDPR. I don't think doing such things should cross the line into "active character".
It's also a terrible idea to infer intent from offering translations in other languages. As another comment pointed out (I presume correctly) there are more German speakers outside Germany than there are within its borders. Why should trying to improve the accessibility of a web site by people around the world make one susceptible to the laws of a language's native country?
As you say, the implied end state is the real problem: do I now need to learn about the relevant laws of every country whose residents (or even citizens?) might visit my web site? That's regulation without representation, and should be resisted on principle IMHO. Or will every site need a standard disclaimer that it's only intended for residents of X?
Perhaps some creative lawyer will figure out how to add a clause to Terms of Use that shifts responsibility for damages incurred by exposure to extraterritorial laws to the offending (offended?) user, and we can have a detente through mutually assured destruction of dueling lawsuits. :)
And just to preempt any criticism from the European peanut gallery, I'm in favor of stronger privacy protections on the Internet but they need to be worked out and agreed on globally, not imposed unilaterally by claiming extraterritorial jurisdiction.
In what ways do you think the GDPR is distinct from the laws in the present case? Let's say, for argument's sake, that gutenberg.org starts capturing PII about visitors and storing it without conforming to the GDPR. Do you think it would be fair for the EU to sue them and (attempt to) enforce their law? If so, why?
> All of the bacon we sell is made without synthetic nitrates or nitrites.
Is that the dodge mentioned in the article where they actually do use nitrates from celery instead, which are just as bad even though they're natural?
> "we now expect it to last 5 years"
> That will allow the satellite to record more than 10 billion cosmic ray events.
Assuming DAMPE continues detecting cosmic ray events at its current rate, I think the total number after 5 years would be a bit over 5 million. That's a few magnitudes off of 10 billion... Math fail, or do I misunderstand something?
1.5m / 530d * 5y * 365d/y = 5.165m