summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-08-20Add remote interaction ui for postsTusooa Zhu
2022-08-20Update thread visibility functionTusooa Zhu
2022-08-20LintTusooa Zhu
2022-08-20Switch to associated_object_id indexTusooa Zhu
2022-08-20Add function to calculate associated object idTusooa Zhu
2022-08-19Add glitch-lily as an installable frontendSean King
2022-08-19Release 2.4.4Tusooa Zhu
2022-08-19Refactor streamer testTusooa Zhu
2022-08-19Execute session disconnect in backgroundTusooa Zhu
2022-08-19LintTusooa Zhu
2022-08-19Test that server will disconnect websocket upon token revocationTusooa Zhu
2022-08-19Use Websockex to replace websocket_clientTusooa Zhu
2022-08-19Disconnect streaming sessions when token is revokedTusooa Zhu
2022-08-19Merge branch 'varnish-fix-changelog' into 'develop'feld
Document the changes for Varnish 7.0+ compatibility and RFC compliance See merge request pleroma/pleroma!3723
2022-08-20emoji-test: update to latest 15.0 draftHélène
2022-08-19ArticleNotePageValidator: fix replies fixingHélène
Some software, like GoToSocial, expose replies as ActivityPub Collections, but do not expose any item array directly in the object, causing validation to fail via the ObjectID validator. Now, Pleroma will drop that field in this situation too.
2022-08-18HttpSignaturePlug: accept standard (request-target)Hélène
The (request-target) used by Pleroma is non-standard, but many HTTP signature implementations do it this way due to a misinterpretation of the draft 06 of HTTP signatures: "path" was interpreted as not having the query, though later examples show that it must be the absolute path with the query part of the URL as well. This behavior is kept to make sure most software (Pleroma itself, Mastodon, and probably others) do not break, but Pleroma now accepts signatures for a (request-target) containing the query, as expected by many HTTP signature libraries, and clarified in the draft 11 of HTTP signatures. Additionally, the new draft renamed (request-target) to @request-target. We now support both for incoming requests' signatures.
2022-08-16fix resolution of GTS user keysFloatingGhost
2022-08-15Migrations: delete contexts with BaseMigratorHélène
Due to the lengthiness of this task, the migration has been adapted into a BaseMigrator migration, running in the background instead.
2022-08-15CommonFixes: more predictable context generationHélène
`context` fields for objects and activities can now be generated based on the object/activity `inReplyTo` field or its ActivityPub ID, as a fallback method in cases where `context` fields are missing for incoming activities and objects.
2022-08-12Document the changes for Varnish 7.0+ compatibility and RFC complianceMark Felder
2022-08-12Merge branch 'from/upstream-develop/tusooa/2912-receiver-reject-mrf' into ↵Haelwenn
'develop' Treat MRF rejects as success in Oban worker Closes #2912 See merge request pleroma/pleroma!3720
2022-08-12Merge branch 'fix_flaky_tests_where_we_sometimes_loose_db_connections' into ↵Haelwenn
'develop' Fix flaky tests with DB connections; Allow higher amount of restarts for Pleroma.Repo during testing See merge request pleroma/pleroma!3696
2022-08-12Merge branch 'from/upstream-develop/tusooa/sync-settings' into 'develop'Haelwenn
Synchronized settings for apps (frontends) See merge request pleroma/pleroma!3698
2022-08-12Merge branch 'from/upstream-develop/floatingghost/follow-state' into 'develop'Haelwenn
Backport: bugfix/follow-state Closes #2902 See merge request pleroma/pleroma!3718
2022-08-11Merge branch 'fix-varnish7-support' into 'develop'feld
Fix Varnish7 support See merge request pleroma/pleroma!3722
2022-08-10Fix the mocks to use uppercase as wellMark Felder
2022-08-10Update the recommended VCL configurationMark Felder
2022-08-10Fix Varnish 7 support by ensuring Media Preview Proxy fetches headers with a ↵Mark Felder
capitalized HEAD verb
2022-08-10CreateGenericValidator: fix reply context fixingHélène
Incoming Pleroma replies to a Misskey thread were rejected due to a broken context fix, which caused them to not be visible until a non-Pleroma user interacted with the replies. This fix properly sets the post-fix object context to its parent Create activity as well, if it was changed.
2022-08-10Migrations: delete context objectsHélène
These objects represent from 30 to 70% of the rows on the objects table, based on numbers from a few live instances (single-user, small, large.) As those pseudo-objects prevent creating objects with those actual IDs, deleting them is a better solution. This could have happened if an object used another object's ID as its context.
2022-08-10StatusView: implement pleroma.context fieldHélène
This field replaces the now deprecated conversation_id field, and now exposes the ActivityPub object `context` directly via the MastoAPI instead of relying on StatusNet-era data concepts.
2022-08-09Add changelogTusooa Zhu
2022-08-09Update api spec to reflect OAuth scope changeTusooa Zhu
2022-08-09StatusView: clear MSB on calculated conversation_idHélène
This field seems to be a left-over from the StatusNet era. If your application uses `pleroma.conversation_id`: this field is deprecated. It is currently stubbed instead by doing a CRC32 of the context, and clearing the MSB to avoid overflow exceptions with signed integers on the different clients using this field (Java/Kotlin code, mostly; see Husky and probably other mobile clients.) This should be removed in a future version of Pleroma. Pleroma-FE currently depends on this field, as well.
2022-08-09CommonFields: remove context_idHélène
2022-08-09Object: remove context_id fieldHélène
30 to 70% of the objects in the object table are simple JSON objects containing a single field, 'id', being the context's ID. The reason for the creation of an object per context seems to be an old relic from the StatusNet era, and has only been used nowadays as an helper for threads in Pleroma-FE via the `pleroma.conversation_id` field in status views. An object per context was created, and its numerical ID (table column) was used and stored as 'context_id' in the object and activity along with the full 'context' URI/string. This commit removes this field and stops creation of objects for each context, which will also allow incoming activities to use activity IDs as contexts, something which was not possible before, or would have been very broken under most circumstances. The `pleroma.conversation_id` field has been reimplemented in a way to maintain backwards-compatibility by calculating a CRC32 of the full context URI/string in the object, instead of relying on the row ID for the created context object.
2022-08-09Make backups require its own scopeTusooa Zhu
2022-08-08Treat containment failure as cancel in ReceiverWorkerTusooa Zhu
2022-08-07Change default moderator privileges to better match what we previously hadIlja
Moderators were able to delete statusses via pleroma-fe. For that reason I now gave them :messages_delete by default. They are also able to recieve reports through the notifications. For that reason I now gave them :reports_manage_reports by default. They were also able to see deactivated accounts through pleroma-fe. However * they were unable to tell if the account is deactivated or not (which was a bug and fixed by thes privileges MR this commit is part of) * they were not able to actually change the activation state. Because of this, I decided to *not* give them the privilege :users_manage_activation_state as this would give significantly more privileges, while not giving it will actually improve the current experience as it works around the existing bug of not showing activation state.
2022-08-06Fix FederatorTestTusooa Zhu
2022-08-06Treat MRF rejects as success in Oban workerTusooa Zhu
2022-08-05Use latest alpine version for docker imageTusooa Zhu
2022-08-03bugfix/follow-state (#104)floatingghost
Reviewed-on: https://akkoma.dev/AkkomaGang/akkoma/pulls/104
2022-08-02Use actor_types() to determine whether the Update is for userTusooa Zhu
2022-08-02Merge branch 'from/upstream-develop/tusooa/2871-fix-local-public' into 'develop'Haelwenn
local only fixes Closes #2871 See merge request pleroma/pleroma!3660
2022-08-02Merge branch 'from/upstream-develop/tusooa/backup-without-email' into 'develop'Haelwenn
Allow users to create backups without providing email address See merge request pleroma/pleroma!3665
2022-08-02Merge branch 'weblate' into 'develop'Haelwenn
Translations update from Pleroma Weblate See merge request pleroma/pleroma!3716
2022-07-31Translated using Weblate (Chinese (Simplified))Yating Zhan
Currently translated at 18.9% (189 of 998 strings) Translation: Pleroma/Pleroma Backend (domain config_descriptions) Translate-URL: http://weblate.pleroma-dev.ebin.club/projects/pleroma/pleroma-backend-domain-config_descriptions/zh_Hans/
2022-07-31Translated using Weblate (Chinese (Simplified))tusooa
Currently translated at 18.9% (189 of 998 strings) Translation: Pleroma/Pleroma Backend (domain config_descriptions) Translate-URL: http://weblate.pleroma-dev.ebin.club/projects/pleroma/pleroma-backend-domain-config_descriptions/zh_Hans/