Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-06-21 | Add privilige :emoji_management | Ilja | |
2022-06-21 | Add privilige :status_delete | Ilja | |
It also allows to update a message, so it's not just deleting. I need a better name... | |||
2022-06-21 | last off :statuses_read | Ilja | |
From the endpoints left to do, I believe these should be under :statuses_read. These should be the last for that privilege for this MR | |||
2022-06-21 | Mark relevant tests synchronous | Ilja | |
One of the things we do during the tests is change the config. But that's global state and different tests were interfering. E.g. one test would set `clear_config([:instance, :admin_privileges], [:statuses_read])`, but while that runs, another test may do `clear_config([:instance, :admin_privileges], [:user_invite])`. Now the code for the first test checks the setting, and it finds `:user_invite` instead of `:statuses_read`. Now the modules where this happens are marked to run synchronously, so they don't interfere with each other. | |||
2022-06-21 | Add privileges for :user_read | Ilja | |
2022-06-21 | Add privileges for :report_handle | Ilja | |
2022-06-21 | Add privileges for :user_invite | Ilja | |
2022-06-21 | Add privileges for :user_activation | Ilja | |
2022-06-21 | Add privileges for :user_tag | Ilja | |
2022-06-21 | Remove privileged_staff | Ilja | |
Everything that was done through this setting, can now be set by giving the proper privileges to the roles. | |||
2022-06-21 | Add priviledges for :statuses_read | Ilja | |
This was the last in :require_privileged_staff. I'll remove that in the next commit | |||
2022-06-21 | Add priviledges for :user_credentials | Ilja | |
I only moved the ones from the :require_privileged_staff block for now | |||
2022-06-21 | Add privilege :user_deletion | Ilja | |
2022-06-21 | Add new setting and Plug to allow for privilege settings for staff | Ilja | |
2022-06-16 | Store mutes expiration date | marcin mikołajczak | |
Signed-off-by: marcin mikołajczak <git@mkljczk.pl> | |||
2022-06-11 | Show original status at the first of history | Tusooa Zhu | |
2022-06-11 | Workaround with_index does not support function in Elixir 1.9 | Tusooa Zhu | |
2022-06-11 | Send the correct update in streamer | Tusooa Zhu | |
get_create_by_ap_id_with_object() seems to fetch the old object. Why this happens needs further investigation. | |||
2022-06-11 | Expose history and source apis to anon users | Tusooa Zhu | |
2022-06-09 | Fix incorrectly cached content after editing | Tusooa Zhu | |
2022-06-08 | Return the corresponding object id in attachment view | Tusooa Zhu | |
2022-06-08 | Add object id to uploaded attachments | Tusooa Zhu | |
2022-06-06 | Merge branch 'hackney_reenable_TLSv1.3' into 'develop' | lain | |
hackney adapter helper: enable TLSv1.3 See merge request pleroma/pleroma!3661 | |||
2022-06-05 | Lint | Tusooa Zhu | |
2022-06-05 | Return update notification in mastodon api | Tusooa Zhu | |
2022-06-05 | Create Update notifications | Tusooa Zhu | |
2022-06-04 | Fix CommonAPITest | Tusooa Zhu | |
2022-06-04 | Expose content type of status sources | Tusooa Zhu | |
2022-06-03 | Fix SideEffectsTest | Tusooa Zhu | |
2022-06-03 | Show edited_at in MastodonAPI/show | Tusooa Zhu | |
2022-06-03 | Test that own edits are streamed | Tusooa Zhu | |
2022-06-03 | Stream out edits | Tusooa Zhu | |
2022-06-02 | Fix long report notes giving errors on creation | Tusooa Zhu | |
2022-06-01 | Inject history when object is refetched | Tusooa Zhu | |
2022-06-01 | Strip internal fields in formerRepresentation | Tusooa Zhu | |
2022-05-31 | Implement mastodon api for editing status | Tusooa Zhu | |
2022-05-31 | Add tlsv1.3 to suggestions | Pierre-Louis Bonicoli | |
2022-05-31 | hackney adapter helper & reverse proxy client: enable TLSv1.3 | Pierre-Louis Bonicoli | |
The list of TLS versions was added by 8bd2b6eb138ace3408a03c78ecc339fc35b19f10 when hackney version was pinned to 1.15.2. Later hackney version was upgraded (166455c88441b22455d996ed528ed4804514a3c0) but the list of TLS versions wasn't removed. From the hackney point of view, this list has been replaced by the OTP defaults since 0.16.0 (734694ea4e24f267864c459a2f050e943adc6694). It looks like the same issue already occurred before: 0cb7b0ea8477bdd7af2e5e9071843be5b8623dff. A way to test this issue (where example.com is an ActivityPub site which uses TLSv1.3 only): $ PLEROMA_CONFIG_PATH=/path/to/config.exs pleroma start_iex Erlang/OTP 22 [erts-10.7.2.16] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [hipe] Erlang/OTP 22 [erts-10.7.2.16] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [hipe] Interactive Elixir (1.10.4) - press Ctrl+C to exit (type h() ENTER for help) iex(pleroma@127.0.0.1)2> Pleroma.Object.Fetcher.fetch_and_contain_remote_object_from_id("https://example.com/@/Nick/") {:error, {:tls_alert, {:protocol_version, 'TLS client: In state hello received SERVER ALERT: Fatal - Protocol Version\n'}}} With this patch, the output is the expected one: iex(pleroma@127.0.0.1)3> Pleroma.Object.Fetcher.fetch_and_contain_remote_object_from_id("https://example.com/@/Nick/") {:error, {:ok, %{ "@context" => [ "https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1", %{ "Emoji" => "toot:Emoji", "Hashtag" => "as:Hashtag", "atomUri" => "ostatus:atomUri", "conversation" => "ostatus:conversation", "featured" => "toot:featured", "focalPoint" => %{"@container" => "@list", "@id" => "toot:focalPoint"}, "inReplyToAtomUri" => "ostatus:inReplyToAtomUri", "manuallyApprovesFollowers" => "as:manuallyApprovesFollowers", "movedTo" => "as:movedTo", "ostatus" => "http://ostatus.org#", "sensitive" => "as:sensitive", "toot" => "http://joinmastodon.org/ns#" } ], "endpoints" => %{"sharedInbox" => "https://example.com/inbox"}, "followers" => "https://example.com/@/Nick/followers", "following" => nil, "icon" => %{ "type" => "Image", "url" => "https://example.com/static/media/[...].png" }, "id" => "https://example.com/@/Nick/", "inbox" => "https://example.com/@/Nick/inbox", "liked" => nil, "name" => "Nick", "outbox" => "https://example.com/@/Nick/outbox", "preferredUsername" => "Nick", "publicKey" => %{ "id" => "https://example.com/@/Nick/#main-key", "owner" => "https://example.com/@/Nick/", "publicKeyPem" => "[...] }, "summary" => "", "type" => "Person", "url" => "https://example.com/@/Nick/" }} A way to test the reverse proxy bits of this issue (where example.com allows TLSv1.3 only): iex(pleroma@127.0.0.1)1> Pleroma.ReverseProxy.Client.Hackney.request("GET", "https://example.com", [], []) {:error, {:tls_alert, {:protocol_version, 'TLS client: In state hello received SERVER ALERT: Fatal - Protocol Version\n'}}} | |||
2022-05-30 | Implement viewing source | Tusooa Zhu | |
2022-05-29 | Implement mastodon api for showing edit history | Tusooa Zhu | |
2022-05-29 | Allow updating polls | Tusooa Zhu | |
2022-05-29 | Record edit history for Note and Question Updates | Tusooa Zhu | |
2022-05-29 | Handle Note and Question Updates | Tusooa Zhu | |
2022-05-29 | Allow Updates by every actor on the same origin | Tusooa Zhu | |
2022-05-22 | Merge branch 'lewdthewides-develop-patch-48691' into 'develop' | Haelwenn | |
Instruct users to run 'git pull' as the pleroma user See merge request pleroma/pleroma!3667 | |||
2022-05-22 | BBS: add repeat functionality | duponin | |
2022-05-22 | BBS: show post ID when posted | duponin | |
2022-05-22 | BBS: add post favourite feature | duponin | |
2022-05-21 | Apply Hélène suggestions | Hélène | |
2022-05-21 | BBS: mark notification as read | duponin | |