AkkomaGang/akkoma
AkkomaGang/akkoma
15
65
Fork 92
Code Issues 177 Pull requests 24 Projects 2 Releases 14 Packages Wiki Activity

minor-changes (#313)
Some checks are pending
ci/woodpecker/push/woodpecker Pipeline is pending
Details

Browse source 
Only real change here is making MRF rejects log as debug instead of info (#234)

I don't know if it's the best way to do it, but it seems it's just MRF using this and almost always this is intended.

The rest are just minor docs changes and syncing the restricted nicknames stuff.

I compiled and ran my changes with Docker and they all work.

Co-authored-by: r3g_5z <june@terezi.dev>
Reviewed-on: #313
Co-authored-by: @r3g_5z@plem.sapphic.site <june@girlboss.ceo>
Co-committed-by: @r3g_5z@plem.sapphic.site <june@girlboss.ceo>
This commit is contained in:
@r3g_5z@plem.sapphic.site 2022-11-26 19:27:58 +00:00 committed by floatingghost
parent a90c45b7e9
commit 565ead8397
5 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/docs/configuration/hardening.md
View file

@ -55,11 +55,11 @@ An additional “Strict transport security” header will be sent with the confi
> Recommended value: `same-origin` > Recommended value: `same-origin`
If you click on a link, your browser’s request to the other site will include from where it is coming from. The “Referrer policy” header tells the browser how and if it should send this information. (see [Referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy)) If you click on a link, your browser’s request to the other site will include from where it is coming from. The “Referrer policy” header tells the browser how and if it should send this information. (see [Referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy)). `no-referrer` can be used if a referrer is not needed for improved privacy.
## systemd ## systemd
A systemd unit example is provided at `installation/pleroma.service`. A systemd unit example is provided at `installation/akkoma.service`.
### PrivateTmp ### PrivateTmp

3
docs/docs/installation/docker_en.md
View file

@ -51,7 +51,8 @@ mkdir pgdata
``` ```
This will ask you a few questions - the defaults are fine for most things, This will ask you a few questions - the defaults are fine for most things,
the database hostname is `db`, and you will want to set the ip to `0.0.0.0`. the database hostname is `db`, the database password is `akkoma`
(not auto generated), and you will want to set the ip to `0.0.0.0`.
Now we'll want to copy over the config it just created Now we'll want to copy over the config it just created

2
lib/pleroma/object/fetcher.ex
View file

@ -184,7 +184,7 @@ def fetch_object_from_id!(id, options \\ []) do
nil nil
{:reject, reason} -> {:reject, reason} ->
Logger.info("Rejected #{id} while fetching: #{inspect(reason)}") Logger.debug("Rejected #{id} while fetching: #{inspect(reason)}")
nil nil
e -> e ->

2
lib/pleroma/web/activity_pub/activity_pub.ex
View file

@ -1674,7 +1674,7 @@ def fetch_and_prepare_user_from_ap_id(ap_id, additional \\ []) do
{:error, e} {:error, e}
{:error, {:reject, reason} = e} -> {:error, {:reject, reason} = e} ->
Logger.info("Rejected user #{ap_id}: #{inspect(reason)}") Logger.debug("Rejected user #{ap_id}: #{inspect(reason)}")
{:error, e} {:error, e}
{:error, e} -> {:error, e} ->

2
lib/pleroma/web/api_spec/operations/twitter_util_operation.ex
View file

@ -81,7 +81,7 @@ def change_password_operation do
defp change_password_request do defp change_password_request do
%Schema{ %Schema{
title: "ChangePasswordRequest", title: "ChangePasswordRequest",
description: "POST body for changing the account's passowrd", description: "POST body for changing the account's password",
type: :object, type: :object,
required: [:password, :new_password, :new_password_confirmation], required: [:password, :new_password, :new_password_confirmation],
properties: %{ properties: %{