pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2019-01-13T21:09:11Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/512Pagination/partial loading for follows/followers2019-01-13T21:09:11ZShpuld ShpludsonPagination/partial loading for follows/followersOpening Lain's soykaf account KILLS the browser because of thousands of accounts and their info it fetches and processes. Frontend will also need to support this.Opening Lain's soykaf account KILLS the browser because of thousands of accounts and their info it fetches and processes. Frontend will also need to support this.https://git.pleroma.social/pleroma/pleroma/-/issues/474MRF hellthread mitigation2018-12-23T11:28:45ZkaniiniMRF hellthread mitigationImplement an MRF filter to kill hellthreads. Should have a customizable mention threshold.
Use the JSON mentions instead of parsing the HTML mentions to ensure that all mentions are counted.
If the number of mentions exceeds the thres...Implement an MRF filter to kill hellthreads. Should have a customizable mention threshold.
Use the JSON mentions instead of parsing the HTML mentions to ensure that all mentions are counted.
If the number of mentions exceeds the threshold, discard the message as spam.https://git.pleroma.social/pleroma/pleroma/-/issues/395Figure out a way to make domain.com/user urls work2018-12-18T15:26:03ZfeldFigure out a way to make domain.com/user urls workMastodon has the domain.com/@user domains, but the @ is a rather unfamiliar part of a domain name. GNU Social has always had the domain.com/user urls, but that involves restricting usernames and reserving some special routes, as well as ...Mastodon has the domain.com/@user domains, but the @ is a rather unfamiliar part of a domain name. GNU Social has always had the domain.com/user urls, but that involves restricting usernames and reserving some special routes, as well as maybe invalidating existing names later once we need a new 'special route' (e.g. 'settings').
One solution would be to put all the pleroma routes under domain.com/p/..., so we'd only need to reserve the 'p' username (which is illegal anyway). This would make it possible to use all other routes for usernames.https://git.pleroma.social/pleroma/pleroma/-/issues/354Move all http interactions to Tesla2018-12-09T09:33:31ZlainMove all http interactions to TeslaSee https://github.com/teamon/tesla.
This makes it easy to mock requests, switch http backends and overall make things easier to use / change.See https://github.com/teamon/tesla.
This makes it easy to mock requests, switch http backends and overall make things easier to use / change.https://git.pleroma.social/pleroma/pleroma/-/issues/394Additional tags for users other than "admin"2018-12-07T18:25:41ZfeldAdditional tags for users other than "admin"The frontend issue for this is in https://git.pleroma.social/pleroma/pleroma-fe/issues/94
This would give us additional metadata like 'admin', 'moderator', etc.
Should probably be a new array type field and not just in 'info' because w...The frontend issue for this is in https://git.pleroma.social/pleroma/pleroma-fe/issues/94
This would give us additional metadata like 'admin', 'moderator', etc.
Should probably be a new array type field and not just in 'info' because we probably want to filter on it.
This will give us the ability to filter groups of users on a server as well as easily identify more information about a user on the local instance. This information is not relevant to any part of the federation.https://git.pleroma.social/pleroma/pleroma/-/issues/48When registration is disabled, registration option should be removed from the...2018-12-07T17:59:33ZHyper! (Stitch)When registration is disabled, registration option should be removed from the Web UIThis will help prevent DoS attacks and also prevent a few JS errors from occurring on the page.
I am not sure how to debug yet, but as I learn I will update this issue.This will help prevent DoS attacks and also prevent a few JS errors from occurring on the page.
I am not sure how to debug yet, but as I learn I will update this issue.https://git.pleroma.social/pleroma/pleroma/-/issues/51Extended Installation instructions2018-12-07T17:57:39ZHyper! (Stitch)Extended Installation instructionsNot an issue, but putting the file here for when @lambadalambda is ready to merge it (I can't merge request here atm.)
[README.md](/uploads/caa09c3a8cd937edc4d49e703d211419/README.md)Not an issue, but putting the file here for when @lambadalambda is ready to merge it (I can't merge request here atm.)
[README.md](/uploads/caa09c3a8cd937edc4d49e703d211419/README.md)https://git.pleroma.social/pleroma/pleroma/-/issues/43Adding point about generate new secret_key_base to readme2018-12-07T17:38:49ZfroschAdding point about generate new secret_key_base to readme@lambadalambda mentioned in matrix that it would be better to generate a new `secret_key_base` key with `mix phx.gen.secret`. I think this should be part of the README.@lambadalambda mentioned in matrix that it would be better to generate a new `secret_key_base` key with `mix phx.gen.secret`. I think this should be part of the README.https://git.pleroma.social/pleroma/pleroma/-/issues/65Object Storage backend2018-09-02T20:48:44ZTechnowixObject Storage backendIn order to sustain growth of instances, not having to do mega-replication of GBytes of assets and help #64, having to ability to use a object storage for attachments can be really interesting.
* [x] Use S3 api as an attachments storage...In order to sustain growth of instances, not having to do mega-replication of GBytes of assets and help #64, having to ability to use a object storage for attachments can be really interesting.
* [x] Use S3 api as an attachments storage
* [ ] Use Swift api as an attachments storage
* [ ] Use B2 api as an attachments storage
* [x] Option to have a pleroma-managed cache of attachments, like use 10 GByte for lastest attachments locally to not use the upload bandwidth (not cheap in general) of thoses services.https://git.pleroma.social/pleroma/pleroma/-/issues/127Update the URL regex to match non-HTTP schemes2018-08-16T15:41:18Zdtlunadtluna@riseup.netUpdate the URL regex to match non-HTTP schemeshttps://voluntaryism.club/notice/40964
![Снимок_экрана_2018-04-13_17-47-47](/uploads/76eca019c597dffbcb313031c963a363/Снимок_экрана_2018-04-13_17-47-47.png)
`@link_regex ~r/https?:\/\/[\w\.\/?=\-#\+%&@~\(\):]+[\w\/]/u` in `lib/pleroma/...https://voluntaryism.club/notice/40964
![Снимок_экрана_2018-04-13_17-47-47](/uploads/76eca019c597dffbcb313031c963a363/Снимок_экрана_2018-04-13_17-47-47.png)
`@link_regex ~r/https?:\/\/[\w\.\/?=\-#\+%&@~\(\):]+[\w\/]/u` in `lib/pleroma/formatter.ex:147` should be replaced with something better1.0HaelwennHaelwennhttps://git.pleroma.social/pleroma/pleroma/-/issues/229Feature request: Report media proxy feature in APIs2018-07-12T16:47:22ZHakaba HitoyoFeature request: Report media proxy feature in APIsApplication: http://distsn.org/pleroma-instances.html
Media proxy is an important feature for privacy or performance. I plan to display the media proxy flag in my list of Pleroma instances. Can you report media proxy feature in the APIs...Application: http://distsn.org/pleroma-instances.html
Media proxy is an important feature for privacy or performance. I plan to display the media proxy flag in my list of Pleroma instances. Can you report media proxy feature in the APIs, such as `/nodeinfo/2.0.json` or `/api/statusnet/config`?https://git.pleroma.social/pleroma/pleroma/-/issues/121Answering yourself should no show up your notifications2018-05-13T08:16:59ZGhost UserAnswering yourself should no show up your notificationsIt's my first issue so let me know if I'm doing something wrong.
When you're answering one of your own toots, it shows up in your notifications, whether your mention yourself or not.
![screenshot_07-04-2018_22-17-37](/uploads/1e5832aef...It's my first issue so let me know if I'm doing something wrong.
When you're answering one of your own toots, it shows up in your notifications, whether your mention yourself or not.
![screenshot_07-04-2018_22-17-37](/uploads/1e5832aefbd3d2d2c2d062daaa83a736/screenshot_07-04-2018_22-17-37.png)
*Here, my second toot answers my toot "I see"*
I think this is wrong and you should not see yourself there.1.0https://git.pleroma.social/pleroma/pleroma/-/issues/87New line trimming2018-04-29T02:24:27ZHyper! (Stitch)New line trimmingWe should convert sequential newlines into just one (or two) "\n" As I just tested with notice https://p2px.me/notice/190855 On Mastodon and GNUSocial/Friendica/SocialHome it displays in full down the column. This is bad as it can cause ...We should convert sequential newlines into just one (or two) "\n" As I just tested with notice https://p2px.me/notice/190855 On Mastodon and GNUSocial/Friendica/SocialHome it displays in full down the column. This is bad as it can cause disorientation to users trying to read a timeline.https://git.pleroma.social/pleroma/pleroma/-/issues/146Enable custom panel by default and have default content2018-04-21T08:05:39ZMorgan Bazalgettethe@howl.moeEnable custom panel by default and have default contentFor now, it just says "This is a Pleroma instance". I think it'd be useful to have it link to the PleromaFE / MastoFE (both, anticipating that the custom panel will also be shown on mastofe: mastofe#12), as well as a link to pleroma.soci...For now, it just says "This is a Pleroma instance". I think it'd be useful to have it link to the PleromaFE / MastoFE (both, anticipating that the custom panel will also be shown on mastofe: mastofe#12), as well as a link to pleroma.social.
This way we can implement #141, while giving admins control on the custom panel and whether to show or hide more 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.