- 17 Nov, 2020 23 commits
-
-
rinpatch authored
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 #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.
-
lain authored
-
rinpatch authored
It's libmagic-dev in both Ubuntu and Debian. Reported in private by NaiJi.
-
rinpatch authored
This prevents `git grep` from showing the matching line and diffs from being shown by default.
-
rinpatch authored
It has been the de-facto style for a while now, however it is not enforced, so there were some entries that didn't use it.
-
rinpatch authored
-
rinpatch authored
-
rinpatch authored
Updates the frontend bundle and syncs the changelog.
-
lain authored
-
Haelwenn authored
-
lain authored
-
Guy Sheffer authored
- 16 Nov, 2020 3 commits
- 14 Nov, 2020 2 commits
-
-
Haelwenn authored
- 13 Nov, 2020 8 commits
-
-
lain authored
-
lain authored
-
* These are the first small steps for issue 2034 "Reports should send a notification to admins". * I added a new type of notification "pleroma:report" to the the database manually (a migration will need to be written later) * I added the new type to the notification_controller * I made the view return the notification. It doesn't include the report itself (yet)
-
lain authored
-
Alexander Strizhakov authored
-
- 12 Nov, 2020 4 commits
-
-
rinpatch authored
Release/2.2.0 See merge request pleroma/secteam/pleroma!19
-
rinpatch authored
Validate the content-type of the response when fetching an object, according to https://www.w3.org/TR/activitypub/#x3-2-retrieving-objects. content-type headers had to be added to many mocks in order to support this, some of this was done with a regex. While I did go over the resulting files to check I didn't modify anything unrelated, there is a possibility I missed something. Closes #1948