You aren't using your own domain because Google may forget to renew their domain, you are using your own domain so you are not relying on Google to make your content available. If you are afraid that your registrar may kick you out, you should also be afraid that Google may kick you out too - which actually has a higher chance to happen than losing your own domain (assuming you are paying for it).

Personally after losing my blog when Posterous shut down i decided i do not want to bother with 3rd party blog services anymore.

You can petition ICANN if you lost a domain that you paid for. As long as you are the rightful owner it will be returned to you. Keep a active credit card on file with your registrar and keep a credit with them as well. All the horror stories I see are cases where someone stops paying.

https://www.icann.org/resources/pages/help/dndr/udrp-en

> As long as you are the rightful owner it will be returned to you.

As long you can prove you are the rightful owner. Sometimes that's much easier said than done, especially to a particular burden of proof they might require to pull the domain away from someone actively using it.

Was running a multi hour deploy. Only minor features, so low risk.

Everything broke with our biggest client.

After a massive scramble it turned out our clients certificate had expired, in middle of the deploy.

  So our system could no longer talk to them.

Whoops

It's going to be a lot easier for Google to do that to get blogspot.in back versus if I were to do it.

> You would have much more likely chance being kicked by the registrar/card not accepted/country ban/forgot password/domain hacked/forgetting to renew and myriad of other reasons...

Folks underestimate how easily this can happen and how very painful the entire process can be: https://news.ycombinator.com/item?id=3597025

There's pros and cons. I had a 4 letter .com back in the late 90s, but I was on holiday and my card expired - the hosting company emailed me, but clearly I didn't get it, so they didn't renew, and "ename technology" have been squatting it for 20 years.

I always have two cards on file with my registrar, but this year I had to cancel one card and the other one expired. Thankfully I was on top of my emails but I came within a month of losing my domains, which all kind of renew around the same time. It's frustrating to have to worry about this every once in a while.

Then renew 2 years at a time and then set a reminder to extend the renewal every year? That way you have a full year of leeway.

I have a lot more faith in me maintaining my personal domain name than google maintaining whatever service.

I also get evicted if I don’t pay rent on time. Paying recurring fees so services remain available is part of being a functional person.

Medium going out of business seems inevitable.

Your probably right.

If 1+ billion internet users had their own domain names, we'd never hear the end of the

Never use your own domain for anything ever

horror stories.

Or there might be a very robust infrastructure in place to prevent that from happening because there is now a multi-billion dollar market that companies want to serve.

Well I assume the comment is aimed at HN people not everyone in the world.

Yes because google never kills off services...

Never

ohh wait https://killedbygoogle.com/

It says AngularJS is killed off. That doesn't sound right... can someone fill me in?

As mentioned... it's Angular "1" and it's planned for July 2021 when LTS ends.

https://docs.angularjs.org/misc/version-support-status

Thanks for clearing that up!

This feels like it probably doesn't belong on this site. We don't say Google "killed" Android (Nougat), it's just an old EOL version. I've not used Angular, so maybe there are some salient differences I'm not appreciating.

The differences between AngularJS and Angular are roughly at the same level as the differences between Angular and React or Angular and jQuery.

Even so, it's not exactly comparable to killing a service. If you really want to continue using Angular 1, you can. You can even fork it and keep it up to date yourself. That's completely different from abandoning a proprietary service.

Lots of people don't like Angular-non-js, since it makes a lot of breaking changes and, among other things, switches to Typescript. AngularJS going EOL is effectively equal to it dying.

Angular, a typescript based framework is different from AngularJS a javascript based framework even though that have the same root name

Google killed AngularJS.

See: https://docs.angularjs.org/misc/version-support-status

Looks like it will get security patches through parts of next year.

Angular, the successor to AngularJS is still alive and kicking.

I tweeted the site owner he refused to remove it. According to him its angular js is killed

This isn’t a great example, it’s succeeded by “Angular”, v2 of AngularJS.

Angular 1, not Angular 2 or more accurately, AngularJS was killed off and superseded by Angular.