@mint It is fixed, but not merged into the 2.7.1 release even though the MR has a 2.7.1 milestone and it won't apply retroactively, because the remote server drops the activity for being invalid. The other follow bug was merged though.
@prettygood@druid@snacks I've been running a source install since the beginning, because I expected I would need to patch things in the future. If you don't mind the gigabytes of build tools required for it to build, it's fine.
Converting an OTP install to a source one is a different can of worms. It might be better to create your own OTP releases from a patched branch.
@eric@druid@prettygood@snacks From a Pleroma issue it seem that the OTP build uses Erlang 23 which didn't fully support OpenSSL 3, building with newer Erlang versions should work fine with OpenSSL 3. You can even use LibreSSL with a recent enough version of Erlang 26.
@eric@druid@snacks@prettygood In this case OTP means you have the code and you run mix release --overwrite --path pleroma and out should come a folder with all the binaries you need to run pleroma without Erlang and Elixir installed on the target system.
Or at least I think it works like that. I never tried to run it like that outside of writing a package that mimics the Gentoo install script.
@eric@phnt@druid@snacks that's what the Gentoo ebuild does yeah. That's how I've always had it installed. I know if I set the right unmask I can use the git tree version but that frankly sounds trepidatious