Marking a notification as unread resets the timeago stamp causing
the times to look wrong. It can be reproduced by marking an old
notification as unread. Using the update_column instead of
update_attribute will not touch the updated_at attribute, and
thus will not affect the updated time ago in the view.

Fixes #6798.

closes #6821

closes #6817

The REGEX is unused

closes #6810

encrypting the channel setting

Courtesy of https://github.com/mozilla/build-tools/commit/c13a297

[ci skip]

Following query takes over 20 minutes and fills up the database:
SELECT * FROM participations WHERE author_id = XXXXX

On servers with a huge participations-table this is a serious
performance issue which is easily fixed by the author_id index

Signed-off-by: Lukas Matt <lukas@zauberstuhl.de>

closes #6738

Use 1004 as our placeholder birth year because 1004 was a leap year. (Well, actually, people in 1004 probably had no idea what a leap year is. Or red tests. Or code.)

and bump typhoeus

Google Chrome Frame was a plugin for Internet Explorer, but is no longer
supported. And it was included with http and not https which triggered a
warning on most pods.

Also set the minimum version to 9 to support #6557

closes #6751

closes #6748

_url doesn't with generate https if the pod uses https

since that could allow fetching spoofed/altered posts
thanks @supertux88

closes #6734

closes #6720

Only mark unread notifications as read otherwise, the UPDATE statement would update all the notifications...

closes #6711

closes #6710