In Create validator we do not validate the object data,
but that is because the object itself will go through the
pipeline again, which is not the case for Update. Thus,
we added validation for objects in Update activities.

# Conflicts:
#   lib/pleroma/constants.ex

mix: update eblurhash to 1.2.2

See merge request pleroma/pleroma!3686

Add index hotspots

See merge request pleroma/pleroma!3664

Use EXIF data of image for image description

See merge request pleroma/pleroma!3535

Bugfix: Validate mediaType only by it's format

See merge request pleroma/pleroma!3597

Server announcements (1st pass)

See merge request pleroma/pleroma!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.

Rename to Exiftool.StripLocation

No migrations or checks yet

During attachment upload Pleroma returns a "description" field. Pleroma-fe has an MR to use that to pre-fill the image description field, <https://git.pleroma.social/pleroma/pleroma-fe/-/merge_requests/1399>

* This MR allows Pleroma to read the EXIF data during upload and return the description to the FE
    * If a description is already present (e.g. because a previous module added it), it will use that
    * Otherwise it will read from the EXIF data. First it will check -ImageDescription, if that's empty, it will check -iptc:Caption-Abstract
    * If no description is found, it will simply return nil, just like before
* When people set up a new instance, they will be asked if they want to read metadata and this module will be activated if so

This was taken from an MR i did on Pleroma and isn't finished yet.

get_create_by_ap_id_with_object() seems to fetch the old object.
Why this happens needs further investigation.

hackney adapter helper: enable TLSv1.3

See merge request pleroma/pleroma!3661