See <https://docs.gitlab.com/ee/user/project/description_templates.html#set-a-default-template-for-merge-requests-and-issues>

When people create a new issue or MR, they will now get a default template. This can be used to give proper information to people about what we need/expect for issues/mr's.

Shrink CI

See merge request !3691

Translatable config descriptions

Closes pleroma-meta#65

See merge request !3695

MastoAPI: Use `types` for filtering notifications

See merge request !3648

DOCS: Add some small piece about setting up a Gitlab-runner

See merge request !3694

Translate static_pages.po (Simplified Chinese)

See merge request !3655

This is based on me setting one up, but I kept it general with mostly linking to other documentation.
The idea is that to just provide some Pleroma-specific info, maybe give some pointers, and point to the right (external) docs.

Add short_description instance field

Closes #2865

See merge request pleroma/pleroma!3651

Make checking blacklisted domains and restricted nicknames case-insensitive

Closes #2894 and #2888

See merge request !3687

Pass remote follow avatar into media proxy

Closes #2830

See merge request !3690

Make validation functions for restricted nicknames and blacklisted domains; do restricted nickname validation in LDAP account registration

Fix long report notes giving errors on creation

See merge request !3679

mix: update eblurhash to 1.2.2

See merge request !3686

Add index hotspots

See merge request !3664

Use EXIF data of image for image description

See merge request !3535

Bugfix: Validate mediaType only by it's format

See merge request !3597

Server announcements (1st pass)

See merge request !3643

Previous eblurhash versions bundled precompiled binaries which caused
issues on non-Darwin operating systems.

I noticed that pictures taken with Ubuntu-Touch have whitespace in one of the fields
This should just be ignored imo

The previous pictures were labeled as public domain, but are actually a collage of pictures under other licenses.

I now replaced them with a jpeg of simply a white pixel.

I used keyword_list[:key], but if the key doesn't exist, it will return nil. I actually expect a list and further down the code I use that list.
I believe the key should always be present, but in case it's not, it's better to return an empty list instead of nil. That way the code wont fail further down the line.