pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2024-02-06T05:43:42Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3217scoped notifications2024-02-06T05:43:42ZJeff Cliffscoped notificationshttps://a2mi.social/@MegaMichelle/111385398640070512
https://infosec.exchange/@CppGuy/111393303860768677
@MegaMichelle@a2mi.social
came up with an interesting and useful idea(originally for mastodong but equally valid idea for pleroma)...https://a2mi.social/@MegaMichelle/111385398640070512
https://infosec.exchange/@CppGuy/111393303860768677
@MegaMichelle@a2mi.social
came up with an interesting and useful idea(originally for mastodong but equally valid idea for pleroma): thread scoped notifications
here's the scenario
Dr. A actually knows something about topic B.
Dr. A is in a thread with a bunch of dumb shits who waste everyone's time, we'll call them C D E F and G.
Dr. A wades in every couple 1000 posts and says something like "no actually blahblahblah" and then goes back to lurking and watching C D E F and G talk amongst themselves
what Dr. A says is actually valuable but *not* valuable enough to auto notify based on *every* thread he's in. Perhaps you're particularly interested in what he says about topic B. You could search by hashtag, or by keyword, but another useful thing would be is if the fact that he was posting in that thread itself was occurring, that you want to be notified.
Perhaps some kind of option right around the 'mute this thread' one could be 'notify when this user participates in this thread'.https://git.pleroma.social/pleroma/pleroma/-/issues/3216Latency POSTing to the /inbox2023-12-11T16:28:56ZfeldLatency POSTing to the /inboxAfter some exploratory work in !3985 it's clear that there's less than ideal performance with POSTing to an inbox under some conditions. The primary issue is related to signature validation when we have to fetch the actor's public key. I...After some exploratory work in !3985 it's clear that there's less than ideal performance with POSTing to an inbox under some conditions. The primary issue is related to signature validation when we have to fetch the actor's public key. If either server is under load it can really increase the time to process the request to several seconds or more.
I think it may be possible to do some kind of "optimistic" validation where if we have the key and can validate immediately we should do so, otherwise we should accept the activity and delay the signature validation until the Oban job executes to process the activity.
Does this seem like a reasonable approach?https://git.pleroma.social/pleroma/pleroma/-/issues/3215Replace clear_config with explicit mocks via Mox2024-02-06T05:44:13ZlainReplace clear_config with explicit mocks via Moxclear_config changes the global state and makes it impossible for tests to run asynchronously.clear_config changes the global state and makes it impossible for tests to run asynchronously.https://git.pleroma.social/pleroma/pleroma/-/issues/3214Replace Mock/Meck with Mox2024-02-06T05:43:54ZlainReplace Mock/Meck with MoxMock/Meck work by redefining modules and modifying the global state, making it impossible to run tests that use them async. Mox requires an explicit contract/behaviour and allows for per-process mocking, like Tesla's mock.
Mock is used ...Mock/Meck work by redefining modules and modifying the global state, making it impossible to run tests that use them async. Mox requires an explicit contract/behaviour and allows for per-process mocking, like Tesla's mock.
Mock is used in at least these files:
```
test/pleroma/upload/filter/mogrify_test.exs
test/pleroma/upload/filter/mogrifun_test.exs
test/pleroma/workers/receiver_worker_test.exs
test/pleroma/user/backup_test.exs
test/pleroma/application_requirements_test.exs
test/pleroma/object/fetcher_test.exs
test/pleroma/user_relationship_test.exs
test/pleroma/web/activity_pub/relay_test.exs
test/pleroma/web/admin_api/controllers/media_proxy_cache_controller_test.exs
test/pleroma/web/activity_pub/side_effects_test.exs
test/pleroma/web/admin_api/controllers/user_controller_test.exs
test/pleroma/web/activity_pub/publisher_test.exs
test/pleroma/web/activity_pub/activity_pub_test.exs
test/pleroma/web/activity_pub/transmogrifier_test.exs
test/pleroma/web/activity_pub/mrf/media_proxy_warming_policy_test.exs
test/pleroma/web/activity_pub/transmogrifier/note_handling_test.exs
test/pleroma/web/activity_pub/transmogrifier/follow_handling_test.exs
test/pleroma/web/federator_test.exs
test/pleroma/activity/ir/topics_test.exs
test/pleroma/web/media_proxy/invalidation_test.exs
test/pleroma/web/twitter_api/util_controller_test.exs
test/pleroma/web/plugs/admin_secret_authentication_plug_test.exs
test/pleroma/web/plugs/plug_helper_test.exs
test/pleroma/web/plugs/http_signature_plug_test.exs
test/pleroma/web/plugs/o_auth_scopes_plug_test.exs
test/pleroma/web/media_proxy/media_proxy_controller_test.exs
test/pleroma/web/plugs/frontend_static_plug_test.exs
test/pleroma/web/o_auth/ldap_authorization_test.exs
test/pleroma/web/pleroma_api/controllers/emoji_file_controller_test.exs
test/pleroma/web/common_api_test.exs
test/pleroma/web/pleroma_api/controllers/user_import_controller_test.exs
test/pleroma/web/pleroma_api/controllers/emoji_pack_controller_test.exs
test/pleroma/web/mastodon_api/controllers/search_controller_test.exs
test/pleroma/web/mastodon_api/controllers/filter_controller_test.exs
test/pleroma/web/mastodon_api/update_credentials_test.exs
test/pleroma/notification_test.exs
test/pleroma/signature_test.exs
test/pleroma/uploaders/s3_test.exs
test/mix/tasks/pleroma/uploads_test.exs
test/mix/tasks/pleroma/user_test.exs
```https://git.pleroma.social/pleroma/pleroma/-/issues/3213After running `mix deps.unlock --unused` to clean up the mix.lock file, tests...2024-02-06T05:44:35ZlainAfter running `mix deps.unlock --unused` to clean up the mix.lock file, tests reliable fail for me in non-obvious waysEncountered while working on https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3967. Maybe the deps are different between the test and dev environment?Encountered while working on https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3967. Maybe the deps are different between the test and dev environment?https://git.pleroma.social/pleroma/pleroma/-/issues/3212only_safe query parameter for nsfw free timelines, option to default for unau...2024-02-06T05:44:56Zplebonly_safe query parameter for nsfw free timelines, option to default for unauthenticated userssaw this requested, figured to write it up at least partly
rewrite restrict_media in lib/pleroma/web/activity_pub/activity_pub.ex fetch_activities_query
to a case statement and include only_safe via a similar query
```
defp restrict_m...saw this requested, figured to write it up at least partly
rewrite restrict_media in lib/pleroma/web/activity_pub/activity_pub.ex fetch_activities_query
to a case statement and include only_safe via a similar query
```
defp restrict_media(query, %{} = opts) do
case opts do
%{only_media: true} ->
from(
[activity, object] in query,
where: fragment("(?)->>'type' = 'Create'", activity.data),
where: fragment("(?)->'attachment' <> '[]'", object.data)
)
%{only_safe: true} ->
from(
[activity, object] in query,
where: fragment("(?)->>'type' = 'Create'", activity.data),
where: fragment("(?)->'sensitive' <> 'true'", object.data),
where: fragment("(?)->'attachment' = '[]'", object.data)
)
_ ->
query
end
end
```
an option to force it for users not logged in was tacked on, but i'm not sure on the place to deal with that, adding a :media Config to `restrict_unauthenticated` is clear, but not which code path it should apply tohttps://git.pleroma.social/pleroma/pleroma/-/issues/3211Pleroma.Instances.Instance is missing a `on_replace: :update`2024-02-06T05:45:36ZplebPleroma.Instances.Instance is missing a `on_replace: :update`iex(pleroma@declin)1\> Pleroma.Instances.Instance.get_or_update_metadata(URI.parse("https://lain.com"))
a test case for the update part is missing, and a call to get_or_update_metadata to actually populate it
<details>
<summary>
\*\* ...iex(pleroma@declin)1\> Pleroma.Instances.Instance.get_or_update_metadata(URI.parse("https://lain.com"))
a test case for the update part is missing, and a call to get_or_update_metadata to actually populate it
<details>
<summary>
\*\* (RuntimeError) you are attempting to change relation :metadata of Pleroma.Instances.Instance but the \`:on_replace\` option of this relation is set to \`:raise\`.
</summary>
By default it is not possible to replace or delete embeds and associations during \`cast\`. Therefore Ecto requires the parameters given to \`cast\` to have IDs matching the data currently associated to Pleroma.Instances.Instance. Failing to do so results in this error message.
If you want to replace data or automatically delete any data not sent to `cast`, please set the appropriate `:on_replace` option when defining the relation. The docs for `Ecto.Changeset` covers the supported options in the "Associations, embeds and on replace" section.
However, if you don't want to allow data to be replaced or deleted, only updated, make sure that:
* If you are attempting to update an existing entry, you are including the entry primary key (ID) in the data.
* If you have a relationship with many children, all children must be given on update.
</details>
the only thing probably using this functionality in the wild is https://256.lt/mrf/software_policy.ex which tries to use both incompatible implementations
plz fixhttps://git.pleroma.social/pleroma/pleroma/-/issues/3210Remove/disable the built-in emoji2024-02-06T05:47:13ZpiggoRemove/disable the built-in emojiI wanted to hide the three emoji that come by default with pleroma.
The diff below worked, but I now have dirty git, it doesn't look right.
- Why are they there? Just for unit tests?
- blank.png makes sense for emoji graphics, but the...I wanted to hide the three emoji that come by default with pleroma.
The diff below worked, but I now have dirty git, it doesn't look right.
- Why are they there? Just for unit tests?
- blank.png makes sense for emoji graphics, but the other two?
- Is there a more proper way to remove them?
```diff
diff --git a/config/emoji.txt b/config/emoji.txt
index 52b714ee5..8b1378917 100644
--- a/config/emoji.txt
+++ b/config/emoji.txt
@@ -1,3 +1 @@
-firefox, /emoji/Firefox.gif, Gif,Fun
-blank, /emoji/blank.png, Fun
-dinosaur, /emoji/dino walking.gif, Gif
+
diff --git a/priv/static/emoji/Firefox.gif b/priv/static/emoji/Firefox.gif
deleted file mode 100644
index 81561d94b..000000000
Binary files a/priv/static/emoji/Firefox.gif and /dev/null differ
diff --git a/priv/static/emoji/blank.png b/priv/static/emoji/blank.png
deleted file mode 100644
index 8f50fa023..000000000
Binary files a/priv/static/emoji/blank.png and /dev/null differ
diff --git a/priv/static/emoji/dino walking.gif b/priv/static/emoji/dino walking.gif
deleted file mode 100644
index 694a541e7..000000000
Binary files a/priv/static/emoji/dino walking.gif and /dev/null differ
```https://git.pleroma.social/pleroma/pleroma/-/issues/3206500 on inbox delivery of federated reply2024-02-06T05:39:41Zsnarfed500 on inbox delivery of federated replyHi all! I build and run https://fed.brid.gy/ . I've been working on an interop issue with Pleroma for a while on and off: when I deliver a reply to a Pleroma inbox, I get a 500 back with response body `"error"`. Background in https://git...Hi all! I build and run https://fed.brid.gy/ . I've been working on an interop issue with Pleroma for a while on and off: when I deliver a reply to a Pleroma inbox, I get a 500 back with response body `"error"`. Background in https://github.com/snarfed/bridgy-fed/issues/12 , details below. Maybe related to #2884? Not sure. Thanks in advance for looking, and for maintaining Pleroma!
The latest instance of this was delivering the activity below to https://sironi.tk/users/luca/inbox . sironi.tk evidently runs Pleroma 2.5.5, which I know is older than your latest 2.6.0 release. I'm happy to test against 2.6.0 if you want to point me to an instance running it!
```
2023-11-08 14:23:57.450 UTC
POST https://sironi.tk/users/luca/inbox
[HTTP Signature headers for keyId https://fed.brid.gy/snarfed.org#key ]
```
```json
{
"id": "https://fed.brid.gy/r/https://snarfed.org/2023-11-08_sironi-tk#bridgy-fed-create-c",
"actor": "https://fed.brid.gy/snarfed.org",
"published": "2023-11-08T14:09:50.134166+00:00",
"@context": "https://www.w3.org/ns/activitystreams",
"type": "Create",
"object": {
"published": "2023-11-08T06:09:44-08:00",
"content": "<a class=\"u-in-reply-to\" href=\"https://sironi.tk/notice/AbansIUFY43IrYaFMG\"></a>\n<div class=\"e-content\">\nThank you for the offer! I wouldn\u2019t worry about it right now though. The sandbox isn\u2019t really intended for normal users, and I still have tons to do before I run out of my own testing anyway. I appreciate the idea though!\n</div>",
"url": "https://fed.brid.gy/r/https://snarfed.org/2023-11-08_sironi-tk",
"id": "https://fed.brid.gy/r/https://snarfed.org/2023-11-08_sironi-tk",
"type": "Note",
"attributedTo": "https://fed.brid.gy/snarfed.org",
"inReplyTo": "https://sironi.tk/objects/72418a30-4a04-49a8-bde8-083dee651f8a",
"cc": [
"https://sironi.tk/users/luca",
"https://fed.brid.gy/snarfed.org",
"https://www.w3.org/ns/activitystreams#Public",
"https://venera.social/profile/activitypubblueskybridge",
"https://sironi.tk/users/luca/followers"
],
"contentMap": {
"en": "<a class=\"u-in-reply-to\" href=\"https://sironi.tk/notice/AbansIUFY43IrYaFMG\"></a>\n<div class=\"e-content\">\nThank you for the offer! I wouldn\u2019t worry about it right now though. The sandbox isn\u2019t really intended for normal users, and I still have tons to do before I run out of my own testing anyway. I appreciate the idea though!\n</div>"
},
"tag": [{
"type": "Mention",
"href": "https://sironi.tk/users/luca"
}],
"to": ["https://www.w3.org/ns/activitystreams#Public"]
},
"to": ["https://www.w3.org/ns/activitystreams#Public"]
}
```https://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/3202AGEN PERMAINAN JUDI BOLA SLOT ONLINE TERBAIK DI INDONESIA2023-10-15T21:34:19Zulli annaAGEN PERMAINAN JUDI BOLA SLOT ONLINE TERBAIK DI INDONESIASlot online merupakan permainan judi online terpopuler saat ini yang dapat diakses oleh seluruh para pemain dengan menggunakan sebuah media yaitu handphone maupun komputer. Seluruh orang dapat memainkan permainan judi online ini kapanpun...Slot online merupakan permainan judi online terpopuler saat ini yang dapat diakses oleh seluruh para pemain dengan menggunakan sebuah media yaitu handphone maupun komputer. Seluruh orang dapat memainkan permainan judi online ini kapanpun dan di mana saja. Tentunya permainan slot online memiliki karakter tema yang berbeda beda yang akan membuat seluruh para pemain menjadi tidak akan bosan untuk bermain [slot online](https://git.pleroma.social/pleroma/pleroma/-/issues/3202). Jika para pemain berhasil memperoleh kemenangan, para pemain tersebut akan memperoleh sebuah hadiah yang sangat banyak dan tentunya hadiah tersebut dapat di klaim secara langsung oleh para pemain tersebut.
Tentunya memperoleh sebuah kemenangan bukanlah hal mudah karena semua orang wajib memiliki berbagai bocoran yang dapat membantu untuk memperoleh sebuah kemenangan dengan mudah. Jika ingin memperoleh sebuah bocoran yang sangat akurat diwajibkan untuk bermain di dalam situs terpercaya seperti pada situs terpercaya kami yaitu situs [Sbobet88](https://eranmendel.com/) slot dana terpercaya. Seluruh para pemain akan memperoleh sebuah kemenangan dengan mudah jika bermain di dalam situs terpercaya kami. Berbagai permainan yang ada dapat di mainkan seluruhnya dengan sepuasnya.
Jika sudah bergabung dengan situs [slot mpo](https://www.glowsantamonica.org/) terpercaya kami tersebut akan mendapatkan banyak bocoran yang sangat akurat dan juga mendapatkan informasi lengkap, tentunya informasi tersebut dapat membantu seluruh para pemain untuk memperoleh sebuah kemenangan dengan mudah. Maka itu jika anda ingin memperoleh sebuah kemenangan dengan mudah segera bergabung dengan situs dana slot mpo terpercaya kami sekarang juga.
Seluruh para pemain hanya membutuhkan modal yang terjangkau untuk dapat bermain di dalam situs terpercaya kami, hanya dengan modal yang sangat terjangakau tersebut seluruh para pemain dapat bermain permainan [slot online](https://faminegenocide.com/) sesuka hati anda.
Seluruh para pemain hanya membutuhkan modal yang terjangkau untuk dapat bermain di dalam situs terpercaya kami, hanya dengan modal yang sangat terjangakau tersebut seluruh para pemain dapat bermain permainan slot online sesuka hati anda. Maka itu jika ingin bermain dengan modal yang murah dapat bermain di dalam situs [slot dana](https://www.mybindi.com/) terpercaya.
Banyak informasi terakurat yang ada di dalam situs terpercaya kami, segera kunjungi situs terpercaya kami melalui link berikut ini:
[https://mysentimentexactlee.com/](https://mysentimentexactlee.com/)
[https://bijou-cinemas.com/](https://bijou-cinemas.com/)https://git.pleroma.social/pleroma/pleroma/-/issues/3201Jenis Game Situs Slot Dana Judi Mpo Slot Gacor Terpercaya2023-10-02T02:21:32ZGhost UserJenis Game Situs Slot Dana Judi Mpo Slot Gacor Terpercaya[Slot deposit dana](https://www.mybindi.com/) yang merupakan platform gaming kasino terbaik di Indonesia ini memiliki banyak keunggulan menarik, antara lain kemampuan terbaik dan terlengkap untuk menyetor uang ke dana judi Pulsa Telkomse...[Slot deposit dana](https://www.mybindi.com/) yang merupakan platform gaming kasino terbaik di Indonesia ini memiliki banyak keunggulan menarik, antara lain kemampuan terbaik dan terlengkap untuk menyetor uang ke dana judi Pulsa Telkomsel tanpa potongan selain itu. Memperkenalkan beberapa game slot Gacor terbaru yang sangat menghibur dengan kemenangan maxwin jackpot tertinggi dengan live RTP besar dari berbagai provider populer.
Tidak hanya menyediakan berbagai macam permainan slot online dari [kumpulan situs mpo terpercaya](https://amoralweb.com/), pemain juga dapat mencoba permainan judi online lainnya seperti live casino online, taruhan togel online nomor, pasaran website permainan sbobet88 dan permainan lainnya. Bonus dapat diterima setiap hari dengan uang asli, menjadikan pengalaman bermain game lebih menyenangkan dan menguntungkan.
Inilah saat yang tepat untuk memenangkan jackpot terbesar di situs game online terpercaya dengan hadiah maxwin terbesar. Kumpulan link deposit MPO terbaru memberikan pemain kesempatan untuk merasakan permainan [slot gacor](https://faminegenocide.com/) yang belum pernah ada sebelumnya, lebih mudah dimainkan dan lebih mudah dimenangkan. Mesin slot online memang menjadi fokus para pecinta mesin slot gacor di Indonesia.
Tentunya setiap situs deposit [slot dana](https://bijou-cinemas.com/) di Indonesia selalu menawarkan kemenangan maksimal di situs MPO terbaru, menerima berbagai jenis pembayaran slot deposit taruhan global. Banyak mesin slot menyetor uang tanpa potongan. Menyediakan layanan deposit terlengkap seperti transfer antar semua bank lokal, deposit melalui Dana, Ovo, Gopay, Linkaja dan deposit pulsa tanpa potongan.
Bocoran game slot online lengkap lainnya seperti Jam Slot Gacor pada pasaran taruhan bola terbaru di [Sbobet88](https://eranmendel.com/) nampaknya mudah dimenangkan dengan pengalaman bermain yang seru, disertai dengan bonus-bonus terbaru, [jackpot maxwin](https://git.pleroma.social/pleroma/pleroma/-/issues/3201) terbesar memberikan peluang menang paling menarik. jackpot terbesar, karena kami selalu mengutamakan pelayanan. Cara terbaik memanjakan pemain slot di Indonesia. http://www.qianhailaw.cn/slot-deposit-dana/https://git.pleroma.social/pleroma/pleroma/-/issues/3200Situs Slot Gacor Link Mpo Deposit 5000 Termurah2023-10-02T02:21:39ZGhost UserSitus Slot Gacor Link Mpo Deposit 5000 TermurahKumpulan mpo bonus jackpot terkini dari situs [judi online indoclub](https://helpfreetheearth.com/) menawarkan bermacam opsi game slot yang gampang dimenangkan dengan minimun deposit pada slot gunakan dana sampai jumlah dini terendah, me...Kumpulan mpo bonus jackpot terkini dari situs [judi online indoclub](https://helpfreetheearth.com/) menawarkan bermacam opsi game slot yang gampang dimenangkan dengan minimun deposit pada slot gunakan dana sampai jumlah dini terendah, menjanjikan kemenangan gampang dalam game slot di lini Maxwin dengan kemenangan optimal tanpa potongan. Lumayan dengan memakai 1 akun permainan, pemain telah dapat memainkan seluruh permainan di link MPO terkini.
Dengan proses registrasi yang kilat serta tata cara pembayaran [slot deposit dana](https://manutdzone.com/) yang lengkap, situs game slot online membenarkan data pemain 100% terlindungi lewat sistem mutahir yang terenkripsi secara otomatis sehingga tidak gampang ditransfer ke orang lain yang tidak bertanggung jawab. Menawarkan bermacam opsi game slot online dengan mutu gameplay yang gampang dimengerti, apalagi buat pendatang baru sekalipun.
Kumpulan mesin slot gacor dari link permainan online Indoclub menawarkan 5000 mesin slot duit asli paling murah dengan sistem pembayaran terkini memakai aplikasi Dana. Slot deposit mpo kumpulan [slot gacor](https://git.pleroma.social/pleroma/pleroma/-/issues/3200) terkini saat ini telah sangat populer sebab teruji menawarkan jackpot Maxwin terbanyak buat taruhan judi online berbayar penuh.
Dengan bermain di seluruh situs indoclub, pemain tidak butuh lagi meragukan kehandalannya, mereka sangat mencermati mutu game serta penyedia game casino online Deposit bagus online menawarkan dana game online duit asli terbaik, menjamin game lebih menjanjikan kemenangan dengan pembayaran terbaik di serangkaian situs [MPO terbaru](https://agg668.com/) terpercaya.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/3194Pleroma should not promote OTP <version>+ at documentation2023-12-16T01:03:41ZWalter CoolPleroma should not promote OTP <version>+ at documentationHi,
Current changes on latest stable release are not enough to run OTP25 or OTP26 due [ssl_verify_fun](https://github.com/deadtrickster/ssl_verify_fun.erl/issues/29) and [ecto](https://github.com/elixir-ecto/ecto/issues/4132)
Develop a...Hi,
Current changes on latest stable release are not enough to run OTP25 or OTP26 due [ssl_verify_fun](https://github.com/deadtrickster/ssl_verify_fun.erl/issues/29) and [ecto](https://github.com/elixir-ecto/ecto/issues/4132)
Develop already contains the latest fixes at mix.lock file, and should work fine. Ton of warnings at build time, but fine.
In other hand, current documentation states OTP 22.2+ https://git.pleroma.social/pleroma/pleroma/-/blob/develop/docs/installation/generic_dependencies.include
Is it possible to define a minor and major version instead? Current stable branch works fine with OTP 24. Otherwise people will have problems installing latest releases from Erlang since they break lot of stuff.