Your name servers seem to be ns[1-5].he.net, and ns1.he.net doesn't know what blog.lacour.me is:
> blog.lacour.me
Server: ns1.he.net
Address: 216.218.130.2
*** No address (A) records available for blog.lacour.me $ dig @75.75.75.75 blog.lacour.me
QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
{{ no answer }}
$ dig @75.75.75.75 blog.lacour.me
QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
blog.lacour.me. 75275 IN CNAME silvrback.herokuapp.com.
silvrback.herokuapp.com. 156 IN CNAME us-east-1-a.route.herokuapp.com.
us-east-1-a.route.herokuapp.com. 30 IN A 23.23.208.103 host blog.lacour.me
blog.lacour.me is an alias for silvrback.herokuapp.com.
silvrback.herokuapp.com is an alias for us-east-1-a.route.herokuapp.com.
us-east-1-a.route.herokuapp.com has address 54.83.3.141Mozilla's "Reader View" is a fantastic step towards establishing a consistent (and user-configurable) look-and-feel across the web. But its domain is still very narrow and wouldn't apply to Slack, unfortunately. Yet it's the only product I know of that's even working towards this kind of goal.
That could be a future GTK browser :) dynamically downloads a glade ui file and python + CSS scripts to bring the web to GTK.
Their business pricing, which includes SSL, starts at $399 per month.
Or you can self-host with something like http://staytus.co/
Yes you have to set up multi-AZ deployment, but that's super simple on AWS. Add in their new free SSL certs and voila!
Even as a small startup, that's easily worth the time to save nearly $5k per year.
I've had web browsers that default to white screen flashing on new tabs, and most don't respect your native theme.
My current workaround]in Firefox is to disable background images, set default foreground/background and link colours. Set a default font, and ensure font sizes don't fall below a certain size.
Some text inputs have a dark background and a dark font. Which makes things very difficult. I'm typing blind.
Another issue is that many designs use background images where you would expect foreground placement. For example Instagram doesn't work for me. Slack is usable, but some image previews are lost. Other sites that rely upon imagery for navigation can pose a problem. The compose window in Gmail, I have to use mystery meat navigation to work out each button's function. Which is quite poor.
I've tried setting my own stylesheets in browsers where you can, but it's easy to break layouts.
Obviously accessibility is still overlooked by many site designers.
I also don't like being stuck in one browser, so a better cross application solution is preferable, rather than site specific fixes.
https://wiki.archlinux.org/index.php/firefox#Unreadable_inpu...
You can customise the colors according to your preference.
I also like the FT Deep Dark theme for firefox.
Not trying to dismiss this. I'd genuinely like to know as I'm often on my computer late at night.
Here is a link to the Github project: https://github.com/laCour/slack-night-mode
I wish the Slack App had a night theme..
It's also very nice that Flux is applied after this so I don't get a dark blue screen.
Oh my god they're `eval`ing url components