pleroma issues
https://git.pleroma.social/pleroma/pleroma/-/issues
2019-07-22T02:49:35Z
https://git.pleroma.social/pleroma/pleroma/-/issues/1118
[Feature Request] A "Direct Replies" tab on the Interactions page
2019-07-22T02:49:35Z
Your New SJW Waifu
[Feature Request] A "Direct Replies" tab on the Interactions page
It'd be nice to have a tab that only showed direct replies and OP mentions in addition to all mentions. It would certainly make it easier to not miss someone asking for help or another conversation you have going when you're caught in a ...
It'd be nice to have a tab that only showed direct replies and OP mentions in addition to all mentions. It would certainly make it easier to not miss someone asking for help or another conversation you have going when you're caught in a hellthread. It'd also make checking for any replies you might have missed during the day a lot easier too.
https://git.pleroma.social/pleroma/pleroma/-/issues/1117
Following external Pleroma 1.0 users is broken
2019-07-29T16:28:21Z
Your New SJW Waifu
Following external Pleroma 1.0 users is broken
Following accounts on other Pleroma instances is broken (you gotta open profile on home instance and remote follow). Same for [other Pleroma instances that aren't up to date on `master` or running stable that try to follow users on my in...
Following accounts on other Pleroma instances is broken (you gotta open profile on home instance and remote follow). Same for [other Pleroma instances that aren't up to date on `master` or running stable that try to follow users on my instance](https://neckbeard.xyz/notice/9l4yqLhL2oQXFf93x2).
Mastodon seems unaffected tho ![yui_shrug](https://neckbeard.xyz/emoji/custom/yui_shrug.png)
https://git.pleroma.social/pleroma/pleroma/-/issues/1051
Remove Uploaders.Swift
2019-07-09T16:54:34Z
minibikini
Remove Uploaders.Swift
What do you think about removing Uploaders.Swift? It's been broken for months (#784) and nobody complained yet.
As a bonus, we'll be able to remove `httpoison` from dependencies, because nothing else depends on it.
What do you think about removing Uploaders.Swift? It's been broken for months (#784) and nobody complained yet.
As a bonus, we'll be able to remove `httpoison` from dependencies, because nothing else depends on it.
https://git.pleroma.social/pleroma/pleroma/-/issues/1002
Replace the default nginx 502 page
2020-05-04T09:42:36Z
rinpatch
rin+pleroma@patch.cx
Replace the default nginx 502 page
"502 error - nginx" does not tell much to the admin, instead we could replace it with a pleroma-styled page containing a short list of reasons why this might be happening and a link to the docs. Would also be a good use case for [pleroma...
"502 error - nginx" does not tell much to the admin, instead we could replace it with a pleroma-styled page containing a short list of reasons why this might be happening and a link to the docs. Would also be a good use case for [pleroma-fox-tan-shy.png](https://git.pleroma.social/pleroma/pleroma/blob/develop/priv/static/images/pleroma-fox-tan-shy.png)
https://git.pleroma.social/pleroma/pleroma/-/issues/944
Application blocklist
2019-07-10T14:44:45Z
kaniini
Application blocklist
We need to refuse to grant application credentials as well as retroactively revoke access to apps on a configurable blocklist. This is intended for blocking broken apps or apps which have unacceptable behaviour like Tootdon. The admin ...
We need to refuse to grant application credentials as well as retroactively revoke access to apps on a configurable blocklist. This is intended for blocking broken apps or apps which have unacceptable behaviour like Tootdon. The admin should be able to override the blocklist if they wish.
https://git.pleroma.social/pleroma/pleroma/-/issues/920
Do not fallback to index.html for /api/* routes
2019-05-22T04:05:42Z
rinpatch
rin+pleroma@patch.cx
Do not fallback to index.html for /api/* routes
This frequently confuses developers, instead we should just respond with `{"error": "Not implemented"}`
This frequently confuses developers, instead we should just respond with `{"error": "Not implemented"}`
Aaron Tinio
Aaron Tinio
https://git.pleroma.social/pleroma/pleroma/-/issues/875
Find ways to reduce resource usage, mostly RAM.
2020-04-28T10:29:09Z
lain
Find ways to reduce resource usage, mostly RAM.
Thoughts:
- Thread fetching is unbounded, can crash any amount of ram.
- We could have a guide for low-res pleroma installations, with tips to configure postgres etc
- We should figure out which parts of the application are actually res...
Thoughts:
- Thread fetching is unbounded, can crash any amount of ram.
- We could have a guide for low-res pleroma installations, with tips to configure postgres etc
- We should figure out which parts of the application are actually resource intensive.
https://git.pleroma.social/pleroma/pleroma/-/issues/860
ATOM feeds from hashtags
2019-11-30T22:08:45Z
xx
ATOM feeds from hashtags
in the same way that every user has their own public ATOM feed, an ATOM feed from a hashtag would be useful for "bookmarking" tags or otherwise working with posts given a hashtag
in the same way that every user has their own public ATOM feed, an ATOM feed from a hashtag would be useful for "bookmarking" tags or otherwise working with posts given a hashtag
https://git.pleroma.social/pleroma/pleroma/-/issues/770
Add emoji tags
2019-06-10T15:20:12Z
lain
Add emoji tags
Emojis right now can get a bit too much to display in a good way. We should make it possible to have 'tags' on emojis so they can be sorted by that in frontend applications. This would involve extending the Emoji entity (https://docs.joi...
Emojis right now can get a bit too much to display in a good way. We should make it possible to have 'tags' on emojis so they can be sorted by that in frontend applications. This would involve extending the Emoji entity (https://docs.joinmastodon.org/api/entities/#emoji) with a pleroma.tags property.
Alexander Strizhakov
Alexander Strizhakov
https://git.pleroma.social/pleroma/pleroma/-/issues/719
@erroruser@example.com is unsightly
2020-04-23T11:55:45Z
feld
@erroruser@example.com is unsightly
Instead of replacing tagged users in a reply that your instance has disabled/blocked/defederated with, can we just remove the mention entirely? Displaying `@erroruser@example.com` is kind of gross
Instead of replacing tagged users in a reply that your instance has disabled/blocked/defederated with, can we just remove the mention entirely? Displaying `@erroruser@example.com` is kind of gross
https://git.pleroma.social/pleroma/pleroma/-/issues/683
Add withMutes=1 option to MastoAPI post-returning endpoints
2019-02-28T10:22:20Z
HJ
Add withMutes=1 option to MastoAPI post-returning endpoints
The idea is so that if FE or client wants to, they can process muted statuses themselves. I.e. PleromaFE would collapse them with option of removing them completely. This would solve the discrepancy between MastoAPI/Clients "nuclear" mut...
The idea is so that if FE or client wants to, they can process muted statuses themselves. I.e. PleromaFE would collapse them with option of removing them completely. This would solve the discrepancy between MastoAPI/Clients "nuclear" mutes and PleromaFE/Qvitter "non-extrimist" mutes.
https://git.pleroma.social/pleroma/pleroma/-/issues/658
Actually delete things that are "deleted". Because CP.
2020-04-27T16:41:54Z
nepfag
Actually delete things that are "deleted". Because CP.
There's CP. I want it gone. I "deleted" the user but the CP is still there.
I don't care if it breaks some shitty threads. Things need to get deleted from the local disk if an admin wants it.
There's CP. I want it gone. I "deleted" the user but the CP is still there.
I don't care if it breaks some shitty threads. Things need to get deleted from the local disk if an admin wants it.
https://git.pleroma.social/pleroma/pleroma/-/issues/649
Pleroma can't follow either PixelFed or Writefreely instances
2019-02-25T13:26:07Z
Clément
Pleroma can't follow either PixelFed or Writefreely instances
Hello,
I am a Pleroma user since few months -on a public instance before, now on my own instance-, and I'm facing an issue when I want to follow accounts from PixelFed or Writefreely on my Pleroma instance: Even on auto-accepting accou...
Hello,
I am a Pleroma user since few months -on a public instance before, now on my own instance-, and I'm facing an issue when I want to follow accounts from PixelFed or Writefreely on my Pleroma instance: Even on auto-accepting accounts, Pleroma answers "Request sent!" when hitting the "Follow" button.
I tried follow these accounts on Mastodon and this works.
Thank you, ask me if you need more infos.
kaniini
kaniini
https://git.pleroma.social/pleroma/pleroma/-/issues/637
Error message when posting an MRF violating message
2021-02-09T07:07:29Z
nepfag
Error message when posting an MRF violating message
Currently, if a post violates a local MRF policy (such as HellThreadPolicy), it can't be posted and the FE just displays the error "{}".
A general "MRF violation: @ your admin" message would be more helpful.
Currently, if a post violates a local MRF policy (such as HellThreadPolicy), it can't be posted and the FE just displays the error "{}".
A general "MRF violation: @ your admin" message would be more helpful.
Karen Konou
Karen Konou
https://git.pleroma.social/pleroma/pleroma/-/issues/618
usernames consisting of integers link to the wrong user page
2019-04-14T17:25:29Z
wood cat
usernames consisting of integers link to the wrong user page
I have a user who registered as @1212@wetfish.space, when clicking their username you are instead taken to the page of the 1212th federated account on my instance instead of their user page. To prevent this in the future, integer usernam...
I have a user who registered as @1212@wetfish.space, when clicking their username you are instead taken to the page of the 1212th federated account on my instance instead of their user page. To prevent this in the future, integer usernames should not be considered valid when creating a new account.
https://git.pleroma.social/pleroma/pleroma/-/issues/593
Notification API Broken
2019-02-22T20:34:46Z
KmN
Notification API Broken
After an update to ```c57f37bd36702fa8865366fbfaea9ac3f28dfad3``` I'm getting the following errors in the logs and notifications don't work in the main Pleroma FE or Mastodon FE. I can post messages that show on other instances as well t...
After an update to ```c57f37bd36702fa8865366fbfaea9ac3f28dfad3``` I'm getting the following errors in the logs and notifications don't work in the main Pleroma FE or Mastodon FE. I can post messages that show on other instances as well tag users in posts but I don't see responses.
```
Request: GET /api/qvitter/statuses/notifications.json?count=20
** (exit) an exception was raised:
** (ArgumentError) argument error
:erlang.bit_size(nil)
(pleroma) lib/pleroma/web/mastodon_api/views/status_view.ex:192: Pleroma.Web.MastodonAPI.StatusView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/activity_view.ex:279: Pleroma.Web.TwitterAPI.ActivityView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/activity_view.ex:176: Pleroma.Web.TwitterAPI.ActivityView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/notification_view.ex:62: Pleroma.Web.TwitterAPI.NotificationView.render/2
(elixir) lib/enum.ex:1314: Enum."-map/2-lists^map/1-0-"/2
(elixir) lib/enum.ex:1314: Enum."-map/2-lists^map/1-0-"/2
(phoenix) lib/phoenix/view.ex:399: Phoenix.View.render_to_iodata/3
```
https://git.pleroma.social/pleroma/pleroma/-/issues/559
Swagger/OpenAPI IDL generation for all supported APIs
2020-04-14T22:46:08Z
kaniini
Swagger/OpenAPI IDL generation for all supported APIs
It would be nice to have OpenAPI IDL generation for supported APIs (OpenAPI was formerly called Swagger).
https://github.com/xerions/phoenix_swagger is an Elixir module which may help with this.
It would be nice to have OpenAPI IDL generation for supported APIs (OpenAPI was formerly called Swagger).
https://github.com/xerions/phoenix_swagger is an Elixir module which may help with this.
https://git.pleroma.social/pleroma/pleroma/-/issues/534
Retire broken servers
2019-02-01T09:14:41Z
lain
Retire broken servers
At the moment, Pleroma will always try to federate, even if a remote host hasn't been online for a while. With long-running instances, this can lead to a situation where a huge amount of servers that you are trying to send to are dead an...
At the moment, Pleroma will always try to federate, even if a remote host hasn't been online for a while. With long-running instances, this can lead to a situation where a huge amount of servers that you are trying to send to are dead and just slow down federation.
We should keep track of federation errors and not try federating to servers that have not have any successful federation for a while (4 weeks or so)
Ivan Tashkinov
Ivan Tashkinov
https://git.pleroma.social/pleroma/pleroma/-/issues/514
Media proxy: domain blacklist
2020-05-11T09:17:46Z
kaniini
Media proxy: domain blacklist
In some cases, it may be desirable to not have an instance's media in local cache. Accordingly, instead of caching for those instance's media domains, send a 302 instead.
In some cases, it may be desirable to not have an instance's media in local cache. Accordingly, instead of caching for those instance's media domains, send a 302 instead.
href
href@random.sh
href
href@random.sh
https://git.pleroma.social/pleroma/pleroma/-/issues/493
Insecure mode
2023-05-08T03:47:13Z
kaniini
Insecure mode
To facilitate migration from other fediverse software, we would like to be able to replay AP activities into Pleroma. This will of course be problematic because of the anti-spoofing protection and signature requirements. Thusly, it wou...
To facilitate migration from other fediverse software, we would like to be able to replay AP activities into Pleroma. This will of course be problematic because of the anti-spoofing protection and signature requirements. Thusly, it would be nice to have a mode which turns these security features off.
Insecure mode should be a special invocation of the Pleroma server instead of a config setting. Something like an environment variable should trigger it.
That would allow us to import data through replaying it. We should also have very noticeable warnings when the server is operating in Insecure mode and it should not attempt to federate in Insecure mode.
(in other words the only functionality that should be live is only the functionality needed to import the data. nothing more.)