There is already pretty decent documentation on the Mastodon website for how to install and configure a server: https://docs.joinmastodon.org/admin/prerequisites/.

If you'd like to see the NixOS way I used, I could probably make a separate blog post about that.

When I got started with Mastodon, I myself was trying to find resources on when or when not to run your own Mastodon server, but had a hard time of finding that, so I hoped the post at least could help answer that for other people, although my experience with running Mastodon obviously is limited for now.

I've previously profiled pipenv and found it to be slowed down massively due to launching pip for each package it was working on. Unfortunately the maintainers think the progress bar is more important than performance: https://github.com/pypa/pipenv/issues/2207

That's interesting; they actually discuss the issue and talk about parallelizing it, but all you need to do is pass a requirements file to pip.

It would be nice if pip could act more as a base tool and pass information back to a wrapper.

I think most browsers don't include referrer information when clicking a link on a HTTPS site which leads to a HTTP site, but other than that I believe the information is kept by default.

Site owners can however tell browsers how much information they should include in the "referer" header via the "Referrer-Policy" response header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re....

Perhaps you can use my command line image printer for something like that: https://github.com/Tenzer/explosion.

I can definitely relate to that, my biggest pet peeve is probably people writing ElasticSearch instead of Elasticsearch - even though it isn't written like that anywhere on the official website.

On the topic of the Schuko plug, I never really understood why there had to be that many variations of it. Being from Denmark, I have more often than not had problems with the ground pin obstructing me from using a Danish plug in other countries. It has often times lead me to either saw off the ground pin, or replace the plug with a two-pin connector without the ground pin - in both cases decreasing the security of the plug for accessibility.

Python 3.4? Really? Why not 3.5!

The post ends with "We look forward to your feedback as you try out nginScript [...]" but it doesn't mention where we can test it out. Does anybody know more about that?

It's here: http://hg.nginx.org/njs/

It might be worth noting that if you pickle data in Python 3 then it actually has protocol versions which aren't compatible with Python 2: https://docs.python.org/3/library/pickle.html#data-stream-fo....

Sure, that's also what I cover in the post. The latter part about rewriting is only relevant when you want to have the service behind an ELB to be located at something else than "/".