pleroma merge requestshttps://git.pleroma.social/pleroma/pleroma/-/merge_requests2024-01-16T19:06:43Zhttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3806Anonymize reports2024-01-16T19:06:43ZtusooaAnonymize reportsFixes https://git.pleroma.social/pleroma/pleroma/-/issues/2661 https://git.pleroma.social/pleroma/pleroma/-/issues/1024Fixes https://git.pleroma.social/pleroma/pleroma/-/issues/2661 https://git.pleroma.social/pleroma/pleroma/-/issues/10242.6.0https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3805Add mix task to send a notifaction, with a web push2022-12-18T12:59:31ZDuponinAdd mix task to send a notifaction, with a web pushSending only a Push notification can't be done, it needs a Notification.
Creating a notification needs an activity.
Creating an activity needs an object.
That's why it's running throughout the whole process.
It isn't really clean becaus...Sending only a Push notification can't be done, it needs a Notification.
Creating a notification needs an activity.
Creating an activity needs an object.
That's why it's running throughout the whole process.
It isn't really clean because it's forging a post, it might be
acceptable to perform it from an account like "admin" or similar.
That said, you can't use Pleroma's builtin users ('relay' and
'internal.fetch') because they are invisible and stripped out from
notification creation pipeline.
It would have been a better solution, to have real administrative users.
Close #463https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3789Add free setup instructions2023-01-01T17:53:35ZSalvatore TestaAdd free setup instructionsI made a tutorial on how to get Pleroma up and running rather quickly.I made a tutorial on how to get Pleroma up and running rather quickly.https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3785Add API endpoint for exporting followers2024-02-15T15:35:22ZfeldAdd API endpoint for exporting followersThe way we export followers right now is a hack and it's also not the same format as we accept for imports (Mastodon's format)
The goal is to be able to import into Pleroma an export made by PleromaThe way we export followers right now is a hack and it's also not the same format as we accept for imports (Mastodon's format)
The goal is to be able to import into Pleroma an export made by Pleroma2.6.3https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3769Draft: Importing a Collection2022-11-25T20:43:33ZtusooaDraft: Importing a CollectionWill resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2617
- [x] formerRepresentations processing (would that be needed?)
- [x] ~~does ActivityPub.create accept outsider format or internal format?~~ piped through common pip...Will resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2617
- [x] formerRepresentations processing (would that be needed?)
- [x] ~~does ActivityPub.create accept outsider format or internal format?~~ piped through common pipeline
- [x] give user the option to import public/unlisted as unlisted (without cc'ing followers collection)
- [ ] oban enqueuing
- [ ] pleroma api
- [x] ensure no bad html code/injection is possiblehttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3758Add migration cooldown period2022-12-25T05:49:33Zmarcin mikołajczakAdd migration cooldown periodhttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3750Draft: Restrict Announces of objects from banned users2023-10-24T23:43:00ZtusooaDraft: Restrict Announces of objects from banned usersWill fix https://git.pleroma.social/pleroma/pleroma/-/issues/2926
- [x] StreamingWill fix https://git.pleroma.social/pleroma/pleroma/-/issues/2926
- [x] Streaminghttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3744Draft: Support running multi-node2022-12-12T13:52:25ZtusooaDraft: Support running multi-nodewill resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2925
- [x] libcluster
- [ ] cachex?
- [ ] shout: propagate initial state **and every state change**
- need perfect replication, order matters
- db?
- we can generate...will resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2925
- [x] libcluster
- [ ] cachex?
- [ ] shout: propagate initial state **and every state change**
- need perfect replication, order matters
- db?
- we can generate an (flake)id upon every new message and resolve conflicts using id order
- [x] config: propagate changes to all nodes
- [ ] restarter: outside Pleroma application tree, need other ways to communicate
- [x] emoji: propagate changes to all nodes
- [ ] endpoint: should just work?
- [x] oban: will just work https://elixirforum.com/t/example-of-multiple-node-worker-cluster-with-oban/29236/3
- [x] streamer
- [ ] docker: allow only one active migration at a time (how?)
- [ ] ?https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3732Remove frontend bundle2022-12-17T01:35:01ZtusooaRemove frontend bundlehttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3731Draft: Alternative domains support2022-09-19T17:50:04ZtusooaDraft: Alternative domains supporthttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3730Draft: Add accepted_shortcodes to StealEmojiPolicy2022-08-21T17:49:38ZIljaDraft: Add accepted_shortcodes to StealEmojiPolicyWhen at least one pattern is provided, only emoji whose shortcode match one of these patterns will be accepted.
Mostly useful with the regex option to only steal e.g. blobfoxes.
* [ ] Allow wildcards for hostsWhen at least one pattern is provided, only emoji whose shortcode match one of these patterns will be accepted.
Mostly useful with the regex option to only steal e.g. blobfoxes.
* [ ] Allow wildcards for hostshttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3728Draft: Offset pagination2022-08-20T14:31:43ZtusooaDraft: Offset paginationWill resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2786Will resolve https://git.pleroma.social/pleroma/pleroma/-/issues/2786https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3714Draft: Add default Gitlab templates for Issues and MR's2022-09-18T06:33:51ZIljaDraft: Add default Gitlab templates for Issues and MR'sSee <https://docs.gitlab.com/ee/user/project/description_templates.html#set-a-default-template-for-merge-requests-and-issues>
When people create a new issue or MR, they will now get a default template. This can be used to give prope...See <https://docs.gitlab.com/ee/user/project/description_templates.html#set-a-default-template-for-merge-requests-and-issues>
When people create a new issue or MR, they will now get a default template. This can be used to give proper information to people about what we need/expect for issues/mr's.
You can test on Pleroma in my namespace (I set this branch as default branch) <https://git.pleroma.social/ilja/pleroma>
This is based partly on what we already had, partly on what we had for newroma, and partly new stuff I added. Pls let me know if there are things you think need changing so I can adapt it.
* [x] Add some first draft
* [ ] Also peek at what was done for FE (seems pretty good) and update here <https://git.pleroma.social/pleroma/pleroma-fe/-/merge_requests/1577>
* [ ] From @helene in chat: "you mix PR and MR a lot, and maybe specifying what those acronyms are at least one would be nice (writing "merge request" once instead of just MR, for example) :)"
* [ ] Also say something about changelog/docs
* [ ] Maybe check <https://git.pleroma.social/pleroma/pleroma-meta/-/merge_requests/1> if there are other things that's checked during e.g. code review that can be added herehttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3711Draft: Reject requests from specified instances if `authorized_fetch_mode` is...2023-10-02T13:07:48Zmarcin mikołajczakDraft: Reject requests from specified instances if `authorized_fetch_mode` is enabledhttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3700Draft: Fix flaky test: default S3 uploader values make code fail2022-07-28T03:36:12ZIljaDraft: Fix flaky test: default S3 uploader values make code failSee comment https://git.pleroma.social/pleroma/pleroma/-/issues/2860#note_91829
Some tests seem to fail when doing `--stale`. The reason is that the code that is tested indirectly make use of the uploader. When they failed, it's because...See comment https://git.pleroma.social/pleroma/pleroma/-/issues/2860#note_91829
Some tests seem to fail when doing `--stale`. The reason is that the code that is tested indirectly make use of the uploader. When they failed, it's because the uploader was set to `S3` whose default settings don't work properly. For the tests/modules that failed, I started with setting the global settings to the `Local` uploader who does work. I have no idea why I only see these failures when running with `--stale`.IljaIljahttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3683Mastodon-compatible webhooks2023-12-22T12:58:36Zmarcin mikołajczakMastodon-compatible webhooksIntended to work like the [new Mastodon feature](https://github.com/mastodon/mastodon/pull/18510).
> Webhooks would benefit automation through the moderation API by notifying applications about system events in real-time. They would als...Intended to work like the [new Mastodon feature](https://github.com/mastodon/mastodon/pull/18510).
> Webhooks would benefit automation through the moderation API by notifying applications about system events in real-time. They would also enable integrations with chat apps like Discord, IRC and Slack, helping moderator coordination.
>
> Events currently supported:
>
> * `report.created`
> * `account.created`
>
> The `X-Hub-Signature` header adopted from the WebSub spec can be optionally used to verify that the payloads are authentic.
>
> The payload delivered to the webhook has the form of:
> ```
> {
> "event": "report.created",
> "created_at": "2022-06-08T12:28:31.000Z",
> "object": {
> // The report entity would be here
> }
> }
> ```
> Mind that `created_at` at the top-level refers to the event itself, and not the `object`.https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3681More search options2022-10-11T21:17:20ZtusooaMore search optionsThis MR allows the server admin to specify the combinations of the following search policies:
- allow searching public/unlisted (kept as default, same as current Pleroma)
- allow searching everything the user interacted with (same as Ma...This MR allows the server admin to specify the combinations of the following search policies:
- allow searching public/unlisted (kept as default, same as current Pleroma)
- allow searching everything the user interacted with (same as Mastodon)
- allow searching everything visible to the user (implies the former two)https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3677Draft: Misskeyish Drive2023-08-19T13:35:05ZtusooaDraft: Misskeyish DriveWill resolve #2738
- [ ] internal:
- [x] Ability to list uploaded files by one user (Image and Document)
- [x] Ability to delete uploaded files (dedupe-aware)
- [x] Track attachment relationship between Objects
- [ ] Atomicity...Will resolve #2738
- [ ] internal:
- [x] Ability to list uploaded files by one user (Image and Document)
- [x] Ability to delete uploaded files (dedupe-aware)
- [x] Track attachment relationship between Objects
- [ ] Atomicity when performing actions on files (`:global`)
- [ ] API
- [x] list media
- [x] provide information on where media is used
- [x] delete media
- [later] User quota for uploading, dynamically assigned using a couple of factors like post numbers, registration date, user tags?
- [later] Maybe: access control
- [ ] Migration code to scan all uploaded attachments and assign the corresponding upload path (would this be possible?)
- [x] Add ap ids to all upload objects
- [x] Create an UploadedFile for each one
- [ ] Legacy ap-id-less upload objects: how to link them?https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3671MastoAPI: /api/v1/admin/accounts, /api/v1/admin/reports2023-12-27T23:17:51Zmarcin mikołajczakMastoAPI: /api/v1/admin/accounts, /api/v1/admin/reportshttps://git.pleroma.social/pleroma/pleroma/-/merge_requests/3670Allow assigning users to reports2024-02-01T10:55:59Zmarcin mikołajczakAllow assigning users to reports