pleroma-fe issueshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues2022-08-21T02:04:50Zhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/229Support for viewing lists2022-08-21T02:04:50ZsuccfemboiSupport for viewing listsOn mastofe or pinafore, one has the ability to create list in which it creates a timeline of users one has selected.On mastofe or pinafore, one has the ability to create list in which it creates a timeline of users one has selected.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/310PleromaFE moderation tools discussion2019-10-15T16:54:46ZfeldPleromaFE moderation tools discussionPleroma doesn't have any moderation tools in the UI yet except the "Delete" functionality as pictured below.
![E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09](/uploads/c1f8fce575055f96a727a9b3c8ea9e5e/E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09.jpeg)
I...Pleroma doesn't have any moderation tools in the UI yet except the "Delete" functionality as pictured below.
![E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09](/uploads/c1f8fce575055f96a727a9b3c8ea9e5e/E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09.jpeg)
I propose that we replace the delete button with some kind of context menu that exposes the following:
If moderator:
* Delete status
* Lock/Unlock account (local users)
* Activate/Deactivate account (remote users; effectively an instance-wide block)
If admin:
* Grant/Revoke moderator (local users)
* Grant/Revoke admin (local users)
* Delete account (local users)
Does this make sense? Let me know if I confused anythinghttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/101Add an emoji selector2019-09-26T05:28:00ZnormandyAdd an emoji selectorThis allows users to more easily see what kind of custom emojis exist on the instance.This allows users to more easily see what kind of custom emojis exist on the instance.feldfeldhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/86strange behaviour for notifications2018-12-02T11:21:02Zkatherinestrange behaviour for notificationsmaybe it's something to do with instance-specific race conditions, but old
notifications keep reappearing as new after having been previously marked
"Read". no idea what information might be helpful here (and maybe this is
really somethi...maybe it's something to do with instance-specific race conditions, but old
notifications keep reappearing as new after having been previously marked
"Read". no idea what information might be helpful here (and maybe this is
really something to do with the backend?), but one thing i've noticed, though,
that seems a bit reproduce-able:
1. open web client and log in
2. notification sidebar has nothing, or maybe one thing, in it
3. load own timeline, which contains a that was directed at me and that i've repeated
4. that post appears in the notifications sidebar as "unread"
![2018-1524369010](/uploads/cbfe0d5b4792c476ac087b61f9192ff8/2018-1524369010.png)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/481Remove "Mentions" TL?2019-07-29T16:26:21ZHJRemove "Mentions" TL?Should we do it? Do people use it in the age of working notifications?
I know I use it like once a year to find some post but I could live without it.Should we do it? Do people use it in the age of working notifications?
I know I use it like once a year to find some post but I could live without it.HJHJhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/121Feature Request: tag / hashtag search box2020-06-01T12:26:20ZpypperFeature Request: tag / hashtag search boxIt would be extra handy if there were a little `#` icon right beside the user search icon that was for searching hashtags. Similar behaviour, and just renders the `/tag/<input value>` page into the screen.
I'm currently typing in /tag/<...It would be extra handy if there were a little `#` icon right beside the user search icon that was for searching hashtags. Similar behaviour, and just renders the `/tag/<input value>` page into the screen.
I'm currently typing in /tag/<whatever topic> to see if there are any discussions going on.
Any interest in adding this?https://git.pleroma.social/pleroma/pleroma-fe/-/issues/260Searching posts by content2019-10-15T16:53:29ZsuccfemboiSearching posts by contentOn mastofe one can search for users and messages on the fediverse, but on Pleroma-fe one can't.On mastofe one can search for users and messages on the fediverse, but on Pleroma-fe one can't.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/70Log in / Log out in Pleroma FE is wonky2018-12-02T11:57:57ZlainLog in / Log out in Pleroma FE is wonkySwitch to token-based login.Switch to token-based login.0.9https://git.pleroma.social/pleroma/pleroma-fe/-/issues/711Scrolling Performance2020-12-01T11:33:49ZShpuld ShpludsonScrolling PerformanceCreating this issue based on !977 and the problems with it.
The problem:
the more you scroll, the more your timeline gets filled with content, DOM gets bloated, Vue has more work when updating the also bloated virtual dom, and the br...Creating this issue based on !977 and the problems with it.
The problem:
the more you scroll, the more your timeline gets filled with content, DOM gets bloated, Vue has more work when updating the also bloated virtual dom, and the browser has more work when updating the actual dom, as well as when doing the layout and all that stuff. I did some testing with modified code to confirm this, you can basically load thousands of statuses into memory of the application but only display ~100 of them, and the performance when scrolling doesn't really drop at any point, even with thousands of statuses. This is without cleaning up the application memory from old statuses, just the views only showing a smaller part of them. This completely confirms my guess that the performance issues do not come from memory, but excessive v-dom/dom.
Suggested fix:
Virtual scrolling, as you scroll the timeline keeps track of statuses not in view, needs to keep track of the edges of the hidden parts as well as the height of them. Only the visible statuses are rendered as statuses, and the hidden statuses on top/bottom just as a block with the height of the hidden statuses they represent. When you scroll up/down, the hidden statuses height is decreased/increased and the visible statuses slice moves accordingly. The only real issue with this is when you resize the window, the height of statuses can change and the stored heights of hidden statuses don't match to their real height anymore, however I believe this can be remedied by doing scroll offsets based on the old stored hidden height of a status and the actual current rendered height of it when the hidden statuses are turned into real ones.
Some requirements for the implementation:
- It should be something that we can enable without making it an option, as in it doesn't make the experience worse.
- Keeping track of visible statuses should be done in a way that doesn't get more expensive the more you have, which means you can't just have scroll listeners for each status, it won't go well with thousands of them.
- Needless to say, the solution shouldn't have to mess with the application state stored with vuex, it should be purely handled by view components.
- Scrolling both up and down shouldn't feel different even when status hiding/unhiding is being done, scrolling shouldn't be locked and it shouldn't jump in unintended ways.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/681Autocomplete for accounts should not split on the @2020-09-03T14:08:38ZfeldAutocomplete for accounts should not split on the @If you autocomplete for username@bikeshed.party at first the results are all for similar matches to `username` but then it starts providing only results for `bikeshed.party` after the `@` is entered. This is wrong and annoying.
Can we m...If you autocomplete for username@bikeshed.party at first the results are all for similar matches to `username` but then it starts providing only results for `bikeshed.party` after the `@` is entered. This is wrong and annoying.
Can we make searches for fully qualified user accounts use some different search logic?Shpuld ShpludsonShpuld Shpludsonhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/553Pinned posts cause profile timeline to skip into the past when scrolling2020-12-01T10:46:18ZkaniiniPinned posts cause profile timeline to skip into the past when scrolling1. Pin a post from a week ago.
2. Scroll through posts.
3. Suddenly you've jumped back a week, even though you have many posts newer than that.
This is probably fixed by not adding the pinned posts to the profile timeline twice.1. Pin a post from a week ago.
2. Scroll through posts.
3. Suddenly you've jumped back a week, even though you have many posts newer than that.
This is probably fixed by not adding the pinned posts to the profile timeline twice.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/353Can't clear avatar, profile banner or profile background2020-07-08T10:13:24ZMartin AshbyCan't clear avatar, profile banner or profile backgroundActual behaviour:
Once you have set any of the above in user settings, you can't unset them.
Desired behaviour:
I should be able to change my mind about having a profile banner or background.Actual behaviour:
Once you have set any of the above in user settings, you can't unset them.
Desired behaviour:
I should be able to change my mind about having a profile banner or background.Wyatt BennoWyatt Bennohttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/351Error message when posting an MRF violating message2019-02-12T19:54:36ZnepfagError message when posting an MRF violating messageCurrently, 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.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/348Display a warning when browser is too old or javascript is disabled2020-12-01T10:42:31ZorekixDisplay a warning when browser is too old or javascript is disabledSome people browse from old smartphones and Pleromafe doesn't open in them, there should be a warning and a suggestion to use Brutaldon in such cases.
See https://pl.smuglo.li/notice/9fjcPuTho55yVcNEtk for a caseSome people browse from old smartphones and Pleromafe doesn't open in them, there should be a warning and a suggestion to use Brutaldon in such cases.
See https://pl.smuglo.li/notice/9fjcPuTho55yVcNEtk for a caseTae HoonTae Hoonhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/194Clicking on an image doesn't open a pop up2019-02-05T23:18:58ZpaviClicking on an image doesn't open a pop upMaybe this is not the expected behaviour but opening a new window/tab of an image after clicking on it is like so 90s UI.
Was that the expected behaviour? I do block JS sometimes and I am not sure if its a bug or the feature hasn't been...Maybe this is not the expected behaviour but opening a new window/tab of an image after clicking on it is like so 90s UI.
Was that the expected behaviour? I do block JS sometimes and I am not sure if its a bug or the feature hasn't been implemented.
This is a bit surprising as I read the UI was written in Vue.JS which is pretty modern UI.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/133No visual feedback is given after sending a follow request2018-12-14T17:33:13ZniaNo visual feedback is given after sending a follow requesthttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/122Ability to ~filter notifications2018-08-31T04:10:26ZHaelwennAbility to ~filter notificationsI guess there should be something like a option table with the type of notifications(replies, boosts, …) and the actions(sound, desktop notification, show it in the column, …).
Several people have asked for it via posts, but I’m not see...I guess there should be something like a option table with the type of notifications(replies, boosts, …) and the actions(sound, desktop notification, show it in the column, …).
Several people have asked for it via posts, but I’m not seeing any tickets about it.HJHJhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/117Add timestamps to chat messages2020-06-01T12:36:41ZnormandyAdd timestamps to chat messagesHard to know when a message was posted otherwise.Hard to know when a message was posted otherwise.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/102Request: Display 'bot' or similar on bot accounts2020-12-01T10:19:31ZAndrew ZahRequest: Display 'bot' or similar on bot accountsBasically a mirror of this new functionality in mastodon 2.4:
https://github.com/tootsuite/mastodon/pull/7391Basically a mirror of this new functionality in mastodon 2.4:
https://github.com/tootsuite/mastodon/pull/7391https://git.pleroma.social/pleroma/pleroma-fe/-/issues/93Things that aren't links that should be2018-12-13T18:56:25ZPipirupirupirupipirupiThings that aren't links that should be![UI](/uploads/5878594120b61df8ce9c8a8cd0da6277/UI.PNG)
* ["Statuses Following Followers" on the left panel should link to the same things that the text on the right panel does so the user can access those pages from anywhere on the inst...![UI](/uploads/5878594120b61df8ce9c8a8cd0da6277/UI.PNG)
* ["Statuses Following Followers" on the left panel should link to the same things that the text on the right panel does so the user can access those pages from anywhere on the instance.]
* [Clicking display names should link to the user profile preview, like the avatar. Usernames should have an @ in front of them to distinguish from display names and follow convention.]
* [@usernames from remote users should link to their instance profile.]
* [Browser treats your avatar in your profile as a link, but it doesn't do anything. Suggestion: link to highest quality version of the avatar image like GNUsocial and Twitter.]