feld

ok after deeper inspection this seems to only affect the container *name* but the underlying container will still be e.g., `cincproject/cinc` so it should be harmless. It could be confusing...

chatmaild -- this would also be useful for lowering the barrier to porting the relay to non-Debian-Linux OSes (not deployed with cmdeploy)

Simplest workaround is to write a Middleware that takes the URL and runs it through `URI.decode` and then `URI.encode` again to be certain it's encoded correctly.] edit: actually you need...

I think at a minimum it just needs to be very clearly documented that proper URL-encoding is not handled at all by Tesla. > That is the tricky bit, that...

With a 2.22.0 core on iOS and a 2.25 core on Desktop it seems that I cannot share a contact with a vcard from one profile of mine to another...

Yeah, it's just a basic test file we use  edit: if github mangled this, here's a link from our repo https://git.pleroma.social/pleroma/pleroma/-/blob/feat/vips-heif-upload-filter/test/fixtures/image.heic?ref_type=heads

``` iex(1)> {:ok, img} = Vix.Vips.Image.new_from_file("test/fixtures/image.heic") {:ok, %Vix.Vips.Image{ref: #Reference}} iex(2)> Vix.Vips.Image.header_value(img, "heif-compression") {:ok, "hevc"} ``` you're right about it being HEVC... now the question is, what does Apple normally use?...

The files I'm finding from iMessages from friends which are HEIC format also report as HEVC... I see in the FreeBSD project we're shipping libheif with HEVC enabled. In 2020...

I was just thinking about this again and I think a reasonable solution may be to make it possible to self-host the Pre-compiled NIF, perhaps by setting an ENV that...

come on, just merge the fix. It works.