Age | Commit message (Collapse) | Author |
|
# Conflicts:
# CHANGELOG.md
# test/pleroma/user_test.exs
|
|
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
|
|
Use EXIF data of image for image description
See merge request pleroma/pleroma!3535
|
|
Server announcements (1st pass)
See merge request pleroma/pleroma!3643
|
|
|
|
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.
|
|
|
|
Also use actor_type to determine if an account is a bot in antiFollowbotPolicy
Closes #2561
See merge request pleroma/pleroma!3498
|
|
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
|
|
|
|
|
|
Even though latest PleromaFE supports displaying these properly, mobile
apps still exist, so I think we should offer a workaround to those who
want it.
|
|
|
|
[Document] Update cheatsheet.md. Add `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`.
See merge request pleroma/pleroma!3604
|
|
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
|
|
Ref: emit-move
|
|
Ref: emit-move
|
|
|
|
MastoAPI: Add user notes on accounts
See merge request pleroma/pleroma!3540
|
|
MastoAPI: accept notify param in follow request
See merge request pleroma/pleroma!3555
|
|
Add initial Nodeinfo document
See merge request pleroma/pleroma!3546
|
|
|
|
V2 suggestions
See merge request pleroma/pleroma!3547
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
Configurable block visibility, fixes #2123
Closes #2123
See merge request pleroma/pleroma!3242
|
|
AdminAPI: endpoint to delete all content from a remote instance
See merge request pleroma/pleroma!3483
|
|
|
|
Remove MastoFE from Pleroma, fixes #2625
Closes #2625
See merge request pleroma/pleroma!3392
|
|
Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3514
|
|
mix pleroma.database set_text_search_config now runs concurrently and infinitely
See merge request pleroma/pleroma!3514
|
|
Add YunoHost to installation guides
See merge request pleroma/pleroma!3497
|
|
|
|
AFAIK OTP releases are the recomended way of installing, but
* People seem unaware of that and use from source installations because they use the guide with the name of their distro
* People don't know what OTP releases are or what it means
I added a warning on all installation-from-source guides and added the same explanation on the two OTP pages (the miigration to OTP and installing OTP)
Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3485
|
|
Make the OPT recomendation clearer
See merge request pleroma/pleroma!3485
|
|
AFAIK OTP releases are the recomended way of installing, but
* People seem unaware of that and use from source installations because they use the guide with the name of their distro
* People don't know what OTP releases are or what it means
I added a warning on all installation-from-source guides and added the same explanation on the two OTP pages (the miigration to OTP and installing OTP)
|
|
|
|
* ./configuration/mrf.md
* Change example
* ./configuration/cheatsheet.md
* Change descriptions to include that a reason is given
* CHANGELOG.md
* Add as breaking change
|
|
|
|
remote instance
|
|
|
|
|