docs: Fix broken links, avoid redirects

docs/api/frontend.rst

@@ -10,7 +10,7 @@ The following requirements applies to any frontend implementation:
   opening TCP ports and exposing Mopidy for a group of clients.
 
 - A frontend MUST implement at least one `Pykka
-  <http://pykka.readthedocs.org/>`_ actor, called the "main actor" from here
+  <https://www.pykka.org/>`_ actor, called the "main actor" from here
   on.
 
 - The main actor MUST accept two constructor arguments:

docs/api/http.rst

@@ -61,7 +61,7 @@ JSON-RPC 2.0 messages
 JSON-RPC 2.0 messages can be recognized by checking for the key named
 ``jsonrpc`` with the string value ``2.0``. For details on the messaging format,
 please refer to the `JSON-RPC 2.0 spec
-<http://www.jsonrpc.org/specification>`_.
+<https://www.jsonrpc.org/specification>`_.
 
 All methods in the :ref:`core-api` is made available through JSON-RPC calls
 over the WebSocket. For example, :meth:`mopidy.core.PlaybackController.play` is

docs/changelog.rst

@@ -33,6 +33,8 @@ Bug fix release.
 - Docs: Resize and compress images, reducing the release tarball size from 3.5
   to 1.1 MB.
 
+- Docs: Fix broken links.
+
 
 v2.2.2 (2018-12-29)
 ===================

docs/clients/mpd.rst

@@ -6,7 +6,7 @@ MPD clients
 
 This is a list of MPD clients we either know works well with Mopidy, or that we
 know won't work well. For a more exhaustive list of MPD clients, see
-http://mpd.wikia.com/wiki/Clients.
+https://mpd.fandom.com/wiki/Clients.
 
 .. contents:: Contents
     :local:
@@ -72,7 +72,7 @@ with support for Linux, mac OS, and Windows.
 GMPC
 ----
 
-`GMPC <http://gmpc.wikia.com/wiki/Gnome_Music_Player_Client>`_ is a graphical MPD client (GTK+) which works
+`GMPC <https://gmpc.fandom.com/wiki/Gnome_Music_Player_Client>`_ is a graphical MPD client (GTK+) which works
 well with Mopidy.
 
 .. image:: mpd-client-gmpc.jpg

docs/clients/mpris.rst

@@ -4,7 +4,7 @@
 MPRIS clients
 *************
 
-`MPRIS <http://specifications.freedesktop.org/mpris-spec/latest/>`_ is short
+`MPRIS <https://specifications.freedesktop.org/mpris-spec/latest/>`_ is short
 for Media Player Remote Interfacing Specification. It is a spec that describes
 a standard D-Bus interface for making media players available to other
 applications on the same system.

docs/clients/upnp.rst

@@ -40,9 +40,9 @@ Using Mopidy-MPRIS and Rygel, or using Mopidy-MPD and upmpdcli.
 Mopidy-MPD and upmpdcli
 -----------------------
 
-`upmpdcli <http://www.lesbonscomptes.com/upmpdcli/>`_ is recommended, since it
+`upmpdcli <https://www.lesbonscomptes.com/upmpdcli/>`_ is recommended, since it
-is easier to setup, and offers `OpenHome 
+is easier to setup, and offers `OpenHome
-<http://www.openhome.org/wiki/OhMedia>`_ compatibility. upmpdcli exposes a UPnP
+<http://wiki.openhome.org/wiki/OhMedia>`_ compatibility. upmpdcli exposes a UPnP
 MediaRenderer to the network, while using the MPD protocol to control Mopidy.
 
 1. Install upmpdcli. On Debian/Ubuntu::

docs/codestyle.rst

@@ -21,7 +21,7 @@ Code style
     bar = 'I am a bytestring, but was it intentional?'
 
 - Follow :pep:`8` unless otherwise noted. `flake8
-  <https://pypi.python.org/pypi/flake8>`_  should be used to check your code
+  <https://pypi.org/project/flake8>`_  should be used to check your code
   against the guidelines.
 
 - Use four spaces for indentation, *never* tabs.

docs/contributing.rst

@@ -19,9 +19,8 @@ Mopidy and its extensions:
   Just sign in and fire away.
 
 - Our IRC channel: `#mopidy <https://webchat.freenode.net/?channels=#mopidy>`_
-  on `irc.freenode.net <http://freenode.net>`_,
+  on `irc.freenode.net <http://freenode.net>`_.
-  with public `searchable logs <https://botbot.me/freenode/mopidy/>`_. Be
+  Be prepared to hang around for a while, as we're not always around to answer
-  prepared to hang around for a while, as we're not always around to answer
   straight away.
 
 Before asking for help, it might be worth your time to read the
@@ -119,13 +118,13 @@ Pull request guidelines
      <http://365git.tumblr.com/post/3308646748/writing-git-commit-messages>`_
 
    - `A Note About Git Commit Messages
-     <http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html>`_
+     <https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html>`_
 
    - `On commit messages
      <http://who-t.blogspot.ch/2009/12/on-commit-messages.html>`_
 
 #. Send a pull request to the ``develop`` branch. See the `GitHub pull request
-   docs <https://help.github.com/articles/using-pull-requests>`_ for help.
+   docs <https://help.github.com/en/articles/about-pull-requests>`_ for help.
 
 .. note::
 

docs/devenv.rst

@@ -54,7 +54,7 @@ your regular Mopidy install, which you set up in the first step, is unaffected
 by your hacking and will always be working.
 
 Most of us use the `virtualenvwrapper
-<https://virtualenvwrapper.readthedocs.org/>`_ to ease working with
+<https://virtualenvwrapper.readthedocs.io/>`_ to ease working with
 virtualenvs, so that's what we'll be using for the examples here. First,
 install and setup virtualenvwrapper as described in their docs.
 
@@ -262,14 +262,14 @@ environments using the ``-e`` option, e.g. to run just unit tests::
 
     tox -e py27
 
-To learn more, see the `tox documentation <http://tox.readthedocs.org/>`_ .
+To learn more, see the `tox documentation <https://tox.readthedocs.io/>`_ .
 
 
 Running unit tests
 ------------------
 
-Under the hood, ``tox -e py27`` will use `pytest <http://pytest.org/>`_ as the
+Under the hood, ``tox -e py27`` will use `pytest <https://docs.pytest.org/>`_
-test runner. We can also use it directly to run all tests::
+as the test runner. We can also use it directly to run all tests::
 
     pytest
 
@@ -335,7 +335,7 @@ We're quite pedantic about :ref:`codestyle` and try hard to keep the Mopidy
 code base a very clean and nice place to work in.
 
 Luckily, you can get very far by using the `flake8
-<http://flake8.readthedocs.org/>`_ linter to check your code for issues before
+<http://flake8.readthedocs.io/>`_ linter to check your code for issues before
 submitting a pull request. Mopidy passes all of flake8's checks, with only a
 very few exceptions configured in :file:`setup.cfg`. You can either run the
 ``flake8`` tox environment, like Travis CI will do on your pull request::
@@ -362,8 +362,8 @@ If successful, the command will not print anything at all.
 Writing documentation
 =====================
 
-To write documentation, we use `Sphinx <http://sphinx-doc.org/>`_. See their
+To write documentation, we use `Sphinx <http://www.sphinx-doc.org/>`_. See
-site for lots of documentation on how to use Sphinx.
+their site for lots of documentation on how to use Sphinx.
 
 .. note::
 
@@ -509,7 +509,7 @@ For clarity, we can rename the ``origin`` remote to ``upstream``::
     upstream        https://github.com/mopidy/mopidy.git (push)
 
 If you haven't already, `fork the repository
-<https://help.github.com/articles/fork-a-repo/>`_ to your own GitHub account.
+<https://help.github.com/en/articles/fork-a-repo>`_ to your own GitHub account.
 
 Then, add the new fork as a remote to your local clone::
 
@@ -553,7 +553,7 @@ When everything is done and committed, push the branch to your fork on GitHub::
 
 Go to the repository on GitHub where you want the change merged, in this case
 https://github.com/mopidy/mopidy, and `create a pull request
-<https://help.github.com/articles/creating-a-pull-request/>`_.
+<https://help.github.com/en/articles/creating-a-pull-request>`_.
 
 
 Updating a pull request

docs/ext/backends.rst

@@ -45,7 +45,7 @@ Mopidy-Beets
 https://github.com/mopidy/mopidy-beets
 
 Provides a backend for playing music from your `Beets
-<http://beets.radbox.org/>`_ music library through Beets' web extension.
+<https://beets.io/>`_ music library through Beets' web extension.
 
 
 Mopidy-Dirble
@@ -151,7 +151,7 @@ Mopidy-Podcast-gpodder
 https://github.com/tkem/mopidy-podcast-gpodder
 
 Extension for Mopidy-Podcast that lets you search and browse podcasts from the
-`gpodder <http://gpodder.org/>`_ web site.
+`gpodder <https://gpodder.github.io/>`_ web site.
 
 
 Mopidy-Podcast-iTunes
@@ -169,8 +169,8 @@ Mopidy-radio-de
 https://github.com/hechtus/mopidy-radio-de
 
 Extension for listening to Internet radio stations and podcasts listed at
-`radio.de <http://www.radio.de/>`_, `radio.net <http://www.radio.net/>`_,
+`radio.de <https://www.radio.de/>`_, `radio.net <https://www.radio.net/>`_,
-`radio.fr <http://www.radio.fr/>`_, and `radio.at <http://www.radio.at/>`_.
+`radio.fr <https://www.radio.fr/>`_, and `radio.at <https://www.radio.at/>`_.
 
 
 Mopidy-RNZ
@@ -178,7 +178,7 @@ Mopidy-RNZ
 
 https://github.com/danbrough/mopidy-rnz
 
-Extension for playing `Radio New Zealands <http://www.radionz.co.nz>`_
+Extension for playing `Radio New Zealands <https://www.rnz.co.nz>`_
 podcasts,live streams and latest news bulletin.
 
 
@@ -240,7 +240,7 @@ Mopidy-TuneIn
 https://github.com/kingosticks/mopidy-tunein
 
 Provides a backend for playing music from the `TuneIn
-<http://tunein.com/>`_ online radio service.
+<https://tunein.com/>`_ online radio service.
 
 
 Mopidy-VKontakte

docs/ext/frontends.rst

@@ -55,7 +55,7 @@ Mopidy-Touchscreen
 https://github.com/9and3r/mopidy-touchscreen
 
 Extension for displaying track info and controlling Mopidy from a touch screen
-using `PyGame <http://www.pygame.org/>`_/SDL.
+using `PyGame <https://www.pygame.org/>`_/SDL.
 
 
 Mopidy-TtsGpio

docs/ext/http.rst

@@ -111,8 +111,8 @@ See :ref:`config` for general help on configuring Mopidy.
     allowed and so you don't need an entry for those. However, if your requests
     originate from a different web server, you will need to add an entry for
     that server in this list. For example, to allow requests from a web server
-    at 'http://www.my.web-client.com' you would specify the entry
+    at 'http://my-web-client.example.com' you would specify the entry
-    'www.my.web-client.com'.
+    'my-web-client.example.com'.
 
 .. confval:: http/csrf_protection
 

docs/ext/web.rst

@@ -162,7 +162,7 @@ https://github.com/pimusicbox/mopidy-musicbox-webclient
 
 The first web client for Mopidy, made with jQuery Mobile by Wouter van Wijk.
 Also the web client used for Wouter's popular `Pi Musicbox
-<http://www.pimusicbox.com/>`_ image for Raspberry Pi.
+<https://www.pimusicbox.com/>`_ image for Raspberry Pi.
 
 .. image:: /ext/musicbox_webclient.jpg
     :width: 696
@@ -225,7 +225,7 @@ Bootstrap by Wojciech Wnętrzak.
     :width: 696
     :height: 343
 
-To use, just visit http://mopster.cowbell-labs.com/.
+To use, just visit http://mopster.urizen.pl/.
 
 
 Mopidy-Jukepi

docs/extensiondev.rst

@@ -32,7 +32,7 @@ named Soundspot to Mopidy, you would name your extension's Python package
 ``mopidy_soundspot``.
 
 The extension must be shipped with a ``setup.py`` file and be registered on
-`PyPI <https://pypi.python.org/>`_.  The name of the distribution on PyPI would
+`PyPI <https://pypi.org/>`_.  The name of the distribution on PyPI would
 be something like "Mopidy-Soundspot". Make sure to include the name "Mopidy"
 somewhere in that name and that you check the capitalization. This is the name
 users will use when they install your extension from PyPI.
@@ -61,7 +61,7 @@ Example content for the most important files follows below.
 cookiecutter project template
 =============================
 
-We've also made a `cookiecutter <http://cookiecutter.readthedocs.org/>`_
+We've also made a `cookiecutter <https://cookiecutter.readthedocs.io/>`_
 project template for `creating new Mopidy extensions
 <https://github.com/mopidy/cookiecutter-mopidy-ext>`_. If you install
 cookiecutter and run a single command, you're asked a few questions about the
@@ -215,7 +215,7 @@ file::
 
 For details on the ``MANIFEST.in`` file format, check out the `distutils docs
 <https://docs.python.org/2/distutils/sourcedist.html#manifest-template>`_.
-`check-manifest <https://pypi.python.org/pypi/check-manifest>`_ is a very
+`check-manifest <https://pypi.org/project/check-manifest>`_ is a very
 useful tool to check your ``MANIFEST.in`` file for completeness.
 
 
@@ -485,7 +485,7 @@ If you make HTTP requests please make sure to respect the :ref:`proxy configs
 configured by the Mopidy user. To make this easier for extension developers,
 the helper function :func:`mopidy.httpclient.format_proxy` was added in Mopidy
 1.1. This function returns the proxy settings `formatted the way Requests
-expects <http://www.python-requests.org/en/latest/user/advanced/#proxies>`__.
+expects <https://2.python-requests.org/en/master/user/advanced/#proxies>`__.
 
 User-Agent strings
 ------------------
@@ -505,7 +505,7 @@ Example using Requests sessions
 -------------------------------
 
 Most Mopidy extensions that make HTTP requests use the `Requests
-<http://www.python-requests.org/>`_ library to do so. When using Requests, the
+<https://2.python-requests.org/>`_ library to do so. When using Requests, the
 most convenient way to make sure the proxy and User-Agent header is set
 properly is to create a Requests session object and use that object to make all
 your HTTP requests::
@@ -541,7 +541,7 @@ your HTTP requests::
     # ``session`` object.
 
 For further details, see Requests' docs on `session objects
-<http://www.python-requests.org/en/latest/user/advanced/#session-objects>`__.
+<https://2.python-requests.org/en/master/user/advanced/#session-objects>`__.
 
 Testing extensions
 ==================
@@ -554,8 +554,8 @@ extension in some unanticipated way.
 Before getting started, it is important to familiarize yourself with the
 Python `mock library <https://docs.python.org/dev/library/unittest.mock.html>`_.
 When it comes to running tests, Mopidy typically makes use of testing tools
-like `tox <https://tox.readthedocs.org/en/latest/>`_ and
+like `tox <https://tox.readthedocs.io/>`_ and
-`pytest <http://pytest.org/latest/>`_.
+`pytest <https://docs.pytest.org/>`_.
 
 Testing approach
 ----------------
@@ -646,9 +646,9 @@ file, and mocking the audio actor::
 The following libraries might be useful for mocking any HTTP requests that
 your extension makes:
 
-- `responses <https://pypi.python.org/pypi/responses>`_ - A utility library for
+- `responses <https://pypi.org/project/responses>`_ - A utility library for
   mocking out the requests Python library.
-- `vcrpy <https://pypi.python.org/pypi/vcrpy>`_ - Automatically mock your HTTP
+- `vcrpy <https://pypi.org/project/vcrpy>`_ - Automatically mock your HTTP
   interactions to simplify and speed up testing.
 
 At the very least, you'll probably want to patch ``requests`` or any other web

docs/history/changelog-0.x.rst

@@ -1897,7 +1897,8 @@ Please note that 0.6.0 requires some updated dependencies, as listed under
   subsystems: player, playlist, options, and mixer. (Fixes: :issue:`32`)
 
 - A new frontend :mod:`mopidy.frontends.mpris` have been added. It exposes
-  Mopidy through the `MPRIS interface <http://specifications.freedesktop.org/mpris-spec/latest/>`_ over D-Bus. In
+  Mopidy through the `MPRIS interface
+  <https://specifications.freedesktop.org/mpris-spec/latest/>`_ over D-Bus. In
   practice, this makes it possible to control Mopidy through the `Ubuntu Sound
   Menu <https://wiki.ubuntu.com/Sound#menu>`_.
 
@@ -2080,7 +2081,7 @@ loading from Mopidy 0.3.0 is still present.
 
 **Important changes**
 
-- Mopidy now depends on `Pykka <http://pykka.readthedocs.org/>`_ >=0.12. If you
+- Mopidy now depends on `Pykka <https://www.pykka.org/>`_ >=0.12. If you
   install from APT, Pykka will automatically be installed. If you are not
   installing from APT, you may install Pykka from PyPI::
 
@@ -2340,11 +2341,11 @@ This is a maintenance release without any new features.
 v0.2.0 (2010-10-24)
 ===================
 
-In Mopidy 0.2.0 we've added a `Last.fm <http://www.last.fm/>`_ scrobbling
+In Mopidy 0.2.0 we've added a `Last.fm <https://www.last.fm/>`_ scrobbling
 support, which means that Mopidy now can submit meta data about the tracks you
 play to your Last.fm profile. See :mod:`mopidy.frontends.lastfm` for
 details on new dependencies and settings. If you use Mopidy's Last.fm support,
-please join the `Mopidy group at Last.fm <http://www.last.fm/group/Mopidy>`_.
+please join the `Mopidy group at Last.fm <https://www.last.fm/group/Mopidy>`_.
 
 With the exception of the work on the Last.fm scrobbler, there has been a
 couple of quiet months in the Mopidy camp. About the only thing going on, has

docs/index.rst

@@ -60,8 +60,7 @@ To get started with Mopidy, start by reading :ref:`installation`.
 
 If you get stuck, you can get help at the `Mopidy discussion forum
 <https://discourse.mopidy.com/>`_. We also hang around at IRC on the
-``#mopidy`` channel at `irc.freenode.net <http://freenode.net/>`_. The IRC
+``#mopidy`` channel at `irc.freenode.net <http://freenode.net/>`_.
-channel has `public searchable logs <https://botbot.me/freenode/mopidy/>`_.
 
 If you stumble into a bug or have a feature request, please create an issue in
 the `issue tracker <https://github.com/mopidy/mopidy/issues>`_. If you're

docs/installation/osx.rst

@@ -9,7 +9,7 @@ If you are running OS X, you can install everything needed with Homebrew.
 
        xcode-select --install
 
-#. Install `Homebrew <https://github.com/Homebrew/homebrew>`_.
+#. Install `Homebrew <https://brew.sh/>`_.
 
 #. If you are already using Homebrew, make sure your installation is up to
    date before you continue::

docs/installation/raspberrypi.rst

@@ -18,7 +18,7 @@ How to for Raspbian
 ===================
 
 #. Download the latest Raspbian Desktop or Lite disk image from
-   http://www.raspberrypi.org/downloads/raspbian/.
+   https://www.raspberrypi.org/downloads/raspbian/.
 
    Unless you need a full graphical desktop the Lite image is preferable since
    it's much smaller.
@@ -88,5 +88,5 @@ You can test sound output independent of Mopidy by running::
 
 If you hear a voice saying "Front Center", then your sound is working.
 
-If you want to change your audio output setting, simply rerun ``sudo 
+If you want to change your audio output setting, simply rerun ``sudo
 raspi-config``.

docs/installation/source.rst

@@ -71,7 +71,7 @@ please follow the directions :ref:`here <contributing>`.
        sudo pip install -U mopidy
 
    This will use ``pip`` to install the latest release of `Mopidy from PyPI
-   <https://pypi.python.org/pypi/Mopidy>`_. To upgrade Mopidy to future
+   <https://pypi.org/project/Mopidy>`_. To upgrade Mopidy to future
    releases, just rerun this command.
 
 #. Finally, you need to set a couple of :doc:`config values </config>`, and

docs/service.rst

@@ -101,7 +101,7 @@ When using PulseAudio, you will typically have a PulseAudio server run by your
 main user. Since Mopidy is running as its own user, it can't access this server
 directly. Running PulseAudio as a system-wide daemon is discouraged by upstream
 (see `here
-<http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/>`_
+<https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/>`_
 for details). Rather you can configure PulseAudio and Mopidy so Mopidy sends
 the sound to the PulseAudio server already running as your main user.
 

docs/troubleshooting.rst

@@ -18,7 +18,7 @@ Sharing config and log output
 =============================
 
 If you're getting help at IRC, we recommend that you use a pastebin, like
-`pastebin.com <http://pastebin.com/>`_ or `GitHub Gist
+`pastebin.com <https://pastebin.com/>`_ or `GitHub Gist
 <https://gist.github.com/>`_, to share your configuration and log output.
 Pasting more than a couple of lines on IRC is generally frowned upon. On the
 mailing list or when reporting an issue, somewhat longer text dumps are
@@ -79,7 +79,7 @@ Debugging GStreamer
 
 If you really want to dig in and debug GStreamer behaviour, then check out the
 `Debugging section
-<http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-checklist-debug.html>`_
+<https://gstreamer.freedesktop.org/documentation/application-development/appendix/checklist-element.html?gi-language=python>`_
 of GStreamer's documentation for your options. Note that Mopidy does not
 support the GStreamer command line options, like ``--gst-debug-level=3``, but
 setting GStreamer environment variables, like :envvar:`GST_DEBUG`, works with

docs/versioning.rst

@@ -4,7 +4,7 @@
 Versioning
 **********
 
-Mopidy follows `Semantic Versioning <http://semver.org/>`_. In summary this
+Mopidy follows `Semantic Versioning <https://semver.org/>`_. In summary this
 means that our version numbers have three parts, MAJOR.MINOR.PATCH, which
 change according to the following rules:
 

mopidy/audio/actor.py

@@ -396,7 +396,7 @@ class _Handler(object):
 class Audio(pykka.ThreadingActor):
 
     """
-    Audio output through `GStreamer <http://gstreamer.freedesktop.org/>`_.
+    Audio output through `GStreamer <https://gstreamer.freedesktop.org/>`_.
     """
 
     #: The GStreamer state mapped to :class:`mopidy.audio.PlaybackState`

mopidy/mpd/protocol/__init__.py

@@ -5,9 +5,9 @@ This is partly based upon the `MPD protocol documentation
 <http://www.musicpd.org/doc/protocol/>`_, which is a useful resource, but it is
 rather incomplete with regards to data formats, both for requests and
 responses. Thus, we have had to talk a great deal with the the original `MPD
-server <http://mpd.wikia.com/>`_ using telnet to get the details we need to
+server <https://mpd.fandom.com/>`_ using telnet to get the details we need to
 implement our own MPD server which is compatible with the numerous existing
-`MPD clients <http://mpd.wikia.com/wiki/Clients>`_.
+`MPD clients <https://mpd.fandom.com/wiki/Clients>`_.
 """
 
 from __future__ import absolute_import, unicode_literals

mopidy/mpd/protocol/playback.py

@@ -42,7 +42,8 @@ def mixrampdb(context, decibels):
     doesn't fade the track volume, just overlaps. The songs need to have
     MixRamp tags added by an external tool. 0dB is the normalized maximum
     volume so use negative values, I prefer -17dB. In the absence of mixramp
-    tags crossfading will be used. See http://sourceforge.net/projects/mixramp
+    tags crossfading will be used. See
+    https://sourceforge.net/projects/mixramp/
     """
     raise exceptions.MpdNotImplemented  # TODO