- 01 Jul, 2022 3 commits
-
-
Ilja authored
No migrations or checks yet
-
Ilja authored
-
Ilja authored
During attachment upload Pleroma returns a "description" field. Pleroma-fe has an MR to use that to pre-fill the image description field, <pleroma-fe!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.
-
- 26 Feb, 2022 1 commit
-
-
Sean King authored
-
- 16 Dec, 2021 1 commit
-
-
Alex Gleason authored
Co-authored-by:
Egor Kislitsyn <egor@kislitsyn.com>
-
- 28 Jan, 2021 2 commits
- 13 Jan, 2021 1 commit
-
-
Haelwenn authored
grep -rl '# Copyright © .* Pleroma' * | xargs sed -i 's;Copyright © .* Pleroma .*;Copyright © 2017-2021 Pleroma Authors <https://pleroma.social/>;'
-
- 22 Dec, 2020 1 commit
-
- 12 Dec, 2020 2 commits
-
-
rinpatch authored
- 14 Nov, 2020 1 commit
-
-
Haelwenn authored
-
- 08 Nov, 2020 1 commit
-
-
rinpatch authored
While taking a final look at instance.gen before releasing I noticed that the release_env task outputs messages in broken english. Upon further inspection it seems to have even more severe issues which, in my opinion, warrant it's at least temporary removal: - We do not explain what it actually does, anywhere. Neither the task docs nor instance.gen, nor installation instructions. - It does not respect FHS on OTP releases (uses /opt/pleroma/config even though we store the config in /etc/pleroma/config.exs). - It doesn't work on OTP releases, which is the main reason it exists. Neither systemd nor openrc service files for OTP include it. - It is not mentioned in install guides other than the ones for Debian and OTP releases.
-
- 15 Oct, 2020 2 commits
- 12 Oct, 2020 1 commit
-
-
feld authored
-
- 09 Jul, 2020 1 commit
-
-
feld authored
-
- 20 May, 2020 1 commit
-
-
Maksim authored
-
- 02 Mar, 2020 1 commit
-
- 25 Feb, 2020 3 commits
-
-
rinpatch authored
See !2245 (comment 52217)
-
rinpatch authored
migrations
-
rinpatch authored
-
- 24 Feb, 2020 1 commit
-
- 04 Oct, 2019 1 commit
-
-
rinpatch authored
It's still too unstable to be used.
-
- 03 Oct, 2019 2 commits
- 18 Sep, 2019 1 commit
-
- 09 Jul, 2019 1 commit
-
-
Sachin Joshi authored
-
- 05 Jul, 2019 1 commit
-
-
Haelwenn authored
Closes: pleroma/pleroma#1058
-
- 22 Jun, 2019 1 commit
-
-
rinpatch authored
-
- 21 Jun, 2019 3 commits
- 20 Jun, 2019 1 commit
-
-
rinpatch authored
-
- 19 Jun, 2019 2 commits
-
-
rinpatch authored
-
rinpatch authored
instead of aliasing This seems to be the convention for functions that can be reused between different mix tasks in all Elixir projects I've seen and it gets rid on an error message when someone runs mix pleroma.common Also in this commit by accident: - Move benchmark task under a proper namespace - Insert a space after the prompt
-
- 14 Jun, 2019 1 commit
-
-
Alexander Strizhakov authored
we can't change module attributes and endpoint settings in runtime
-
- 08 Jun, 2019 1 commit
-
-
rinpatch authored
-
- 20 Apr, 2019 1 commit
-
-
Roman Chvanikov authored
-
- 10 Apr, 2019 1 commit
-
-
Alexander Strizhakov authored
-