pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2023-12-27T17:28:33Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3205Support group actor2023-12-27T17:28:33ZtusooaSupport group actorPart of https://git.pleroma.social/pleroma/pleroma/-/issues/656
Backend-wise:
- Ability to mark an actor as Group.
- Upon receiving an Object that has a local Group in its `to` field, boost it automatically if it is boostable.
- If the ...Part of https://git.pleroma.social/pleroma/pleroma/-/issues/656
Backend-wise:
- Ability to mark an actor as Group.
- Upon receiving an Object that has a local Group in its `to` field, boost it automatically if it is boostable.
- If the local Group is only `cc`d, no boost is generated.
- If the local Group has blocked the author of the Object, do not boost.
- If multiple local Groups are mentioned, it should generate multiple boosts.tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/3204Bookmarked objects are not refetched after running prune_objects2024-02-06T05:47:59ZsleepycrowBookmarked objects are not refetched after running prune_objects<!--
### 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): From Source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.6.50-0-g4c5b45ed7-develop+dev
* Elixir version (`elixir -v` for from source installations, N/A for OTP): Elixir 1.14.5, Erlang/OTP 25
* Operating system: Arch Linux
* PostgreSQL version (`psql -V`): 15.4
### Bug description
After running `mix pleroma.database prune_objects`, remote objects in bookmarks older than `remote_post_retention_days` seemingly disappear from bookmarks. Digging around the database reveals the row in the `bookmarks` table still exists, but the object is simply never refetched when querying `/api/v1/bookmarks`.
#### Reproduction steps
1. Set `remote_post_retention_days` in config to `-1`
2. Fetch a remote post and add it to the bookmarks
3. Run `mix pleroma.database prune_objects` and restart pleroma
4. Refresh bookmarks
5. The remote post no longer shows up in the bookmarks
### Notes
After some digging around in the source code, I found that while `Object.normalize/2` _does_ have the option to fetch objects on-the-fly, it is explicitly disabled in MastoAPI's `status_view.ex` ([line 167](https://git.pleroma.social/pleroma/pleroma/-/blob/4c5b45ed73e93e6e8bcfeb527b9b398ec64c0caf/lib/pleroma/web/mastodon_api/views/status_view.ex#L167), [line 236](https://git.pleroma.social/pleroma/pleroma/-/blob/4c5b45ed73e93e6e8bcfeb527b9b398ec64c0caf/lib/pleroma/web/mastodon_api/views/status_view.ex#L236)). Toggling this on causes the issue to disappear, though given that this never seemed to be on(??), coupled with my somewhat lacking knowledge of that part of the internals, I'm not sure if that is the right solution(?)https://git.pleroma.social/pleroma/pleroma/-/issues/3203Federation is not working on my Tor-Only Server.2024-02-06T05:45:48Zanon anonFederation is not working on my Tor-Only Server.I am having an incredibly hard time getting federation to work on my server. When I attempt to add a relay, onion or otherwise, I get the following:
```
03:43:27.365 request_id=F47fGNcrfQEhHv8AACKI [debug] QUERY OK source="users" db=3.0...I am having an incredibly hard time getting federation to work on my server. When I attempt to add a relay, onion or otherwise, I get the following:
```
03:43:27.365 request_id=F47fGNcrfQEhHv8AACKI [debug] QUERY OK source="users" db=3.0ms queue=0.1ms idle=1548.8ms
SELECT u0."id", u0."bio", u0."raw_bio", u0."email", u0."name", u0."nickname", u0."password_hash", u0."keys", u0."public_key", u0."ap_id", u0."avatar", u0."local", u0."follower_address", u0."following_address", u0."featured_address", u0."tags", u0."last_refreshed_at", u0."last_digest_emailed_at", u0."banner", u0."background", u0."note_count", u0."follower_count", u0."following_count", u0."is_locked", u0."is_confirmed", u0."password_reset_pending", u0."is_approved", u0."registration_reason", u0."confirmation_token", u0."default_scope", u0."domain_blocks", u0."is_active", u0."no_rich_text", u0."ap_enabled", u0."is_moderator", u0."is_admin", u0."show_role", u0."uri", u0."hide_followers_count", u0."hide_follows_count", u0."hide_followers", u0."hide_follows", u0."hide_favorites", u0."email_notifications", u0."mascot", u0."emoji", u0."pleroma_settings_store", u0."fields", u0."raw_fields", u0."is_discoverable", u0."invisible", u0."allow_following_move", u0."skip_thread_containment", u0."actor_type", u0."also_known_as", u0."inbox", u0."shared_inbox", u0."accepts_chat_messages", u0."last_active_at", u0."disclose_client", u0."pinned_objects", u0."is_suggested", u0."last_status_at", u0."birthday", u0."show_birthday", u0."language", u0."notification_settings", u0."blocks", u0."mutes", u0."muted_reblogs", u0."muted_notifications", u0."subscribers", u0."multi_factor_authentication_settings", u0."inserted_at", u0."updated_at" FROM "users" AS u0 WHERE (u0."ap_id" = $1) ["http://taffokdpxhzt5uhhaj2iclduxyljjhs5o5nuxzwbhyq2vsnwj3iokfyd.onion/relay"]
03:43:27.376 request_id=F47fGNcrfQEhHv8AACKI [debug] QUERY OK source="users" db=10.3ms idle=1552.7ms
SELECT u0."id", u0."bio", u0."raw_bio", u0."email", u0."name", u0."nickname", u0."password_hash", u0."keys", u0."public_key", u0."ap_id", u0."avatar", u0."local", u0."follower_address", u0."following_address", u0."featured_address", u0."tags", u0."last_refreshed_at", u0."last_digest_emailed_at", u0."banner", u0."background", u0."note_count", u0."follower_count", u0."following_count", u0."is_locked", u0."is_confirmed", u0."password_reset_pending", u0."is_approved", u0."registration_reason", u0."confirmation_token", u0."default_scope", u0."domain_blocks", u0."is_active", u0."no_rich_text", u0."ap_enabled", u0."is_moderator", u0."is_admin", u0."show_role", u0."uri", u0."hide_followers_count", u0."hide_follows_count", u0."hide_followers", u0."hide_follows", u0."hide_favorites", u0."email_notifications", u0."mascot", u0."emoji", u0."pleroma_settings_store", u0."fields", u0."raw_fields", u0."is_discoverable", u0."invisible", u0."allow_following_move", u0."skip_thread_containment", u0."actor_type", u0."also_known_as", u0."inbox", u0."shared_inbox", u0."accepts_chat_messages", u0."last_active_at", u0."disclose_client", u0."pinned_objects", u0."is_suggested", u0."last_status_at", u0."birthday", u0."show_birthday", u0."language", u0."notification_settings", u0."blocks", u0."mutes", u0."muted_reblogs", u0."muted_notifications", u0."subscribers", u0."multi_factor_authentication_settings", u0."inserted_at", u0."updated_at" FROM "users" AS u0 WHERE (u0."ap_id" = $1) ["https://relay.c.im/actor"]
03:43:27.378 request_id=F47fGNcrfQEhHv8AACKI [debug] QUERY OK source="users" db=1.3ms queue=0.1ms idle=1563.0ms
SELECT u0."id", u0."bio", u0."raw_bio", u0."email", u0."name", u0."nickname", u0."password_hash", u0."keys", u0."public_key", u0."ap_id", u0."avatar", u0."local", u0."follower_address", u0."following_address", u0."featured_address", u0."tags", u0."last_refreshed_at", u0."last_digest_emailed_at", u0."banner", u0."background", u0."note_count", u0."follower_count", u0."following_count", u0."is_locked", u0."is_confirmed", u0."password_reset_pending", u0."is_approved", u0."registration_reason", u0."confirmation_token", u0."default_scope", u0."domain_blocks", u0."is_active", u0."no_rich_text", u0."ap_enabled", u0."is_moderator", u0."is_admin", u0."show_role", u0."uri", u0."hide_followers_count", u0."hide_follows_count", u0."hide_followers", u0."hide_follows", u0."hide_favorites", u0."email_notifications", u0."mascot", u0."emoji", u0."pleroma_settings_store", u0."fields", u0."raw_fields", u0."is_discoverable", u0."invisible", u0."allow_following_move", u0."skip_thread_containment", u0."actor_type", u0."also_known_as", u0."inbox", u0."shared_inbox", u0."accepts_chat_messages", u0."last_active_at", u0."disclose_client", u0."pinned_objects", u0."is_suggested", u0."last_status_at", u0."birthday", u0."show_birthday", u0."language", u0."notification_settings", u0."blocks", u0."mutes", u0."muted_reblogs", u0."muted_notifications", u0."subscribers", u0."multi_factor_authentication_settings", u0."inserted_at", u0."updated_at" FROM "users" AS u0 WHERE (u0."ap_id" = $1) ["https://relay.c.im/actor"]
03:43:27.379 request_id=F47fGNcrfQEhHv8AACKI [debug] Fetching object https://relay.c.im/actor via AP
03:43:27.395 request_id=F47fGNcrfQEhHv8AACKI [error] Could not decode user at fetch https://relay.c.im/actor, :checkout_failure
03:43:27.396 request_id=F47fGNcrfQEhHv8AACKI [error] error: :not_found
```
`:checkout failure` would be the final error that happens no matter what relay I use. I included some debug information in case it's helpful.
Searching doesn't seem to yield results even when I use a direct URL to the post.
I am using the OTP version.
OS: `Linux devuan 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux`
I am running in a QEmu virtual machine.
If you need more info please let me know.https://git.pleroma.social/pleroma/pleroma/-/issues/3199docker container broken in latest2024-02-06T05:48:46ZJosh Panterdocker container broken in latest<!--
### 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): Docker Compose
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): "pleroma/pleroma:latest" as of 3 weeks ago - Digest: 2075e2c
* Elixir version (`elixir -v` for from source installations, N/A for OTP):
* Operating system: Docker
* PostgreSQL version (`psql -V`): 12.1-alpine
### Bug description
Updating to the most recent "latest" pleroma/pleroma docker image resulted in the following error when attempting to bring up the container:
` ** (RuntimeError) Configuration at /etc/pleroma/config.exs has world-permissions, execute the following: chmod o= /etc/pleroma/config.exs`
Reverting to "pleroma/pleroma:latest-stable" brought my site back online.https://git.pleroma.social/pleroma/pleroma/-/issues/3198EXIFtool does not strip GPS from apple mov2023-09-25T02:34:00Zfoo barEXIFtool does not strip GPS from apple movYou might have to use ffmpeg instead: https://exiftool.org/forum/index.php?topic=12615.msg68210#msg68210You might have to use ffmpeg instead: https://exiftool.org/forum/index.php?topic=12615.msg68210#msg68210https://git.pleroma.social/pleroma/pleroma/-/issues/3197List of popular posts2023-09-25T02:34:10ZLucas LópezList of popular postsWhat files would be needed to create a listing of popular posts?What files would be needed to create a listing of popular posts?https://git.pleroma.social/pleroma/pleroma/-/issues/3196Custom emoji reactions don’t work for emojis with multi-byte characters2023-10-15T21:28:29ZJaidyn AnnCustom emoji reactions don’t work for emojis with multi-byte characters<!--
### 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): From Source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.5.52-305-gb08cbe76-develop
* Elixir version (`elixir -v` for from source installations, N/A for OTP): 1.14.0
* Operating system: Arch
* PostgreSQL version (`psql -V`): 15.3
### Bug description
Custom emoji reactions for emojis whose names contain accented/multi-byte characters fails with `{"error": "Could not add reaction emoji"}`.
For example, reacting to a post using the custom emojis “s**á**ndwhich” and “sandvi**ĉ**o” fails:
```
$ curl -X PUT -H "Cookie: __Host-pleroma_key=$PLEROMA_KEY" https://jam.xwx.moe/api/v1/pleroma/statuses/AYKj2y6r97QfJhr5rk/reactions/:sandviĉo: | jq
{
"error": "Could not add reaction emoji"
}
$ curl -X PUT -H "Cookie: __Host-pleroma_key=$PLEROMA_KEY" https://jam.xwx.moe/api/v1/pleroma/statuses/AYKj2y6r97QfJhr5rk/reactions/:sándwhich: | jq
{
"error":"Could not add reaction emoji"
}
```
Despite these emojis, “sándwhich” and “sandviĉo”, both being used [in the post body itself](https://jam.xwx.moe/objects/c2a0f978-ea3e-469c-90f5-8b329a5b99f5).
Custom emoji without accented characters (“todoroki_adoras” and “firefox”) work as expected, though:
```
$ curl -X PUT -H "Cookie: __Host-pleroma_key=$PLEROMA_KEY" https://jam.xwx.moe/api/v1/pleroma/statuses/AYKj2y6r97QfJhr5rk/reactions/:todoroki_adoras: | jq
{
[…redact…]
"emoji_reactions": [
{
"account_ids": [
"AVKUbIAGOV9ZVeJxFg"
],
"count": 1,
"me": true,
"name": "firefox",
"url": "https://jam.xwx.moe/emoji/Programaro mezlibera/firefox.png"
},
{
"account_ids": [
"AVKUbIAGOV9ZVeJxFg"
],
"count": 1,
"me": true,
"name": "todoroki_adoras",
"url": "https://jam.xwx.moe/emoji/Laborado!!/todoroki_adoras.png"
}
],
[…redact…]
}
```
(If it’s of any use, here is a simple emoji pack with “sándwhich” and “sandviĉo”, [Testing.tar.gz](/uploads/7810ffc8b9848e293f7283281b43ba10/Testing.tar.gz).)https://git.pleroma.social/pleroma/pleroma/-/issues/3193how can disable default user not have media2024-02-06T05:49:33Zjane lolnhow can disable default user not have mediahello,how can disable default registration user not have media? think's so much!hello,how can disable default registration user not have media? think's so much!https://git.pleroma.social/pleroma/pleroma/-/issues/3192Safe DM does not work with Markdown mode2023-08-17T03:16:18ZtusooaSafe DM does not work with Markdown mode<!--
### 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): [2.5.4-0-g01bc024e9](https://lily-is.land/infra/pleroma/commit/01bc024e9)
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Operating system: the Docker image
* PostgreSQL version (`psql -V`): 13.12
### Bug description
Send `@usera whatever @userb` in Markdown mode when Safe DM is on. userb is mentioned. Sending it in Plain Text mode will not mention userb.https://git.pleroma.social/pleroma/pleroma/-/issues/3188Implement /.well-known/openid-configuration2024-02-06T05:50:29ZGrant sc07Implement /.well-known/openid-configuration[/.well-known/openid-configuration](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata) allows for discovery of the urls for authorization without (requiring) having pleroma-specific code implemented[/.well-known/openid-configuration](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata) allows for discovery of the urls for authorization without (requiring) having pleroma-specific code implementedhttps://git.pleroma.social/pleroma/pleroma/-/issues/31872.5.3: "Reduced permissions of config files and directories, distros requirin...2024-02-06T05:52:41ZKaito2.5.3: "Reduced permissions of config files and directories, distros requiring greater permissions like group-read need to pre-create the directories"Would it be possible to publish a list of config files and directories and their appropriate permissions?Would it be possible to publish a list of config files and directories and their appropriate permissions?https://git.pleroma.social/pleroma/pleroma/-/issues/3186Dockerfile: Harden permissions2023-08-05T11:47:25ZHaelwennDockerfile: Harden permissionsFor example as it's an OTP build, Pleroma shouldn't have write permissions on it's own code.
Compare with <https://gitweb.gentoo.org/repo/proj/guru.git/tree/www-apps/pleroma/pleroma-9999.ebuild>.For example as it's an OTP build, Pleroma shouldn't have write permissions on it's own code.
Compare with <https://gitweb.gentoo.org/repo/proj/guru.git/tree/www-apps/pleroma/pleroma-9999.ebuild>.https://git.pleroma.social/pleroma/pleroma/-/issues/3170Add a notification for the shoutbox2023-07-27T04:47:57Zmiau miauAdd a notification for the shoutboxMe and the users of my pleroma instance really like the shoutbox feature! But it'd be nice if we could get a notification of new incoming messages. Something as basic as an orange circle, at the top right corner of the shoutbox button, w...Me and the users of my pleroma instance really like the shoutbox feature! But it'd be nice if we could get a notification of new incoming messages. Something as basic as an orange circle, at the top right corner of the shoutbox button, would suffice. Currently, there's not much incentive to use shoutbox since we don't get notified of new messages, so we often forget that it's even there.
Here's a crude mockup below of what I mean.
![shoutbox](/uploads/eb83e1ca78c39db98c093f82fb0c4e93/shoutbox.png)https://git.pleroma.social/pleroma/pleroma/-/issues/3168OTP only works with "pleroma@127.0.0.1" node name2023-07-27T04:48:28ZMoon ManOTP only works with "pleroma@127.0.0.1" node nameI am trying to run multiple OTP instances on the same machine. By default they always use "pleroma@127.0.0.1" for the node name. I am able to override this by doing:
```
Environment=ELIXIR_ERL_OPTIONS='-name whatever@127.0.0.1'
```
in ...I am trying to run multiple OTP instances on the same machine. By default they always use "pleroma@127.0.0.1" for the node name. I am able to override this by doing:
```
Environment=ELIXIR_ERL_OPTIONS='-name whatever@127.0.0.1'
```
in the service file, or prepending it to the start command on the cli.
However, when you try to use pleroma_ctl it will automatically connect to "pleroma@127.0.0.1". I discovered this when copying my config to the database overwrote the config for my other otp instance.
If you try doing ELIXIR_ERL_OPTIONS='-name whatever@127.0.0.1' pleroma/bin/pleroma_ctl
you will get an error telling you the node is in use. If you remove ELIXIR_ERL_OPTIONS then it tells you the node is down.
The only way I have been able to admin multiple pleroma OTP on the same machine is, by stopping all the servers, changing the node name of the one I want to work on to "pleroma@127.0.0.1" and then using pleroma_ctl.https://git.pleroma.social/pleroma/pleroma/-/issues/3158MIME Type/Tags route xml2023-07-27T15:55:09ZLucas LópezMIME Type/Tags route xml### Environment
* Soapbox version:Soapbox 3.2.0-72de8fb
* Backend:Pleroma+soapbox 2.5.52-440-g7fd0b309.develop
* Browser/OS: Windows 11 - Chrome & EDGE
### Bug description
There is a problem with MIME type in soapbox/plaroma, where wh...### Environment
* Soapbox version:Soapbox 3.2.0-72de8fb
* Backend:Pleroma+soapbox 2.5.52-440-g7fd0b309.develop
* Browser/OS: Windows 11 - Chrome & EDGE
### Bug description
There is a problem with MIME type in soapbox/plaroma, where when accessing svg files uploaded in the uploads(media) folder, it ends up looking like a text/plan or text/html and with that it renders as if it were a text and not an svg of fat.
Also when I access the mywebsite.com.br/tags/hashtag page directly in the browser it renders the website code and not the page itself it also happens only when accessed directly, it seems to be a problem in the proxy config in nginx, how to fix ? I'm using the original filehttps://git.pleroma.social/pleroma/pleroma/-/issues/3152Requesting archive for deactivated user2023-07-03T15:01:32ZtusooaRequesting archive for deactivated userCurrently an archive for deactivated users won't fetch their outbox correctly, as deactivated users are excluded in the query. It would be desirable to have deactivated users archive their posts properly.Currently an archive for deactivated users won't fetch their outbox correctly, as deactivated users are excluded in the query. It would be desirable to have deactivated users archive their posts properly.https://git.pleroma.social/pleroma/pleroma/-/issues/3149no function clause matching in Pleroma.Web.Metadata.Utils.scrub_html_and_trun...2023-07-07T00:44:59ZWesley Mooreno function clause matching in Pleroma.Web.Metadata.Utils.scrub_html_and_truncate/3 when fetching feed### Environment
* Installation type: Source
* Pleroma version: 2.5.2
* Elixir version: 1.14.4
* Operating system: Alpine Linux
* PostgreSQL version: 12
### Bug description
I am attempting to create an archive of my public posts from m...### Environment
* Installation type: Source
* Pleroma version: 2.5.2
* Elixir version: 1.14.4
* Operating system: Alpine Linux
* PostgreSQL version: 12
### Bug description
I am attempting to create an archive of my public posts from my Pleroma instance. While I do have access to the database this is a pretty raw form and in the absence of a supported export mechanism I noticed that the Atom feed seems pretty complete and supports paging. I wrote a script to fetch the feed for my user, following the `link rel="next"` link in each document. However, after 38 documents fetching the specified next URL results in an Phoenix error:
![error](/uploads/c7afba4c50ba695470ea3e91417ac820/image.png)
You can see it for yourself at <https://decentralised.social/users/wezm/feed.atom?max_id=9kSDsXZb4f6E80QjAm>
At first I thought that I had perhaps reached the last document but looking at the entries in the preceding document suggests that not the case.https://git.pleroma.social/pleroma/pleroma/-/issues/3143Tag Specific Moderation2023-07-01T21:47:48ZiacoreTag Specific ModerationThis issue is mainly about tag-specific moderation.
For Pleroma to act like Reddit, I think the following points are missing.
1. moderators for a specific tag (tags can act like subreddit)
2. indentation based on replies in frontend; s...This issue is mainly about tag-specific moderation.
For Pleroma to act like Reddit, I think the following points are missing.
1. moderators for a specific tag (tags can act like subreddit)
2. indentation based on replies in frontend; so that the posts are easier to read like Reddit/Hacker News
3. downvote
It is not a stretch for Pleroma to serve as a forum (backend logic -wise).https://git.pleroma.social/pleroma/pleroma/-/issues/3142Failure to parse paginated featured collection2023-07-02T15:06:21Zsilverpill silverpillFailure to parse paginated featured collectionIf actor's `featured` collection doesn't have `orderedItems` property (and has a pointer to `OrderedCollectionPage` instead), signature check fails, incoming activity gets dropped and `{"errors":{"detail":"Internal server error"}}` respo...If actor's `featured` collection doesn't have `orderedItems` property (and has a pointer to `OrderedCollectionPage` instead), signature check fails, incoming activity gets dropped and `{"errors":{"detail":"Internal server error"}}` response is returned.
I guess the error comes for [`pin_data_from_featured_collection`](https://git.pleroma.social/pleroma/pleroma/-/blob/043a00991dec09f5804df1db1fdc1b1179843453/lib/pleroma/web/activity_pub/activity_pub.ex#L1712).https://git.pleroma.social/pleroma/pleroma/-/issues/3139Lists are limited to around 180 accounts due to indexing limitations2023-08-11T04:27:39ZCarlos SolísLists are limited to around 180 accounts due to indexing limitations### Environment
* Installation type (OTP or From Source): OTP
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.5.2
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Oper...### Environment
* Installation type (OTP or From Source): OTP
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.5.2
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Operating system: Debian 11 Bullseye
* PostgreSQL version (`psql -V`): 13.11
### Bug description
When adding a new account to a list, if that list already has enough items, the new addition will fail due to the way that lists are implemented and indexed in the PostgreSQL database.
To replicate:
- On your Pleroma account, open a new list
- Proceed to add accounts to that group
- Eventually, adding a new account to the group will fail with a generic error message.
- Check the logs:
```
pleroma[3589497]: 13:23:23.889 request_id=F2p0aMyDYOMTLgwAAvJi [error] Internal server error: %Postgrex.Error{message: nil, postgres: %{code: :program_limit_exceeded, constraint: "lists_following_index", detail: "Index row references tuple (0,9) in relation \"lists\".", file: "nbtutils.c", hint: "Values larger than 1/3 of a buffer page cannot be indexed.\nConsider a function index of an MD5 hash of the value, or use full text indexing.", line: "2662", message: "index row size 2712 exceeds btree version 4 maximum 2704 for index \"lists_following_index\"", pg_code: "54000", routine: "_bt_check_third_page", schema: "public", severity: "ERROR", table: "lists", unknown: "ERROR"}, connection_id: 3662753, query: nil}
pleroma[3589497]: 13:23:23.891 [error] #PID<0.12250.1> running Pleroma.Web.Endpoint (connection #PID<0.12249.1>, stream id 1) terminated
pleroma[3589497]: Server: social.example.net:80 (http)
pleroma[3589497]: Request: POST /api/v1/lists/13/accounts
pleroma[3589497]: ** (exit) an exception was raised:
pleroma[3589497]: ** (Postgrex.Error) ERROR 54000 (program_limit_exceeded) index row size 2712 exceeds btree version 4 maximum 2704 for index "lists_following_index"
pleroma[3589497]: table: lists
pleroma[3589497]: constraint: lists_following_index
pleroma[3589497]: hint: Values larger than 1/3 of a buffer page cannot be indexed.
pleroma[3589497]: Consider a function index of an MD5 hash of the value, or use full text indexing.
pleroma[3589497]: Index row references tuple (0,9) in relation "lists".
pleroma[3589497]: (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
pleroma[3589497]: (ecto 3.9.5) lib/ecto/repo/schema.ex:756: Ecto.Repo.Schema.apply/4
pleroma[3589497]: (ecto 3.9.5) lib/ecto/repo/schema.ex:459: anonymous fn/15 in Ecto.Repo.Schema.do_update/4
pleroma[3589497]: (elixir 1.14.3) lib/enum.ex:975: Enum."-each/2-lists^foreach/1-0-"/2
pleroma[3589497]: (pleroma 3.9.3-0-g39b3d92-develop) lib/pleroma/web/mastodon_api/controllers/list_controller.ex:66: Pleroma.Web.MastodonAPI.ListController.add_to_list/2
pleroma[3589497]: (pleroma 3.9.3-0-g39b3d92-develop) lib/pleroma/web/mastodon_api/controllers/list_controller.ex:5: Pleroma.Web.MastodonAPI.ListController.action/2
pleroma[3589497]: (pleroma 3.9.3-0-g39b3d92-develop) lib/pleroma/web/mastodon_api/controllers/list_controller.ex:5: Pleroma.Web.MastodonAPI.ListController.phoenix_controller_pipeline/2
pleroma[3589497]: (phoenix 1.6.16) lib/phoenix/router.ex:354: Phoenix.Router.__call__/2
```