parameters

Much thanks to Breno Vitório (@brenu) for the report!

Also remove some unused html responses

fixes #7195

closes #7455

This token is only used for the chat, it isn't an official API.

fixes #4319

closes #7118

closes #7049

Fixed:
* wrong url
* broken navigation
* broken design
after saving the user settings

Fixes #5847

in order to support adding new aspect to a dropdown without full
page reload

* Fix issue #6847

There is no point to redirect to "/stream" after the account deletion
because the user is logged off.

closes #5967

- move to contacts.js
- use json
- move to aspects_controller
- add route
- rewrite test
- fix css in chrome

This reverts commit 8d8d3c64.

Conflicts:
	app/assets/javascripts/main.js

Also redirect to it for download, for Amazon S3
compatibility.

Prior to this patch an attacker could obtain an
users export by guessing the filename with a high
chance of success. Fully authenticating the
download request is a lot harder due to our diverse
deployment scenarios.

This brings the used method in line with the photo
export feature.

Thanks to @tomekr for the report.

Podmin can see a extra checkbox in Settings > Account
for disabling report-email-notification

This new class replaces all existing server side message
rendering helpers and is the new global entry point for such
needs. All models with relevant fields now expose an instance
of MessageRenderer for those. MessageRenderer acts as
gateway between the existing processing solutions for markdown,
mentions and tags and provides a very flexible interface for
all output needs. This makes the API to obtain a message
in a certain format clear. As a result of centralizing the
processing a lot of duplication is eliminated. Centralizing
the message processing also makes it clear where to change
its behaviour, add new representations and what options
are already available.

Fetch user params instead of require.