pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2023-06-27T18:49:45Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3119Send a 413 when a user bio goes beyond character limit2023-06-27T18:49:45ZDuponinSend a 413 when a user bio goes beyond character limitWhen a user updates their bio out of character limit boundary, backend is sending a 403 error code and `{"error":"Invalid request"}`.
The correct error code is 413 "Payload Too Large" and answer should be `{"error":"Payload Too Large"}`....When a user updates their bio out of character limit boundary, backend is sending a 403 error code and `{"error":"Invalid request"}`.
The correct error code is 413 "Payload Too Large" and answer should be `{"error":"Payload Too Large"}`.
Relates to #3053.tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/3065OAuth scopes should have (translatable) descriptions2023-05-17T18:51:27ZtusooaOAuth scopes should have (translatable) descriptionsCurrently our web UI only gives out the name of the scope, without ever explaining what it does. It should, instead, have an explanation.Currently our web UI only gives out the name of the scope, without ever explaining what it does. It should, instead, have an explanation.https://git.pleroma.social/pleroma/pleroma/-/issues/3024Backup: Better representation of status2023-06-27T12:08:13ZtusooaBackup: Better representation of statusWe should have notation of "not processed," "in progress," "success," and "failed."We should have notation of "not processed," "in progress," "success," and "failed."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/2931BBS: Add translation support2023-04-26T12:19:48ZHaelwennBBS: Add translation supporthttps://git.pleroma.social/pleroma/pleroma/-/issues/2775Foreign emoji denylist2023-07-07T16:27:33ZpiggoForeign emoji denylistI wish there was a way to ban certain foreign emoji.
Specifically to ban animated ones like hyper bun that's insane flashing with 2 frames, but that will be difficult without a media proxy stripping the animation.
I found it can be do...I wish there was a way to ban certain foreign emoji.
Specifically to ban animated ones like hyper bun that's insane flashing with 2 frames, but that will be difficult without a media proxy stripping the animation.
I found it can be done with the Replace MRF, but its kinda janky and I think you can't have the colons in the search text.
![Screenshot_20211019_102726](/uploads/5b11e143acad8b7bce70c23f6f1730db/Screenshot_20211019_102726.png)tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/2733Support green checkmark (rel="me") in profile fields2024-03-08T00:52:12ZAlex GleasonSupport green checkmark (rel="me") in profile fieldsI did not know Pleroma already had the ability to scrape links for `rel="me"` introduced by !813. With this, it should be fairly easy to support the green checkmark for custom profile fields like Mastodon does. All we're missing is `veri...I did not know Pleroma already had the ability to scrape links for `rel="me"` introduced by !813. With this, it should be fairly easy to support the green checkmark for custom profile fields like Mastodon does. All we're missing is `verified_at`, which shouldn't even require schema changes to add.
```js
"fields": [
{
"name": "Website",
"value": "<a href=\"https://trwnh.com\" rel=\"me nofollow noopener noreferrer\" target=\"_blank\"><span class=\"invisible\">https://</span><span class=\"\">trwnh.com</span><span class=\"invisible\"></span></a>",
"verified_at": "2019-08-29T04:14:55.571+00:00"
},
{
"name": "Sponsor",
"value": "<a href=\"https://liberapay.com/at\" rel=\"me nofollow noopener noreferrer\" target=\"_blank\"><span class=\"invisible\">https://</span><span class=\"\">liberapay.com/at</span><span class=\"invisible\"></span></a>",
"verified_at": "2019-11-15T10:06:15.557+00:00"
},
{
"name": "Fan of:",
"value": "Punk-rock and post-hardcore (Circa Survive, letlive., La Dispute, THE FEVER 333)Manga (Yu-Gi-Oh!, One Piece, JoJo's Bizarre Adventure, Death Note, Shaman King)Platformers and RPGs (Banjo-Kazooie, Boktai, Final Fantasy Crystal Chronicles)",
"verified_at": null
},
{
"name": "Main topics:",
"value": "systemic analysis, design patterns, anticapitalism, info/tech freedom, theory and philosophy, and otherwise being a genuine and decent wholesome poster. i'm just here to hang out and talk to cool people!",
"verified_at": null
}
]
```https://git.pleroma.social/pleroma/pleroma/-/issues/2187MRF to deny "empty" replies2023-10-04T21:03:32ZfeldMRF to deny "empty" repliesI've had multiple experiences of accidentally sending empty replies (just mentions). We should be able to match this and deny the post with an MRF.I've had multiple experiences of accidentally sending empty replies (just mentions). We should be able to match this and deny the post with an MRF.https://git.pleroma.social/pleroma/pleroma/-/issues/2104Ability to force unfollow followers2023-10-04T21:04:11ZAlex GleasonAbility to force unfollow followersWe'd like to build some features similar to the follower management Mastodon offers into Soapbox FE:
![Screenshot_from_2020-08-31_14-52-16](/uploads/2f761cd1c3207c3b43c6c2db8c8d85a3/Screenshot_from_2020-08-31_14-52-16.png)
The most imp...We'd like to build some features similar to the follower management Mastodon offers into Soapbox FE:
![Screenshot_from_2020-08-31_14-52-16](/uploads/2f761cd1c3207c3b43c6c2db8c8d85a3/Screenshot_from_2020-08-31_14-52-16.png)
The most important feature we want from it is the ability to remove followers. The same can be achieved by block+unblock, but would be better to have an endpoint for it.https://git.pleroma.social/pleroma/pleroma/-/issues/1081Extend timeline APIs to filter out replies2020-04-24T16:32:15ZfeldExtend timeline APIs to filter out repliesRight now if you enable the status filtering in the FE it's done 100% in the FE.
![image](/uploads/d4492d8fc8b2b2beabbdb545ec3e45f9/image.png)
This means when I scroll to the bottom of my feed the refresh can pull less than 20 statuse...Right now if you enable the status filtering in the FE it's done 100% in the FE.
![image](/uploads/d4492d8fc8b2b2beabbdb545ec3e45f9/image.png)
This means when I scroll to the bottom of my feed the refresh can pull less than 20 statuses to read because a large number of the statuses in the next batch were replies. A good UX would have the backend actually provide 20 parent statuses.Alexander StrizhakovAlexander Strizhakovhttps://git.pleroma.social/pleroma/pleroma/-/issues/1025Consider using Dialyzer2019-11-28T19:41:50Zrinpatchrin+pleroma@patch.cxConsider using DialyzerFrom https://erlang.org/doc/man/dialyzer.html
> Dialyzer is a static analysis tool that identifies software discrepancies, such as definite type errors, code that has become dead or unreachable because of programming error, and unnecessa...From https://erlang.org/doc/man/dialyzer.html
> Dialyzer is a static analysis tool that identifies software discrepancies, such as definite type errors, code that has become dead or unreachable because of programming error, and unnecessary tests, in single Erlang modules or entire (sets of) applications.
There is a mix task for using it in Elixir https://github.com/jeremyjh/dialyxir
This seems useful and I've seen quite a lot of Elixir projects using it, but I have not worked with it personally so would be interested to hear if it's actually necessary.https://git.pleroma.social/pleroma/pleroma/-/issues/946New upvote/downvote feature and karma2019-05-31T22:49:49ZxxNew upvote/downvote feature and karmaGab is getting a feature with its Activitypub (fork?) that allows its users to uvpote and downvote posts and earn karma. After GabFE is ported to Pleroma, will Pleroma also keep track of voting and karma? Maybe we can even begin earning...Gab is getting a feature with its Activitypub (fork?) that allows its users to uvpote and downvote posts and earn karma. After GabFE is ported to Pleroma, will Pleroma also keep track of voting and karma? Maybe we can even begin earning karma and upvotes before Gab comes here, to reward us for supporting Pleroma during the pre-release cycle?
I am assuming that gab will only allow post ranking (upvote/downvote) to be local, to prevent botnets stealing votes to artificially influence post popularity. Not sure that there is a "right way" to federate rankings. Maybe having a toggle for local score, host score, network score. But that is messy and way overkill.
This all being said, a very clever way to handle post voting (upvote/downvote reacts) is to tie it into a greater react system, including favorite & emoji react. You can very easily calculate score in various ways or just ironically include a useless upvote/downvote (aka, like and dislike) react.
Look here for suggested "best" sort: http://www.evanmiller.org/how-not-to-sort-by-average-rating.html (*same as reddit's*)
> PROBLEM: You are a web programmer. You have users. Your users rate stuff on your site. You want to put the highest-rated stuff at the top and lowest-rated at the bottom. You need some sort of “score” to sort by.https://git.pleroma.social/pleroma/pleroma/-/issues/875Find ways to reduce resource usage, mostly RAM.2020-04-28T10:29:09ZlainFind 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/839Feature request: XMPP Gateway?2019-06-10T22:17:01Zstr8f0rwardFeature request: XMPP Gateway?In my opinion, Pleroma misses the ability to post from anywhere without going to web interface or using a separate client application. It could be more convenient if you were able to send and receive posts from Pleroma just like any othe...In my opinion, Pleroma misses the ability to post from anywhere without going to web interface or using a separate client application. It could be more convenient if you were able to send and receive posts from Pleroma just like any other messages from different people.
This can be solved by implementing an XMPP/Jabber gateway bot which could be used for that. You should be able to create posts, subscribe to replies or users and receive other posts, etc.
There have been examples of centralized services which implement the same approach with success. Examples are [Juick](https://juick.com) (is kind of defunct, [usage reference](https://web.archive.org/web/20130929041755/http://juick.info/функционал)) and [BnW](https://bnw.im/) ([source code](https://github.com/stiletto/bnw/), [usage reference](http://hive.blasux.ru/u/Stiletto/BnW)). Both references are not in English, but using online translators will help.
It would be very nice if the same features were present in Pleroma, making it more comfortable to use for some of the users.https://git.pleroma.social/pleroma/pleroma/-/issues/837MediaProxy: Domain whitelist2019-04-25T23:23:28Zrinpatchrin+pleroma@patch.cxMediaProxy: Domain whitelistA configurable list of domains for which `MediaProxy.url/1` will return the original url, instead of a proxy url even when MediaProxy is enabled. Could be useful to ease the load on low power instances by not proxying trusted instancesA configurable list of domains for which `MediaProxy.url/1` will return the original url, instead of a proxy url even when MediaProxy is enabled. Could be useful to ease the load on low power instances by not proxying trusted instancesfeldfeldhttps://git.pleroma.social/pleroma/pleroma/-/issues/833expose installed emoji packs and their licenses/copyright data in nodeinfo2019-09-23T18:20:09Zkaniiniexpose installed emoji packs and their licenses/copyright data in nodeinfoalso delete the no longer relevant creative commons license filealso delete the no longer relevant creative commons license filehttps://git.pleroma.social/pleroma/pleroma/-/issues/827Suggestion: When opening a Pleroma website with Javascript turned off, show a...2019-08-17T18:44:45ZYuval LangerSuggestion: When opening a Pleroma website with Javascript turned off, show a message rather than a blank page.Suggestion: When opening a Pleroma website with Javascript turned off, show a message like "Hey, Bozo, turn on your browser's Javascript!", rather than a blank page.
<3 Thank you <3Suggestion: When opening a Pleroma website with Javascript turned off, show a message like "Hey, Bozo, turn on your browser's Javascript!", rather than a blank page.
<3 Thank you <3Sergey SuprunenkoSergey Suprunenkohttps://git.pleroma.social/pleroma/pleroma/-/issues/810Support Mastodon-Style metadata fields2019-12-19T20:59:57ZlainSupport Mastodon-Style metadata fieldsWe already display the data of Mastodon users by going through the source data (see `Pleroma.Web.MastodonAPI.AccountView`). We should support it for local users, too, because it can be useful for rel=me.
Needed for #805.
Steps:
- Add ...We already display the data of Mastodon users by going through the source data (see `Pleroma.Web.MastodonAPI.AccountView`). We should support it for local users, too, because it can be useful for rel=me.
Needed for #805.
Steps:
- Add 'meta_fields' field to User.Info
- Refactor current code to use meta_fields instead of using the source data directly
- Parse existing and incoming user data into those fields
- Modify our MastodonAPI to add support for creating and updating those fields.
Documentation:
https://docs.joinmastodon.org/api/rest/accounts/#patch-api-v1-accounts-update-credentials
https://docs.joinmastodon.org/api/entities/#accountAlexander StrizhakovAlexander Strizhakovhttps://git.pleroma.social/pleroma/pleroma/-/issues/802Addressable lists (announcement system)2019-07-18T07:12:00ZlainAddressable lists (announcement system)It would be useful to directly address a list of people. Glitch makes this possible by having an option to directly mention all the users in a list at once. This is rather dirty and leaks all the users in the list to every user on it. It...It would be useful to directly address a list of people. Glitch makes this possible by having an option to directly mention all the users in a list at once. This is rather dirty and leaks all the users in the list to every user on it. It would be nice to have something like this:
1. Make it possible to directly address a list (by which I mean our internal, per-user lists feature)
2. Have some fallback way to address them for legacy clients (like @user for user, open to suggestions)
3. When addressing the list, add al the users in the list to the BCC field of the activity.
The main difficulty is handling the BCC/BTO field throughout pleroma. It's defined in AP, but we haven't supported it yet.minibikiniminibikinihttps://git.pleroma.social/pleroma/pleroma/-/issues/800Can't renew access_token with refresh_token2019-05-19T14:16:07ZNicolas ConstantCan't renew access_token with refresh_tokenI'm trying to renew an access_token using the refresh_token.
Sending a POST request on /oauth/token?`grant_type=`refresh_token&`client_id=`my_client_id&`client_secret=`my_client_secret&`refresh_token=`my_refresh_token gives me an Inter...I'm trying to renew an access_token using the refresh_token.
Sending a POST request on /oauth/token?`grant_type=`refresh_token&`client_id=`my_client_id&`client_secret=`my_client_secret&`refresh_token=`my_refresh_token gives me an Internal server error.
Does Pleroma need another/different parameter?MaksimMaksim