pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2022-09-03T02:03:50Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/2807Remote interaction with posts2022-09-03T02:03:50ZtusooaRemote interaction with postsXref: https://kazv.moe/notice/AEfGS5pcRpKtJDtFYG
Currently the BE only supports remotely interacting with users (remote follow), but not posts, through the web ui.
There is an API newly added ( https://git.pleroma.social/pleroma/plero...Xref: https://kazv.moe/notice/AEfGS5pcRpKtJDtFYG
Currently the BE only supports remotely interacting with users (remote follow), but not posts, through the web ui.
There is an API newly added ( https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3545/diffs#4e17d67d25cb5ba572c1e9c9eef818ceae110ffc ) but we still need ui (/main/ostatus) for it.https://git.pleroma.social/pleroma/pleroma/-/issues/2804User-Agent is not set2022-01-08T05:36:20ZPete ZaitcevUser-Agent is not setIt appears that my instance makes outgoing http requests with adapter's default User-Agent. If I configure Hackney, User-agent is "hackney/1.18.0". If I configure Gun, User-agent is missing.
This causes certain instances to reject me, b...It appears that my instance makes outgoing http requests with adapter's default User-Agent. If I configure Hackney, User-agent is "hackney/1.18.0". If I configure Gun, User-agent is missing.
This causes certain instances to reject me, because they sit behind Cloudflare, and whitelist Pleroma by User-Agent om WAF. If my instance does not provide a normal User-Agent, Cloudflare rejects my requests, so my instance cannot federate.
I am on the develop branch.
I tried to set user_agent explicitly, like the following, but it made absolutely no difference:
config :pleroma, :http,
proxy_url: nil,
send_user_agent: true,
user_agent: "Pleroma 2.4.1-yukiho; https://mu.zaitcev.nu <zaitcev@yahoo.com>",
adapter: []
It's a little suspicious that I am the only one having these issues. Other Pleroma instances that I federate with send User-Agent correctly.https://git.pleroma.social/pleroma/pleroma/-/issues/2802Mastodon's "remove follower" does not properly propagate2022-01-09T19:03:37ZtusooaMastodon's "remove follower" does not properly propagate<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source): OTP
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): https://lily.kazv.moe/infra/pleroma/-/commit/d7fe6967
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Operating system: Docker image on Ubuntu 20.04
* PostgreSQL version (`psql -V`): 13.3
### Bug description
#### Reproducing steps
0. I followed `tusooa@t.tusooa.xyz` from `testuser@lm.kazv.moe`.
1. On `tusooa@t.tusooa.xyz`, I removed the follower `testuser@lm.kazv.moe`.
2. `GET https://lm.kazv.moe/api/v1/accounts/relationships/?id=ABH0GcHwNlq0ueR0t6` (`ABH0GcHwNlq0ueR0t6` is the account id for `tusooa@t.tusooa.xyz`).
#### Expected behaviour
In (2) the `following` property should be false.
#### Actual behaviour
In (2) the `following` property is true.
#### Some analysis
Firstly, `UserRelationship.view_relationships_option(user, targets)` yields no relationship between the two.
In `Pleroma.Web.MastodonAPI.AccountView.render("relationship.json", ...)`, there is
```
follow_state =
if following_relationships do
user_to_target_following_relation =
FollowingRelationship.find(following_relationships, reading_user, target)
User.get_follow_state(reading_user, target, user_to_target_following_relation)
else
User.get_follow_state(reading_user, target)
end
```
I checked it, `following_relationships` is `[]`; `user_to_target_following_relation` gives `nil`; and `User.get_follow_state(reading_user, target, user_to_target_following_relation)` is to be executed, as `[]` is true.
Now
```
def get_follow_state(
%User{} = follower,
%User{} = following,
following_relationship
) do
case {following_relationship, following.local} do
{nil, false} ->
case Utils.fetch_latest_follow(follower, following) do
%Activity{data: %{"state" => state}} when state in ["pending", "accept"] ->
FollowingRelationship.state_to_enum(state)
_ ->
nil
end
{%{state: state}, _} ->
state
{nil, _} ->
nil
end
end
```
As here `following_relationship` is `nil`, and `following` is a remote user, `{nil, false}` branch will be executed. `Utils.fetch_latest_follow(follower, following)` does give us the follow activity, whose state is indeed `accept`. Thus we have the problem described above.
##### Tracing
`/opt/pleroma/bin/pleroma remote`:
```
> testuser = Pleroma.User.get_by_nickname("testuser")
> tusooa = Pleroma.User.get_by_nickname("tusooa@t.tusooa.xyz")
iex(pleroma@127.0.0.1)3> Pleroma.Web.MastodonAPI.AccountView.render("relationships.json", user: testuser, targets: [tusooa])
16:16:07.418 [debug] QUERY OK source="user_relationships" db=2.9ms queue=0.1ms idle=545.4ms
SELECT u0."relationship_type", u0."source_id", u0."target_id" FROM "user_relationships" AS u0 WHERE ((source_id = ANY($1) AND target_id = ANY($2) AND relationship_type = ANY($3)) OR (source_id = ANY($4) AND target_id = ANY($5) AND relationship_type = ANY($6))) [[<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [1, 2, 4, 3], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [1, 5]]
16:16:07.422 [debug] QUERY OK source="following_relationships" db=1.8ms idle=524.0ms
SELECT f0."id", f0."state", f0."follower_id", f0."following_id", f0."inserted_at", f0."updated_at" FROM "following_relationships" AS f0 WHERE ((follower_id = ANY($1) AND following_id = ANY($2)) OR (follower_id = ANY($3) AND following_id = ANY($4))) [[<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>]]
16:16:07.426 [debug] QUERY OK source="activities" db=2.7ms queue=0.1ms idle=438.2ms
SELECT a0."id", a0."data", a0."local", a0."actor", a0."recipients", a0."inserted_at", a0."updated_at" FROM "activities" AS a0 WHERE ((a0."data")->>'type' = $1) AND (a0."actor" = $2) AND (coalesce((a0."data")->'object'->>'id', (a0."data")->>'object') = $3) ORDER BY a0."id" desc nulls last LIMIT 1 ["Follow", "https://lm.kazv.moe/users/testuser", "https://t.tusooa.xyz/users/tusooa"]
[
%{
blocked_by: false,
blocking: false,
domain_blocking: false,
endorsed: false,
followed_by: false,
following: true,
id: "ABH0GcHwNlq0ueR0t6",
muting: false,
muting_notifications: false,
requested: false,
showing_reblogs: true,
subscribing: false
}
]
iex(pleroma@127.0.0.1)4> Pleroma.UserRelationship.view_relationships_option(testuser, [tusooa])
16:17:09.604 [debug] QUERY OK source="user_relationships" db=2.6ms queue=0.1ms idle=642.0ms
SELECT u0."relationship_type", u0."source_id", u0."target_id" FROM "user_relationships" AS u0 WHERE ((source_id = ANY($1) AND target_id = ANY($2) AND relationship_type = ANY($3)) OR (source_id = ANY($4) AND target_id = ANY($5) AND relationship_type = ANY($6))) [[<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [1, 2, 4, 3], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [1, 5]]
16:17:09.607 [debug] QUERY OK source="following_relationships" db=2.2ms idle=546.3ms
SELECT f0."id", f0."state", f0."follower_id", f0."following_id", f0."inserted_at", f0."updated_at" FROM "following_relationships" AS f0 WHERE ((follower_id = ANY($1) AND following_id = ANY($2)) OR (follower_id = ANY($3) AND following_id = ANY($4))) [[<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 216, 31, 91, 244, 191, 161, 230, 249, 45, 181, 0, 0>>], [<<0, 0, 1, 123, 184, 19, 217, 197, 204, 50, 165, 136, 249, 221, 0, 0>>]]
%{following_relationships: [], user_relationships: []}
```
### Misc
@cobaltkisshttps://git.pleroma.social/pleroma/pleroma/-/issues/2800Not understanding how stream API work2021-12-17T16:46:14ZFikran Mutasa'ilNot understanding how stream API workHi all!
I am not understanding the API documentation on how Pleroma's API streaming works and have not been able to get it working.
At the moment, I am working with some code that uses `/api/v1/timelines/public` on a public timeline. I...Hi all!
I am not understanding the API documentation on how Pleroma's API streaming works and have not been able to get it working.
At the moment, I am working with some code that uses `/api/v1/timelines/public` on a public timeline. I would like to convert my code to use the streamed timeline. Is there a specific section of the API I should reference? Does anyone have any client code I could look at, preferably written in python or go? (but any language will suffice)
Been on this on and off for a few months :(https://git.pleroma.social/pleroma/pleroma/-/issues/2799Cannot delete own account2021-12-15T21:26:47ZAlex GleasonCannot delete own accountv2.4.1
POST `/api/pleroma/delete_account`
Request body:
```json
{
"password": "my password"
}
```
Response:
```json
{
"error": "Invalid password."
}
```
`my password` is indeed the user's password.
The endpoint returns a 200 r...v2.4.1
POST `/api/pleroma/delete_account`
Request body:
```json
{
"password": "my password"
}
```
Response:
```json
{
"error": "Invalid password."
}
```
`my password` is indeed the user's password.
The endpoint returns a 200 response even if an error is present. The account is not deleted.https://git.pleroma.social/pleroma/pleroma/-/issues/2798syslog not compiling (OTP 24)2022-01-20T00:21:19ZJoel Beckmeyersyslog not compiling (OTP 24)Having syslog compile issue with this version:
```
$ elixir -v
Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit]
Elixir 1.13.0 (compiled with Erlang/OTP 24)
```
Log from build below:
```
==...Having syslog compile issue with this version:
```
$ elixir -v
Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit]
Elixir 1.13.0 (compiled with Erlang/OTP 24)
```
Log from build below:
```
==> captcha
rm -f priv/captcha src/captcha.o
cc -g -c -o src/captcha.o src/captcha.c
mkdir -p priv
cc -I src -o priv/captcha -Wl,-z,relro -Wl,-z,now -Wl,--as-needed src/captcha.o
Compiling 1 file (.ex)
Generated captcha app
==> restarter
Compiling 2 files (.ex)
warning: Logger.__do_log__/4 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
warning: Logger.__should_log__/2 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
warning: Logger.debug/1 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
Generated restarter app
==> earmark_parser
Compiling 1 file (.yrl)
Compiling 2 files (.xrl)
Compiling 3 files (.erl)
Compiling 32 files (.ex)
Generated earmark_parser app
==> jumper
Compiling 1 file (.ex)
Generated jumper app
===> Analyzing applications...
===> Compiling parse_trans
==> unsafe
Compiling 3 files (.ex)
Generated unsafe app
make: Entering directory '/builddir/pleroma-develop/deps/eblurhash/c_src'
make: '/builddir/pleroma-develop/deps/eblurhash/c_src/../priv/blurhash' is up to date.
make: Leaving directory '/builddir/pleroma-develop/deps/eblurhash/c_src'
===> Analyzing applications...
===> Compiling eblurhash
===> Analyzing applications...
===> Compiling mimerl
==> nimble_pool
Compiling 2 files (.ex)
Generated nimble_pool app
==> connection
Compiling 1 file (.ex)
Generated connection app
warning: Mix.Local.path_for/1 is deprecated. Use Mix.path_for/1 instead
mix.exs:38: NimbleParsec.MixProject.build_docs/1
==> nimble_parsec
Compiling 4 files (.ex)
Generated nimble_parsec app
==> bbcode_pleroma
Compiling 3 files (.ex)
Generated bbcode_pleroma app
===> Fetching rebar3_hex v6.11.8
===> Fetching hex_core v0.7.1
===> Fetching verl v1.0.2
===> Analyzing applications...
===> Compiling verl
===> Compiling hex_core
===> Compiling rebar3_hex
_build/default/plugins/rebar3_hex/src/rebar3_hex_repo.erl:128:32: Warning: public_key:ssh_encode/2 is deprecated and will be removed in OTP 26; use ssh_file:encode/2 instead
===> Analyzing applications...
===> Compiling sleeplocks
===> Analyzing applications...
===> Compiling metrics
===> Analyzing applications...
===> Compiling unicode_util_compat
===> Analyzing applications...
===> Compiling idna
==> gettext
Compiling 1 file (.yrl)
Compiling 1 file (.erl)
Compiling 20 files (.ex)
Generated gettext app
==> deep_merge
Compiling 2 files (.ex)
Generated deep_merge app
==> jose
Compiling 106 files (.erl)
Compiling 8 files (.ex)
Generated jose app
==> benchee
Compiling 39 files (.ex)
Generated benchee app
===> Fetching pc v1.13.0
===> Analyzing applications...
===> Compiling pc
===> Analyzing applications...
===> Compiling syslog
===> Compiling c_src/syslog_drv.c
===> Linking priv/syslog_drv.so
===> Missing artifact priv/syslog_drv.so
==> pleroma
** (Mix) Could not compile dependency :syslog, "/tmp/.mix/rebar3 bare compile --paths /builddir/pleroma-develop/_build/prod/lib/*/ebin" command failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile syslog", update it with "mix deps.update syslog" or clean it with "mix deps.clean syslog"
```
It looks like there has been some other issues like this, but they were closed with merged fixes, so I'm not sure if this new...https://git.pleroma.social/pleroma/pleroma/-/issues/2796Chat messages are streamed as DMs into home timeline2022-09-03T18:24:29Zrinpatchrin+pleroma@patch.cxChat messages are streamed as DMs into home timelineOn refresh they obviously disappear since rest filters them properly.On refresh they obviously disappear since rest filters them properly.https://git.pleroma.social/pleroma/pleroma/-/issues/2794Attachment dimensions aren't ingested properly anymore2021-12-09T16:05:08ZAlex GleasonAttachment dimensions aren't ingested properly anymoreI added the ability to federate attachment dimensions in !3404
This no longer works in v2.4.1. The data is federated properly, but it's not ingested anymore.
`Transmogrifier.fix_object/1` is no longer getting called during ingestion, a...I added the ability to federate attachment dimensions in !3404
This no longer works in v2.4.1. The data is federated properly, but it's not ingested anymore.
`Transmogrifier.fix_object/1` is no longer getting called during ingestion, and it's left up entirely to the `ArticleNotePageValidator`. The validator doesn't include the logic to rewrite the attachment dimensions into the correct format.https://git.pleroma.social/pleroma/pleroma/-/issues/2792Activity.restrict_deactivated_users has a massive impact on certain queries2021-12-06T19:55:54ZSadposterActivity.restrict_deactivated_users has a massive impact on certain queries### Environment
* Installation type (OTP or From Source): From source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): Latest master w/additions, 2.4.51-353-gc85b278f-develop
* Elixir version (`elixir ...### Environment
* Installation type (OTP or From Source): From source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): Latest master w/additions, 2.4.51-353-gc85b278f-develop
* Elixir version (`elixir -v` for from source installations, N/A for OTP): 1.10.4
* Operating system: Ubuntu 20.04
* PostgreSQL version (`psql -V`): 12.8
### Bug description
I had a user report being unable to view their timeline, logs showed the standard ecto timeouts. I duplicated the query to play around with it, and tried removing parts of the query at random to find out what was taking time, since there was no obvious difference between my user and the user experiencing the issue. A large part was thread containment, which has been known about for a while, but the more interesting one was deactivated users
when not excluding deactivated users, the query time dropped 70% - there's already an index on is_active so I'm not sure what might cause this
timings attached
![image](/uploads/eb84be7de71baf35a8cdda364b40eb93/image.png)
![image](/uploads/68656e9a2e29d529af505dbea6bdbc87/image.png)https://git.pleroma.social/pleroma/pleroma/-/issues/2791Certain emojis don't stick on some instances/platforms2022-08-27T15:04:30ZmeowskiCertain emojis don't stick on some instances/platformsA pleroma user noticed that certain religious emoji reacts like the star of david and cross are not sticking on some instances (kf, spc). They will appear in the react initially, but upon refresh they are gone.
However on my Pleroma 2...A pleroma user noticed that certain religious emoji reacts like the star of david and cross are not sticking on some instances (kf, spc). They will appear in the react initially, but upon refresh they are gone.
However on my Pleroma 2.2.2 on apache + fedora linux, they do stick. Confirmed working on after a refresh.
Not sure if this would be a back end or front end issue, but admins of KF and SPC said they are not blocking these emojis.![Screenshot_from_2021-12-04_13-58-46](/uploads/a93934190c4ec46dd96667b708f59f68/Screenshot_from_2021-12-04_13-58-46.png)https://git.pleroma.social/pleroma/pleroma/-/issues/2790Can't follow accounts on Pixelfed instances2022-05-09T09:41:46ZBen HikerCan't follow accounts on Pixelfed instancesI am not able to follow an account on a Pixelfed instance. The button "follow" indicates all the time "Request sent". In Pixelfed the request is noted and the Pleroma user is displayed as followed. But postings on Pixelfed don't appear i...I am not able to follow an account on a Pixelfed instance. The button "follow" indicates all the time "Request sent". In Pixelfed the request is noted and the Pleroma user is displayed as followed. But postings on Pixelfed don't appear in the TL of Pleroma... seems Pleroma don't understand the AP answer of Pixelfed.https://git.pleroma.social/pleroma/pleroma/-/issues/2789Password reset probably doesn't work anymore2021-12-03T15:13:12ZAlex GleasonPassword reset probably doesn't work anymoreRemoving MastoFE in https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3392/diffs#e6e3618554a28f92c13eb3dc85b9a85111f24cf4_763_738 removed POST `/auth/password` which was being used as a RESTful API endpoint by frontends.
There...Removing MastoFE in https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3392/diffs#e6e3618554a28f92c13eb3dc85b9a85111f24cf4_763_738 removed POST `/auth/password` which was being used as a RESTful API endpoint by frontends.
There's no other way to request a password reset through the API.https://git.pleroma.social/pleroma/pleroma/-/issues/2788Blows up when user.pinned_objects is nil2021-11-29T18:08:12ZNEETzscheBlows up when user.pinned_objects is nil```
Server: iddqd.social:80 (http)
Request: GET /api/v1/accounts/xxxxxxxx/statuses?only_media=true&limit=40&with_muted=true
** (exit) an exception was raised:
** (BadMapError) expected a map, got: nil
(stdlib 3.14.2.1) :m...```
Server: iddqd.social:80 (http)
Request: GET /api/v1/accounts/xxxxxxxx/statuses?only_media=true&limit=40&with_muted=true
** (exit) an exception was raised:
** (BadMapError) expected a map, got: nil
(stdlib 3.14.2.1) :maps.keys(nil)
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/activity_pub/activity_pub.ex:644: Pleroma.Web.ActivityPub.ActivityPub.fetch_activities_for_user/3
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/activity_pub/activity_pub.ex:634: Pleroma.Web.ActivityPub.ActivityPub.fetch_user_activities/3
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/mastodon_api/controllers/account_controller.ex:294: Pleroma.Web.MastodonAPI.AccountController.statuses/2
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/mastodon_api/controllers/account_controller.ex:5: Pleroma.Web.MastodonAPI.AccountController.action/2
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/mastodon_api/controllers/account_controller.ex:5: Pleroma.Web.MastodonAPI.AccountController.phoenix_controller_pipeline/2
(phoenix 1.5.9) lib/phoenix/router.ex:352: Phoenix.Router.__call__/2
(pleroma 2.4.1-206-gf457f52a-block-notification-policy) lib/pleroma/web/endpoint.ex:5: Pleroma.Web.Endpoint.plug_builder_call/2
```
It shouldn't do that.https://git.pleroma.social/pleroma/pleroma/-/issues/2784Pleroma on arm64 fails with /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __ppoll...2021-11-17T20:00:51ZGuy ShefferPleroma on arm64 fails with /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __ppoll_time64: symbol not foundWhen running pleroma from the develop branch docker container it crashes with this error:
I also tried building locally on a raspberrypi to make sure the build here is working correctly, and it seems like the error pops up even when bui...When running pleroma from the develop branch docker container it crashes with this error:
I also tried building locally on a raspberrypi to make sure the build here is working correctly, and it seems like the error pops up even when building on arm64 processor.
```
pleroma | pleroma-db:5432 - accepting connections
pleroma | -- Running migrations...
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __ppoll_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __gmtime64_r: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __clock_gettime64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __stat_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __getrusage_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __localtime64_r: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __mktime64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __clock_getres_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __ctime64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __lstat_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __timerfd_settime64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __dlsym_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __utime64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __fstat_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __gettimeofday_time64: symbol not found
pleroma | Error relocating /opt/pleroma/erts-10.7.2.14/bin/beam.smp: __select_time64: symbol not found
```https://git.pleroma.social/pleroma/pleroma/-/issues/2782Feature request: Add activeMonth and activeHalfyear into usage.users in the n...2021-12-02T16:54:30ZHakaba HitoyoFeature request: Add activeMonth and activeHalfyear into usage.users in the nodeinfo.The number of monthly active users is already in the /api/v1/instance by !3283, but the API is not suit for standards. In the nodeinfo standard, activeMonth and activeHalfyear should be at the `usage.users` section.
This feature will ha...The number of monthly active users is already in the /api/v1/instance by !3283, but the API is not suit for standards. In the nodeinfo standard, activeMonth and activeHalfyear should be at the `usage.users` section.
This feature will have a practical application: https://the-federation.info/ 's lists of instances are sorted by the active monthly users. Now the sort does not work well for the Pleroma instances, however, this feature will fix it.https://git.pleroma.social/pleroma/pleroma/-/issues/2777mrf to reject mass mentions2021-11-07T10:57:27Ztusooamrf to reject mass mentionsas title, reject all objects that mentions too many (admin setable threshold) people.as title, reject all objects that mentions too many (admin setable threshold) people.https://git.pleroma.social/pleroma/pleroma/-/issues/2776`docker build` fails with compilation error in crypt since !35272021-11-17T20:48:56Zbarrucadu`docker build` fails with compilation error in crypt since !3527<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
Docker:
```
git clone https://git.pleroma.social/pleroma/pleroma.git
cd pleroma
docker build .
```
### Bug description
There's a compilation failure with the crypt dependency:
```
** (Mix) Could not compile dependency :crypt, "/root/.mix/rebar3 bare compile --paths /_build/prod/lib/*/ebin" command failed. You can recompile this dependency with "mix deps.compile crypt", update it with "mix deps.update crypt" or clean it with "mix deps.clean crypt"
```
This seems to have been introduced by !3527
I tried changing the base image to the newest version, `elixir:1.12-alpine`, but that didn't help.https://git.pleroma.social/pleroma/pleroma/-/issues/2775Foreign emoji denylist2023-07-07T16:27:33ZpiggoForeign emoji denylistI wish there was a way to ban certain foreign emoji.
Specifically to ban animated ones like hyper bun that's insane flashing with 2 frames, but that will be difficult without a media proxy stripping the animation.
I found it can be do...I wish there was a way to ban certain foreign emoji.
Specifically to ban animated ones like hyper bun that's insane flashing with 2 frames, but that will be difficult without a media proxy stripping the animation.
I found it can be done with the Replace MRF, but its kinda janky and I think you can't have the colons in the search text.
![Screenshot_20211019_102726](/uploads/5b11e143acad8b7bce70c23f6f1730db/Screenshot_20211019_102726.png)tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/2772Unable to delete a post2021-10-13T18:15:49ZSnowUnable to delete a postThis is related with:
https://git.pleroma.social/pleroma/pleroma/-/issues/2771
I tried to delete that certain post, but the post this still in there.This is related with:
https://git.pleroma.social/pleroma/pleroma/-/issues/2771
I tried to delete that certain post, but the post this still in there.https://git.pleroma.social/pleroma/pleroma/-/issues/2770Media preview proxy always returns `Can't fetch HTTP headers.`2021-11-10T14:27:58ZdebulaMedia preview proxy always returns `Can't fetch HTTP headers.`Yesterday I found my media preview proxy was broken. It always returns `424 Failed Dependency - Can't fetch HTTP headers.` but leave no errors in log.
According to source code: https://git.pleroma.social/pleroma/pleroma/-/blob/develop/...Yesterday I found my media preview proxy was broken. It always returns `424 Failed Dependency - Can't fetch HTTP headers.` but leave no errors in log.
According to source code: https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/web/media_proxy/media_proxy_controller.ex#L81 , it seems that the HEAD request failed. Can someone help me? I still have no clues.
I tried but failed:
- reinstall imagemagick.
- restart pleroma.
- re-enable image preview proxy.
And media proxy works as usual.