| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-07-02 | Rename pipelines and add forgotten tags | Ilja | |
| I renamed some tags before, but forgot to rename the pipelines I also had some tags which I forgot to add to the config, description, etc. These have now been done/added | |||
| 2022-07-02 | Add better explanation in the Cheatsheet about what each tag does | Ilja | |
| 2022-07-02 | Change order of privilege tags to make more sense | Ilja | |
| The tags were listed in different places They were listed in a rather randomly order I reordered them in a way I think makes more sense | |||
| 2022-07-01 | Rename the Exiftool module | Ilja | |
| No migrations or checks yet | |||
| 2022-07-01 | Rename the new module | Ilja | |
| 2022-07-01 | Use EXIF data of image to prefill image description | Ilja | |
| 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. | |||
| 2022-07-01 | Add docs and CHANGELOG entries | Ilja | |
| 2022-05-08 | Also use actor_type to determine if an account is a bot in antiFollowbotPolicy | Ilja | |
| 2022-03-29 | Add short_description field | marcin mikołajczak | |
| Signed-off-by: marcin mikołajczak <git@mkljczk.pl> | |||
| 2022-01-19 | Add ForceMentionsInContentPolicy | rinpatch | |
| 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. | |||
| 2022-01-15 | Update cheatsheet.md. Add `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`. | Hakaba Hitoyo | |
| 2021-11-15 | Merge branch 'block-behavior' into 'develop' | lain | |
| Configurable block visibility, fixes #2123 Closes #2123 See merge request pleroma/pleroma!3242 | |||
| 2021-09-07 | Merge branch 'remove/mastofe' into 'develop' | Haelwenn | |
| Remove MastoFE from Pleroma, fixes #2625 Closes #2625 See merge request pleroma/pleroma!3392 | |||
| 2021-08-06 | Change docs | Ilja | |
| * ./configuration/mrf.md * Change example * ./configuration/cheatsheet.md * Change descriptions to include that a reason is given * CHANGELOG.md * Add as breaking change | |||
| 2021-06-04 | Fix merge conflicts with upstream | Sean King | |
| 2021-06-03 | Merge branch 'chore/rename-chat' into 'develop' | Haelwenn | |
| Rename the non-federating Chat feature to Shout See merge request pleroma/pleroma!2842 | |||
| 2021-06-02 | Update wording for relays in docs and config description | Mark Felder | |
| 2021-06-01 | Move shout configuration from :instance, update docs and changelog | Mark Felder | |
| 2021-04-29 | Merge remote-tracking branch 'upstream/develop' into block-behavior | Alex Gleason | |
| 2021-04-15 | Remove MastoFE configuration stuff | Sean King | |
| 2021-03-30 | Add more details to the cheatsheat for FollowBot MRF | Mark Felder | |
| 2021-03-30 | Apply 1 suggestion(s) to 1 file(s) | feld | |
| 2021-03-30 | Document :mrf_follow_bot | Mark Felder | |
| 2021-03-19 | Merge branch 'fix/remove_auto_nsfw' into 'develop' | rinpatch | |
| Remove sensitive setting #nsfw See merge request pleroma/pleroma!3223 | |||
| 2021-03-02 | Merge remote-tracking branch 'remotes/origin/develop' into ↵ | Ivan Tashkinov | |
| feature/object-hashtags-rework | |||
| 2021-02-27 | Remove sensitive-property setting #nsfw, create HashtagPolicy | Haelwenn (lanodan) Monnier | |
| 2021-02-23 | [#3213] Misc. tweaks: proper upsert in Hashtag, better feature toggle ↵ | Ivan Tashkinov | |
| management. | |||
| 2021-02-22 | Update the documentation to use make it use /api/v1/pleroma instead of ↵ | eugenijm | |
| /api/pleroma | |||
| 2021-02-18 | [#3213] HashtagsTableMigrator: fault rate allowance to enable the feature ↵ | Ivan Tashkinov | |
| (defaults to 1%), counting of affected objects, misc. tweaks. | |||
| 2021-02-13 | [#3213] `rescue` around potentially-raising `Repo.insert_all/_` calls. Misc. ↵ | Ivan Tashkinov | |
| improvements (docs etc.). | |||
| 2021-01-29 | [#3286] Documentation on configuring Pleroma as OAuth 2.0 provider. | Ivan Tashkinov | |
| 2021-01-21 | Add ability to invalidate cache entries for Apache | Mark Felder | |
| 2021-01-21 | use proper naming | Alexander Strizhakov | |
| for MediaProxyWarmingPolicy in ConcurrentLimiter | |||
| 2021-01-21 | Update docs | Mark Felder | |
| 2021-01-21 | configurable limits for ConcurrentLimiter | Alexander Strizhakov | |
| Pleroma.Web.RichMedia.Helpers & Pleroma.Web.MediaProxy | |||
| 2021-01-12 | Deprecate Pleroma.Uploaders.S3, :public_endpoint | Mark Felder | |
| 2021-01-06 | Merge remote-tracking branch 'upstream/develop' into block-behavior | Alex Gleason | |
| 2020-11-19 | Cheatsheet: Add docs about reset token expiration | lain | |
| 2020-11-17 | Remove FedSockets | rinpatch | |
| Current FedSocket implementation has a bunch of problems. It doesn't have proper error handling (in case of an error the server just doesn't respond until the connection is closed, while the client doesn't match any error messages and just assumes there has been an error after 15s) and the code is full of bad descisions (see: fetch registry which uses uuids for no reason and waits for a response by recursively querying a ets table until the value changes, or double JSON encoding). Sometime ago I almost completed rewriting fedsockets from scrach to adress these issues. However, while doing so, I realized that fedsockets are just too overkill for what they were trying to accomplish, which is reduce the overhead of federation by not signing every message. This could be done without reimplementing failure states and endpoint logic we already have with HTTP by, for example, using TLS cert auth, or switching to a more performant signature algorithm. I opened https://git.pleroma.social/pleroma/pleroma/-/issues/2262 for further discussion on alternatives to fedsockets. From discussions I had with other Pleroma developers it seems like they would approve the descision to remove them as well, therefore I am submitting this patch. | |||
| 2020-11-04 | Cheatsheet: Add info about :blockers_visible | lain | |
| 2020-10-28 | Merge remote-tracking branch 'origin/develop' into feature/account-export | Egor Kislitsyn | |
| 2020-10-20 | Rename `Pleroma.Backup` to `Pleroma.User.Backup` | Egor Kislitsyn | |
| 2020-10-16 | Adds feature to permit e.g., local admins and community moderators to ↵ | Mark Felder | |
| automatically follow all newly registered accounts | |||
| 2020-10-14 | Merge branch 'develop' into feature/account-export | Mark Felder | |
| 2020-10-13 | changes after rebase | Alexander Strizhakov | |
| 2020-10-13 | RemoteIp module name | Alexander Strizhakov | |
| 2020-10-07 | Add configurable temporary directory | Egor Kislitsyn | |
| 2020-10-07 | Require email | Egor Kislitsyn | |
| 2020-10-07 | Add config for Pleroma.Backup | Egor Kislitsyn | |
| 2020-10-06 | Improve description yet again | Mark Felder | |
 |
index : pleroma | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |