pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2019-01-18T14:34:28Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/176Incorrect avatar2019-01-18T14:34:28ZOmarIncorrect avatarWhat's going on? Pleroma does not show me some avatars, I did the verification and it happens that the address that Pleroma points to is not correct, I guess they changed the avatar and Pleroma has not updated it
One example:
https:...What's going on? Pleroma does not show me some avatars, I did the verification and it happens that the address that Pleroma points to is not correct, I guess they changed the avatar and Pleroma has not updated it
One example:
https://mstdn.mx/system/accounts/avatars/000/019/945/original/7b4ed6994cc57a55b647cfb52747b64e.jpeg (In Pleroma)
https://mstdn.mx/system/accounts/avatars/000/019/945/original/845d66b2bf4c42adef4fe6f786cc0dc1.png (Real avatar)https://git.pleroma.social/pleroma/pleroma/-/issues/164Repeats by unknowns should not show up on your home timeline2020-06-10T10:21:35ZDominik V. SalonenRepeats by unknowns should not show up on your home timelineWhen someone repeats a post. It typically pops up again on your home timeline as long as you follow the person who repeated it. That's fine, I think most people are happy with that behavior.
However, on Pleroma all repeat actions show u...When someone repeats a post. It typically pops up again on your home timeline as long as you follow the person who repeated it. That's fine, I think most people are happy with that behavior.
However, on Pleroma all repeat actions show up, even if you do not follow the person who repeated it. This is extremely annoying and unpractical. If a user's post gathers enough attention, they essentially end up drowning their timeline with their own post: [Related post](https://weeaboo.space/notice/75542)1.0kaniinikaniinihttps://git.pleroma.social/pleroma/pleroma/-/issues/144Feature request: Message relay2018-08-27T08:29:28ZMichaelFeature request: Message relayEspecially small servers suffer the problem that they don't have much public content. For Diaspora this problem was solved with the so called "social relay". Every participating server sends the whole public content of their users additi...Especially small servers suffer the problem that they don't have much public content. For Diaspora this problem was solved with the so called "social relay". Every participating server sends the whole public content of their users additionally to a relay server that distributes it to the other servers.
To limit the amount of messages, servers can subscribe either to all the content or only to selected tags. See for example the list of one of my servers: https://squeet.me/.well-known/x-social-relay
It would be great if Pleroma could do something similar. Possibly using the same endpoints, but using AP as a protocol.https://git.pleroma.social/pleroma/pleroma/-/issues/138Incorrect behaviour for Link header2020-04-22T13:56:58ZMorgan Bazalgettethe@howl.moeIncorrect behaviour for Link headerWhen a user has no more statuses, on `/api/v1/accounts/:id/statuses` no `Link` header is given. Mastodon, instead, gives only a `link: <https://mstdn.io/api/v1/accounts/96921/statuses?exclude_replies=false&since_id=99740919846633556>; re...When a user has no more statuses, on `/api/v1/accounts/:id/statuses` no `Link` header is given. Mastodon, instead, gives only a `link: <https://mstdn.io/api/v1/accounts/96921/statuses?exclude_replies=false&since_id=99740919846633556>; rel="prev"` header, where since_id is the ID of the first post returned. I'd take the guess that this is what causes pleroma/mastofe#9 to happen.minibikiniminibikinihttps://git.pleroma.social/pleroma/pleroma/-/issues/114Activation + Reset token emails2019-07-11T14:51:34ZlainActivation + Reset token emailsThere's already a reset token mechanism available by mix task. This needs to be exposed in an API.
Things to do
- [x] add an SMTP library
- [x] Add an option for users to invite other users (configurable in the config)
- Add the fronte...There's already a reset token mechanism available by mix task. This needs to be exposed in an API.
Things to do
- [x] add an SMTP library
- [x] Add an option for users to invite other users (configurable in the config)
- Add the frontend part for this to PleromaFE (for Admins and Users) — to be implemented in https://git.pleroma.social/pleroma/pleroma-fe/issues/213
It would also be nice to have an option to require an 'activation' email before a user can start using the site.1.0Ivan TashkinovIvan Tashkinovhttps://git.pleroma.social/pleroma/pleroma/-/issues/108Invite system2019-01-31T16:04:32ZnormandyInvite systemIt would be nice to easily add users to an instance that has closed registrations.It would be nice to easily add users to an instance that has closed registrations.1.0HJHJhttps://git.pleroma.social/pleroma/pleroma/-/issues/104unlisted posts showing on the fediverse TL2022-08-12T01:32:22Zcodlunlisted posts showing on the fediverse TLposts from mastodon marked as unlisted show up on the "Whole known network" timeline, which goes against the whole point of unlistedposts from mastodon marked as unlisted show up on the "Whole known network" timeline, which goes against the whole point of unlistedhttps://git.pleroma.social/pleroma/pleroma/-/issues/76Embed status previews (like a client-side implementation of Twitter's quoted ...2019-01-20T11:25:59ZUSB K9Embed status previews (like a client-side implementation of Twitter's quoted tweet feature)Just something useful when folks write a post that links to one or more posts in the fediverse. The post URL and then load whatever the content part the server returns for that particular status. Could also be extended to cover other O...Just something useful when folks write a post that links to one or more posts in the fediverse. The post URL and then load whatever the content part the server returns for that particular status. Could also be extended to cover other OEmbed site links.https://git.pleroma.social/pleroma/pleroma/-/issues/64Proxy and caching of attachments2018-02-12T10:20:45ZTechnowixProxy and caching of attachmentsTo be more friendly with others instances, and to provide full privacy for our users.
* [ ] Option to proxy remote attachments to server them from
* [ ] Allow keep them for a given time / forever.
* [ ] Process them to save space / band...To be more friendly with others instances, and to provide full privacy for our users.
* [ ] Option to proxy remote attachments to server them from
* [ ] Allow keep them for a given time / forever.
* [ ] Process them to save space / bandwidth if we want.https://git.pleroma.social/pleroma/pleroma/-/issues/54Remote profile fetching for registered users only2017-11-07T18:58:25ZwittiRemote profile fetching for registered users onlyMaybe its a good idea to prevent unregistered users from fetching new remote profiles? Otherwise they could flood an instance with requests.Maybe its a good idea to prevent unregistered users from fetching new remote profiles? Otherwise they could flood an instance with requests.https://git.pleroma.social/pleroma/pleroma/-/issues/3018Unified streaming endpoint2023-10-15T21:35:33ZtusooaUnified streaming endpointhttps://docs.joinmastodon.org/methods/streaming/#websocket
Here, send to server subscribe events to start receiving updates for those events.https://docs.joinmastodon.org/methods/streaming/#websocket
Here, send to server subscribe events to start receiving updates for those events.https://git.pleroma.social/pleroma/pleroma/-/issues/3006Can't access translation site2022-11-30T21:18:19ZAhmad DakhlallahCan't access translation siteHello,
Me and others that are trying to join the translation site "translate.pleroma.social" are unable to login to the site.
I do use my Pleroma username and password, and I do get to the page where it asked me to authorize access to ...Hello,
Me and others that are trying to join the translation site "translate.pleroma.social" are unable to login to the site.
I do use my Pleroma username and password, and I do get to the page where it asked me to authorize access to my account but when I click "Authorize", it just redirect me back to "translate.pleroma.social" without signing me in.
![image](/uploads/9c4e0cae9386668ac60112d7bbba7098/image.png)
Also, regarding translation, how can I implement my own translation without first asking for it to be implemented using "translate.pleroma.social"?
How can I compile the JSON file into JS file without braking it?
I'm looking into tested it directly and I can't wait for Pleroma to implement every change that I might need to do.
Thank you!https://git.pleroma.social/pleroma/pleroma/-/issues/2952Allow "Note" to have "Link" tags2023-05-17T19:04:53Zsilverpill silverpillAllow "Note" to have "Link" tags### Environment
* Installation type (OTP or From Source): From Source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.4.3
* Elixir version (`elixir -v` for from source installations, N/A for OTP): 1....### Environment
* Installation type (OTP or From Source): From Source
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.4.3
* Elixir version (`elixir -v` for from source installations, N/A for OTP): 1.10.3
* Operating system: Debian
* PostgreSQL version (`psql -V`): 13.8
### Bug description
(This problem was previously reported in the discussion on quotes: https://git.pleroma.social/pleroma/pleroma/-/issues/2783#note_95257)
Pleroma fails to process `Note` with `Link` tag, and incoming activity is silently dropped. Here's an example of a link tag:
```json
{
"type": "Note",
"tag": [
{
"name": "RE: https://example.org/objects/1",
"type": "Link",
"href": "https://example.org/objects/1",
"mediaType": "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\""
}
],
...
}
```
This type of tag is permitted by AP/AS specs, so I think Pleroma should accept the activity (and ignore the tag if it doesn't know what to do with it).
The fix was recently proposed to Rebased (Pleroma fork): https://gitlab.com/soapbox-pub/rebased/-/merge_requests/185/diffs?commit_id=0cd15c997c70ee2303c3c04e938b8c3de39a436c. Perhaps the same fix can be applied to Pleroma?https://git.pleroma.social/pleroma/pleroma/-/issues/2859Support Update for Note and Question2022-09-03T02:16:46Za1batrossa1ba.omarov@gmail.comSupport Update for Note and QuestionA new Mastodon version with support for post editing was released today. There is no API for that yet, but the foundation is there.
I don't know how Pleroma reacts to Update activities right now, but at bare minimum, the user should be ...A new Mastodon version with support for post editing was released today. There is no API for that yet, but the foundation is there.
I don't know how Pleroma reacts to Update activities right now, but at bare minimum, the user should be notified about an edited post through streaming and notifications.https://git.pleroma.social/pleroma/pleroma/-/issues/2816Mentions are returned in the wrong order2024-03-07T02:19:17ZAlex GleasonMentions are returned in the wrong orderMentions returned by the API don't always match the order they appear in the text.
![Screenshot_from_2022-01-11_08-58-20](/uploads/3974dd75d00ad63fcafbe328277a9e9d/Screenshot_from_2022-01-11_08-58-20.png)
To partially solve this proble...Mentions returned by the API don't always match the order they appear in the text.
![Screenshot_from_2022-01-11_08-58-20](/uploads/3974dd75d00ad63fcafbe328277a9e9d/Screenshot_from_2022-01-11_08-58-20.png)
To partially solve this problem, I made the client sort the mentions so `in_reply_to_account_id` is the first mention.
![Screenshot_from_2022-01-11_09-00-00](/uploads/dce8dca65a1a2b90e314686883e1348d/Screenshot_from_2022-01-11_09-00-00.png)
In a long list of mentions, they'll get jumbled up, and as the thread goes on continue getting jumbled more and more.
I think it happens during federation, because locally the mentions are always in the right order, but checking the same status on a remote server shows them in a different order.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/2746User cannot delete their account2021-12-15T21:26:47ZtusooaUser cannot delete their account<!--
### 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 (docker)
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.4.0
* 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`): psql (PostgreSQL) 13.3 (at https://lily.kazv.moe/infra/postgres/-/blob/servant/Dockerfile )
### Bug description
When I try to delete account in Pleroma-FE, it reports "Invalid credentials." I am sure that I entered the password correctly.https://git.pleroma.social/pleroma/pleroma/-/issues/2710Pleroma Fails to Compile on OpenBSD 6.92021-10-06T05:58:53ZGhost UserPleroma Fails to Compile on OpenBSD 6.9### Environment
* Installation type: From Source
* Pleroma version: Stable Branch
* Elixir version: Elixir 1.11.4 (compiled with Erlang/OTP 21)
* Operating system: OpenBSD 6.9
* PostgreSQL version: psql (PostgreSQL) 13.2
### Bug descr...### Environment
* Installation type: From Source
* Pleroma version: Stable Branch
* Elixir version: Elixir 1.11.4 (compiled with Erlang/OTP 21)
* Operating system: OpenBSD 6.9
* PostgreSQL version: psql (PostgreSQL) 13.2
### Bug description
Following installation instructions on: https://docs.pleroma.social/backend/installation/openbsd_en/
Pleroma fails to compile with the following error:
```
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
Compiling 535 files (.ex)
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
warning: :crypt.crypt/2 is undefined (module :crypt is not available or is yet to be defined)
lib/pleroma/web/plugs/authentication_plug.ex:42: Pleroma.Web.Plugs.AuthenticationPlug.checkpw/2
03:54:08.779 [warn] The on_load function for module crypt returned:
{:error, {:load, 'Library load-call unsuccessful (1).'}}
Compilation failed due to warnings while using the --warnings-as-errors option
```
This is the output from running `mix deps.clean crypt; mix deps.get crypt; mix deps.compile crypt`:
```
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
* Cleaning crypt
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
* Getting crypt (https://git.pleroma.social/pleroma/elixir-libraries/crypt.git - cf2aa3f11632e8b0634810a15b3e612c7526f6a3)
remote: Enumerating objects: 267, done.
remote: Counting objects: 0% (1/267)
[snipped]
remote: Counting objects: 100% (267/267), done.
remote: Compressing objects: 0% (1/132)
[snipped]
remote: Compressing objects: 100% (132/132), done.
remote: Total 267 (delta 112), reused 267 (delta 112), pack-reused 0
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
accept 0.3.5
base62 1.2.1
bbcode_pleroma 0.2.0
bcrypt_elixir 2.2.0
benchee 1.0.1
bunt 0.2.0
cachex 3.2.0
calendar 1.0.0
castore 0.1.7
combine 0.10.0
comeonin 5.3.1
connection 1.1.0
cors_plug 2.0.2
cowboy 2.8.0
cowboy_telemetry 0.3.0
cowlib 2.9.1
credo 1.4.1
custom_base 0.2.1
db_connection 2.3.1
decimal 2.0.0
deep_merge 1.0.0
earmark 1.4.3
earmark_parser 1.4.10
ecto 3.4.6
ecto_enum 1.4.0
ecto_sql 3.4.5
elixir_make 0.6.2
esshd 0.1.1
eternal 1.2.1
ex_aws 2.1.6
ex_aws_s3 2.0.2
ex_const 0.2.4
ex_doc 0.22.2
ex_machina 2.4.0
ex_syslogger 1.5.2
excoveralls 0.12.3
fast_html 2.0.4
fast_sanitize 0.2.2
flake_id 0.1.0
floki 0.27.0
gen_smtp 0.15.0
gettext 0.18.0
html_entities 0.5.1
http_signatures 0.1.0
httpoison 1.6.2
inet_cidr 1.0.4
jason 1.2.2
joken 2.2.0
jose 1.10.1
jumper 1.0.1
linkify 0.5.0
makeup 1.0.3
makeup_elixir 0.14.1
meck 0.8.13
mime 1.4.0
mock 0.3.5
mogrify 0.7.4
mox 1.0.0
nimble_parsec 0.6.0
nimble_pool 0.1.0
oban 2.3.4
phoenix 1.5.6
phoenix_ecto 4.2.1
phoenix_html 2.14.2
phoenix_pubsub 2.0.0
phoenix_swoosh 0.3.2
plug 1.10.4
plug_cowboy 2.4.0
plug_crypto 1.2.0
plug_static_index_html 1.0.0
poison 3.1.0
poolboy 1.5.2
postgrex 0.15.7
pot 0.11.0
prometheus 4.6.0
prometheus_ecto 1.4.3
prometheus_phoenix 1.3.0
prometheus_plugs 1.1.5
quack 0.1.1
ranch 1.7.1
recon 2.5.1
sleeplocks 1.1.1
sweet_xml 0.6.6
swoosh 1.0.6
syslog 1.1.0
telemetry 0.4.2
tesla 1.4.0
�[33m timex 3.6.2 RETIRED!�[0m
�[33m (other) handling of non-olson timezones was broken�[0m
trailing_format_plug 0.0.7
tzdata 1.0.4
ueberauth 0.6.3
unsafe 1.0.1
web_push_encryption 0.3.0
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
gmake: Entering directory '/home/_pleroma/pleroma/deps/crypt/c_src'
cc -fPIC -I /usr/local/lib/erlang21/erts-10.2/include/ -c -o /home/_pleroma/pleroma/deps/crypt/c_src/crypt.o /home/_pleroma/pleroma/deps/crypt/c_src/crypt.c
/home/_pleroma/pleroma/deps/crypt/c_src/crypt.c:53:9: warning: using crypt [-W#pragma-messages]
#pragma message "using crypt"
^
1 warning generated.
cc /home/_pleroma/pleroma/deps/crypt/c_src/crypt.o -shared -o /home/_pleroma/pleroma/deps/crypt/c_src/../priv/crypt.so
gmake: Leaving directory '/home/_pleroma/pleroma/deps/crypt/c_src'
===> Analyzing applications...
===> Compiling crypt
```HaelwennHaelwennhttps://git.pleroma.social/pleroma/pleroma/-/issues/2625Deprecation and removal of MastoFE?2021-12-17T03:38:13ZHaelwennDeprecation and removal of MastoFE?I posted <https://git.pleroma.social/pleroma/mastofe/-/issues/96> about it's situation, I think I could display a warning that mastofe is deprecated in 2.3.x and then we should remove it from our repos (in 2.4.0).I posted <https://git.pleroma.social/pleroma/mastofe/-/issues/96> about it's situation, I think I could display a warning that mastofe is deprecated in 2.3.x and then we should remove it from our repos (in 2.4.0).https://git.pleroma.social/pleroma/pleroma/-/issues/2476Developer Menu?2021-02-03T21:47:13ZBane BiddixDeveloper Menu?A developer menu so people can create their apps in a more easier way without having to use stuff like https://tinysubversions.com/notes/mastodon-bot/?A developer menu so people can create their apps in a more easier way without having to use stuff like https://tinysubversions.com/notes/mastodon-bot/?