[vonquant]

Hey, this looks great.

One thing you might want to consider is having one domain for a website about collectednotes (collectednotes.com) and another for hosting user's blogs (collectednotes.blog for example) because it is currently not clear what urls are official and made by you and which are just blogs made by anyone.

For example, https://collectednotes.com/accounts/ is genuine and made by you whilst https://collectednotes.com/account/ is a blog I just created. To me there seems a very real risk of users being mislead.

[vonquant]

On second thoughts, using a sub domain would make way more sense.

[eitland]

In that case: make sure you trust your registrar.

There was a story here a couple of weeks ago or something with a post mortem from someone who got their websites taken offline and access to their mail suspended or taken offline because some automated system at a giant corporation decided so.

It stayed offline for hours because there was no competent humans available with authority to override the clearly (AFAIK) stupid decision made by the system.

Personally a key takeaway from that (except not depending on said company) was to make sure one has at least two domains, preferably with two registrars, and make sure user generated content is not available on the one you depend on for email etc.

[chrismorgan]

The story in question: https://blog.gitbook.com/tech/post-mortems/06-20-gitbook-dom... (https://news.ycombinator.com/item?id=23417046).

Note that in that case the user content was on a separate domain—the registrar blocked the entire account.

[eitland]

Oh. Possibly even worse.

(Although I think there might have been some comments about user generated content on the main domain.)

[dctoedt]

Great tip - got a link for the story, by any chance? Or do you remember who the company was, so I can search for it myself?

EDIT: I couldn't find anything directly on point, but I did find this related horror story about a company whose ICANN email contact information no longer worked because the company's contact person had left the company. An ICANN email to the contact person bounced back. ICANN took the entire domain offline. The company's Web person had a lot of trouble getting through to a human at ICANN to straighten things out — and even then: "To make a long story short, my client was required to submit articles of incorporation, bank statements and other documents in order to get the domain working again." [0]

EDIT 2: Thanks to Chris Morgan, who provided a link to a GitBook horror story. [1]

I added both stories to my "Startup Law 101" page [2], with a hat tip to both Erik and Chris.

[0] https://www.skyhoundinternet.com/2017/05/17/website-email-ge...

[1] https://news.ycombinator.com/item?id=23516675

[2] https://www.oncontracts.com/startup-law/#Use_a_separate_Web_...

[alecrosa]

ah good catch thank you

[rochak]

+1

[kaushikt]

Exactly. Having a bunch of keywords reserved like Twitter does would be handy.