PROJET AUTOBLOG


Chromic

Site original : Chromic

⇐ retour index

Transferred

mardi 4 avril 2017 à 02:00

I've transferred the chromic.org domain from Dreamhost to Hover. Mostly because of UI/UX reasons.

Back in 2009, when I was looking to get a domain, I chose DreamHost for Shared Hosting. They’re also a registrar, so that’s who I registered the domain with.

A couple of years later, I moved the hosting part to Linode and kept DreamHost as the registrar. Linode doesn’t do domain registrations, and I never had any problems with my domain over at DreamHost so I wasn’t really looking for alternative registrars.

Recently, I started looking into the possibility of implementing DNSSEC, and while DreamHost supports it (as long as you don’t use their nameservers), I couldn’t find the options (DNS glue, DNSSEC fields) myself in the account settings. While hunting around for those, I realized that the vast majority of everything I was seeing on the screen were menus/options completely useless to me since I’m not hosting anything with them.

Then, I came across an article that suggests I need to create a support ticket to have support complete the configuration. Blech. What is this? 1997? I never had to deal with DreamHost support much, and the couple of times I contacted them they were quick to respond and helpful, but I’d very much rather have the option to do this on my own.

I did a couple of searches to see what my options were and decided to move to Hover. They don’t do hosting, their UI focuses on domain-related features, and the glue/DNSSEC settings aren’t hidden away multiple levels deep or completely missing.

More importantly, I can set those up myself. Win!

The transfer itself went without a hitch. No suprises, no downtime, and ultimately transparent. So kudos to both DreamHost and Hover for making that happen painlessly.

Transferred

mardi 4 avril 2017 à 02:00

I've transferred the chromic.org domain from Dreamhost to Hover. Mostly because of UI/UX reasons.

Back in 2009, when I was looking to get a domain, I chose DreamHost for Shared Hosting. They’re also a registrar, so that’s who I registered the domain with.

A couple of years later, I moved the hosting part to Linode and kept DreamHost as the registrar. Linode doesn’t do domain registrations, and I never had any problems with my domain over at DreamHost so I wasn’t really looking for alternative registrars.

Recently, I started looking into the possibility of implementing DNSSEC, and while DreamHost supports it (as long as you don’t use their nameservers), I couldn’t find the options (DNS glue, DNSSEC fields) myself in the account settings. While hunting around for those, I realized that the vast majority of everything I was seeing on the screen were menus/options completely useless to me since I’m not hosting anything with them.

Then, I came across an article that suggests I need to create a support ticket to have support complete the configuration. Blech. What is this? 1997? I never had to deal with DreamHost support much, and the couple of times I contacted them they were quick to respond and helpful, but I’d very much rather have the option to do this on my own.

I did a couple of searches to see what my options were and decided to move to Hover. They don’t do hosting, their UI focuses on domain-related features, and the glue/DNSSEC settings aren’t hidden away multiple levels deep or completely missing.

More importantly, I can set those up myself. Win!

The transfer itself went without a hitch. No suprises, no downtime, and ultimately transparent. So kudos to both DreamHost and Hover for making that happen painlessly.

Renewed

samedi 4 mars 2017 à 06:00
I just renewed the chromic.org domain for another two years:
Chimo Chimo
Boop! Renewed chromic.org. You guys are stuck with me for at least another two years.

The act of renewing the domain kind of felt like the beginning of a new year, somehow. A good time to reflect on what I've done with the domain since last time I renewed it, to think about where it's going, what the future projects are.

I'm not going to lay down plans for the next two years in this post because frankly, I haven't thought about it that far ahead. But I can try to give an overview of the plans I have for the near-future. Maybe publishing those plans here is going to give me a reason to get to them faster than I normally would.

Serving DNS

Right now, I’m hosting a bunch of stuff (including this blog) on Linode, and I’m using Linode’s nameservers for DNS. Everything’s been working well, but I want to try and run my own DNS server for my (sub)domains. There are a couple of reasons for that. One reason is “Project Autonomous” driven: don’t rely on third-parties whenever possible. The other reason is because Linode’s nameservers don’t support DNSSEC, which brings me to my second item in my plans.

DNSSEC

I want to implement DNSSEC. I’m not sure what else to say about this other than “because why not!”. I think it’ll be interesting and I might learn a couple of things along the way.

DANE

I also want to implement DANE, for the same reasons listed for DNSSEC, really.

Indieweb

The *.chromic.org “environment” has grown and evolved and changed over the years. When I started fiddling around with all the platforms and things on here, I wasn’t aware of the Indieweb’s POSSE, webmentions, etc. I kind of wedged webmentions on here at some point, but I’d like to make Indieweb a first-class “citizen” of this place.

For example, I can receive webmentions, but it’s a bit of a pain to reply or send them at the moment. I do have plans and tools in mind to fix this problem, and I hope to get to it soon.

HSTS

[ update: This is done!]

I don’t know why, but I haven’t enabled HSTS on my (sub)domains yet. I want to do that.

Content Security Policy Headers

I want to enable restricitve CSP headers on all subdomains.

Enable Brotli Compression via nginx

[ update: This is done!]

I want to enable Brotli compression on my nginx server. I need to grab the module and compile nginx against it. Not a big deal. I might use the Arch Build System (ABS) for that. I don’t know yet.

Home network (unrelated, bonus item)

This has nothing to do with the domain renewal or the Linode VPS, but since I’m making a list of things I want to do I’m adding it here.

I recently got a couple of network devices that allow me greater control over my network (compared to the generic ISP-provided router/modem I was using before) and I need to sit down and configure my home network with the ideas I have in mind.

Once that’s done, I’m going to have a blog post dedicated to that configuration on here.

Renewed

samedi 4 mars 2017 à 01:00
I just renewed the chromic.org domain for another two years:
Chimo Chimo
Boop! Renewed chromic.org. You guys are stuck with me for at least another two years.

The act of renewing the domain kind of felt like the beginning of a new year, somehow. A good time to reflect on what I've done with the domain since last time I renewed it, to think about where it's going, what the future projects are.

I'm not going to lay down plans for the next two years in this post because frankly, I haven't thought about it that far ahead. But I can try to give an overview of the plans I have for the near-future. Maybe publishing those plans here is going to give me a reason to get to them faster than I normally would.

Serving DNS

Right now, I’m hosting a bunch of stuff (including this blog) on Linode, and I’m using Linode’s nameservers for DNS. Everything’s been working well, but I want to try and run my own DNS server for my (sub)domains. There are a couple of reasons for that. One reason is “Project Autonomous” driven: don’t rely on third-parties whenever possible. The other reason is because Linode’s nameservers don’t support DNSSEC, which brings me to my second item in my plans.

DNSSEC

I want to implement DNSSEC. I’m not sure what else to say about this other than “because why not!”. I think it’ll be interesting and I might learn a couple of things along the way.

DANE

I also want to implement DANE, for the same reasons listed for DNSSEC, really.

Indieweb

The *.chromic.org “environment” has grown and evolved and changed over the years. When I started fiddling around with all the platforms and things on here, I wasn’t aware of the Indieweb’s POSSE, webmentions, etc. I kind of wedged webmentions on here at some point, but I’d like to make Indieweb a first-class “citizen” of this place.

For example, I can receive webmentions, but it’s a bit of a pain to reply or send them at the moment. I do have plans and tools in mind to fix this problem, and I hope to get to it soon.

HSTS

[ update: This is done!]

I don’t know why, but I haven’t enabled HSTS on my (sub)domains yet. I want to do that.

Content Security Policy Headers

I want to enable restricitve CSP headers on all subdomains.

Enable Brotli Compression via nginx

[ update: This is done!]

I want to enable Brotli compression on my nginx server. I need to grab the module and compile nginx against it. Not a big deal. I might use the Arch Build System (ABS) for that. I don’t know yet.

Home network (unrelated, bonus item)

This has nothing to do with the domain renewal or the Linode VPS, but since I’m making a list of things I want to do I’m adding it here.

I recently got a couple of network devices that allow me greater control over my network (compared to the generic ISP-provided router/modem I was using before) and I need to sit down and configure my home network with the ideas I have in mind.

Once that’s done, I’m going to have a blog post dedicated to that configuration on here.

Renewed

samedi 4 mars 2017 à 01:00

I just renewed the chromic.org domain for another two years:

Chimo Chimo
Boop! Renewed chromic.org. You guys are stuck with me for at least another two years.

The act of renewing the domain kind of felt like the beginning of a new year, somehow. A good time to reflect on what I've done with the domain since last time I renewed it, to think about where it's going, what the future projects are.

I'm not going to lay down plans for the next two years in this post because frankly, I haven't thought about it that far ahead. But I can try to give an overview of the plans I have for the near-future. Maybe publishing those plans here is going to give me a reason to get to them faster than I normally would.

Serving DNS

Right now, I’m hosting a bunch of stuff (including this blog) on Linode, and I’m using Linode’s nameservers for DNS. Everything’s been working well, but I want to try and run my own DNS server for my (sub)domains. There are a couple of reasons for that. One reason is “Project Autonomous” driven: don’t rely on third-parties whenever possible. The other reason is because Linode’s nameservers don’t support DNSSEC, which brings me to my second item in my plans.

DNSSEC

I want to implement DNSSEC. I’m not sure what else to say about this other than “because why not!". I think it’ll be interesting and I might learn a couple of things along the way.

DANE

I also want to implement DANE, for the same reasons listed for DNSSEC, really.

Indieweb

The *.chromic.org “environment” has grown and evolved and changed over the years. When I started fiddling around with all the platforms and things on here, I wasn’t aware of the Indieweb’s POSSE, webmentions, etc. I kind of wedged webmentions on here at some point, but I’d like to make Indieweb a first-class “citizen” of this place.

For example, I can receive webmentions, but it’s a bit of a pain to reply or send them at the moment. I do have plans and tools in mind to fix this problem, and I hope to get to it soon.

HSTS

[ update: This is done!]

I don’t know why, but I haven’t enabled HSTS on my (sub)domains yet. I want to do that.

Content Security Policy Headers

I want to enable restricitve CSP headers on all subdomains.

Enable Brotli Compression via nginx

[ update: This is done!]

I want to enable Brotli compression on my nginx server. I need to grab the module and compile nginx against it. Not a big deal. I might use the Arch Build System (ABS) for that. I don’t know yet.

Home network (unrelated, bonus item)

This has nothing to do with the domain renewal or the Linode VPS, but since I’m making a list of things I want to do I’m adding it here.

I recently got a couple of network devices that allow me greater control over my network (compared to the generic ISP-provided router/modem I was using before) and I need to sit down and configure my home network with the ideas I have in mind.

Once that’s done, I’m going to have a blog post dedicated to that configuration on here.