mastofe issueshttps://git.pleroma.social/pleroma/mastofe/-/issues2021-04-16T23:30:50Zhttps://git.pleroma.social/pleroma/mastofe/-/issues/96MastoFE lack of maintainance since 2020-09-232021-04-16T23:30:50ZHaelwennMastoFE lack of maintainance since 2020-09-23Since around 2018-04 I took over maintenance of MastoFE as the previous maintainer was missing in action, there has been few occasional contributors since but no one that apparently could be a co-maintainer.
I switched it to Glitch-soc...Since around 2018-04 I took over maintenance of MastoFE as the previous maintainer was missing in action, there has been few occasional contributors since but no one that apparently could be a co-maintainer.
I switched it to Glitch-soc to ease collaboration and reduce our modifications, sadly the maintainer of Glitch-soc gradually changed from "friendly/welcoming to pleroma" to "fuck pleroma", which basically mean that MastoFE is now unmaintained, as I'd rather not have to somehow manage to revert back to Genuine/Vanilla Mastodon.
And as pleroma continues there is also a gigantic gap forming between what a true pleroma-frontend would feature and what a mastodon frontend patched for some neat features could feature (no settings, no chats, no emoji reactions, …).
For users this means that you should switch to another frontend ([List of alternative frontends on Pleroma Documentation](https://docs.pleroma.social/backend/clients/#alternative-web-interfaces)), for the ones that want to keep multiple-columns I would recommend [Sengi](https://nicolasconstant.github.io/sengi/), which also allows to use multiple accounts.
(I will archive this repo on 2021-05-01, this also means closing issues/comments/…)https://git.pleroma.social/pleroma/mastofe/-/issues/95Posting a status to a list causes mastoFE to crash2021-04-16T21:10:33ZSean TilleyPosting a status to a list causes mastoFE to crashHey there!
I'm in the process of building [Sporadic*](https://git.feneas.org/deadsuperhero/sporadic): a Diaspora-clone frontend for Pleroma! One of the features I was interested in supporting was the recreation of Aspects, which is basi...Hey there!
I'm in the process of building [Sporadic*](https://git.feneas.org/deadsuperhero/sporadic): a Diaspora-clone frontend for Pleroma! One of the features I was interested in supporting was the recreation of Aspects, which is basically a way to post a private status to a specified group of people.
I was trying this out for the first time today, and while it seems to have gone through, mastoFE immediately freaked out.
Here's what was in the payload:
```
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="status"
Testing a private status sent to List 6 only. No one else should be able to see this.
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="visibility"
list:6
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="content_type"
text/markdown
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="in_reply_to_id"
undefined
-----------------------------34318860801516679447438874830--
```
and the stacktrace as well:
https://pastebin.com/XLb2SkXf
Attached is also the JSON of the resulting status, for posterity.
[list-status.json](/uploads/f2eb586adb2eba4550d4ba370b5e394c/list-status.json)https://git.pleroma.social/pleroma/mastofe/-/issues/94Unable to showing media in mastoFE.2021-02-10T10:12:04ZSnowUnable to showing media in mastoFE.Pleroma 2.2.2.
This is a same post.
And I found out only see this bug while the post with poll+media.
![7452000406](/uploads/cba3bf32e74b9185f20b92d2cd0eba91/7452000406.png)
![7d802071ac](/uploads/afe38d6225d49a363c3e16ca26389879/7d80...Pleroma 2.2.2.
This is a same post.
And I found out only see this bug while the post with poll+media.
![7452000406](/uploads/cba3bf32e74b9185f20b92d2cd0eba91/7452000406.png)
![7d802071ac](/uploads/afe38d6225d49a363c3e16ca26389879/7d802071ac.png)https://git.pleroma.social/pleroma/mastofe/-/issues/93No mascot seems to make the sidebar go white2021-01-20T04:09:47ZHaelwennNo mascot seems to make the sidebar go whitereported by xerz on IRC.reported by xerz on IRC.https://git.pleroma.social/pleroma/mastofe/-/issues/92Missing mascot on mastofe2021-01-16T17:06:50ZSnowMissing mascot on mastofe![XOdV15Zdaj](/uploads/76d50e25464ef77cf91123849bf885d4/XOdV15Zdaj.png)
![chrome_DbRDnyuCZM](/uploads/74633d01a0383354e3b1ddcc2d701df3/chrome_DbRDnyuCZM.png)
I set that before.![XOdV15Zdaj](/uploads/76d50e25464ef77cf91123849bf885d4/XOdV15Zdaj.png)
![chrome_DbRDnyuCZM](/uploads/74633d01a0383354e3b1ddcc2d701df3/chrome_DbRDnyuCZM.png)
I set that before.https://git.pleroma.social/pleroma/mastofe/-/issues/91Suggestion - enhancement for AWI mode, with 2 panels filling wide displays. R...2020-12-16T22:51:26ZYann R. G.Suggestion - enhancement for AWI mode, with 2 panels filling wide displays. Reader and Writer friendly. [also posted at Glitch-Social Git]### Pitch
A proposal for consideration -- that Advanced Web Interface could better support wide screen displays, for users interested in using **two panels of information**. (_as opposed to the typical narrow, numerous ones à la TweetDe...### Pitch
A proposal for consideration -- that Advanced Web Interface could better support wide screen displays, for users interested in using **two panels of information**. (_as opposed to the typical narrow, numerous ones à la TweetDeck_).
### Motivation
The Advanced Web Interface in Mastodon was closely modeled on the TweetDeck app. It works well for users accustomed to narrow panels and a fast moving display of Feeds in each. Eugen R recognizes this as his model for AWI.
This was never attractive to me. I have tweaked settings and been able to improve the screen usage in my system substantially.
At first, this was _highly dependant on the instance's Themes_ -- two that I have accounts on (Todon.nl and Qoto.org) had improved their AWI themes, and setting up with two panes worked fairly well.
Screenshot 1 : the AWI display at Qoto.org, using Dark Theme wide display :
![](https://i.postimg.cc/L8vGf5F8/Qoto-AWI-2panels-800x413p.jpg)
In typical day to day use, I tend to have the Local Feed in the left panel, and a Notifications on the right panel. So far so good.
------
### Improving AWI via an add-on :
But -- I managed to get it better, enhanced via use of [a Firefox add-on called **Collapsed Mastodon**](https://addons.mozilla.org/en-US/firefox/addon/collapsed-mastodon/).
With Collapsed Mastodon installed and the instance added to its configuration, the 2 pane view at Qoto now displays this :
Screenshot 2 : AWI theme, enhanced by Collapsed Mastodon, at Qoto.org; Dark Theme, wide display :
![](https://i.postimg.cc/P5hPJ3dk/Qoto-AWI-2-P-Collapsed-800x413p.jpg)
The leftmost area where the Toot Editor is typically located has been collapsed. The information panels fill the width of the screen almost completely. (This would also happen if AWI was being used in 3 or 4 Columns mode)
-----
### Replying ? New Toots? How is it done?
I like and enjoy working in this mode - it has some good points for it :
* the client uses the full width of the display.
* not only removing the mostly empty space in the leftmost part (bellow the Toot editor box)
* but adding a Reply Toot Editor below any post on the screen
This last feature is so neat that I wish the mainstream AWI would incorporate it. On the standard AWI mode, *the left space is sacrificed to keep an inactive Toot Editor, idle until needed*.
The Collapsed Mastodon does that, instead, *by opening a Reply Editor below any post on the screen, when you click the Reply arrow*.
Screenshot 3 : Reply Toot Editor box below one of the on-screen toots. Taken at a Glitch instance.
![](https://i.postimg.cc/rmWkST9Z/Koyu-AWI-Masto-Look-800x413p.jpg)
-----
### Advantages and Benefits ?
This Toot Reply Editor is immediately below the post being replied to, so you can keep an eye and refer to it easily. It also starts at *a decent vertical size*, and with the *fairly large width of this panel*, it *can contain a lot of text*.
The editor will expand as long as needed, so it’s a boon for anyone writing long replies; no visual stress or cramped, narrow editor to type in.
A new Toot all together will pop up a smaller sized Edit box in the Left side Panel - near the Pencil Tool icon. It is smaller than the full column width, but still a nicer writing space that the typical in mastodon.
![](https://i.postimg.cc/pr26pMcF/New-Toot-Editor-232x196p.jpg)
My main instance allows *5 thousand characters* maximum allowed toot size -- *so we tend to enjoy freedom and post Long Form frequently*.
I had prepared [a detailed topic in our Discourse Forum](https://discourse.qoto.org/t/mastodon-screen-use-in-wide-screen-displays-a-search-for-better-results/280), explaining the possibilities and advantages.
------
### Conclusions :
And now would like to offer the ***Pleroma MastoFE*** (as well as the Glitch-Social FE team) this input, *to be considered for adoption into the code base*.
The enhancements done by **Eskuero**, the creator and maintainer of _Collapsed Mastodon_, could be analyzed and possibly imported into the codebase -- *I believe this is a much more functional setup than the current AWI implementation*.
[Eskuero's project is on this Git](https://github.com/Eskuero/collapsed_mastodon).
Thank you for your attention and consideration.
Rob G., @rgx@muensterland.social [ originally posted [at the **Glitch-Social Github**](https://github.com/glitch-soc/mastodon/issues/1359)]https://git.pleroma.social/pleroma/mastofe/-/issues/90Sensitive content hidden despite "Reveal sensitive media behind a CW by default"2021-04-16T21:10:34ZRoelof PieterSensitive content hidden despite "Reveal sensitive media behind a CW by default"Hello. Perhaps I am misunderstanding but I figured the option "Reveal sensitive media behind a CW by default" would show all content (in Mastodon-FE) even when it is marked with a content warning. I have set this option but still seen CW...Hello. Perhaps I am misunderstanding but I figured the option "Reveal sensitive media behind a CW by default" would show all content (in Mastodon-FE) even when it is marked with a content warning. I have set this option but still seen CW'ed content behind a "clickthrough". I have had this for a long time now (years) but can not imaging me being the only one noticing this. I therefore wonder if I am misunderstanding something (or if something might be wrong with my personal Pleroma instance). Regards, Rolf
![sensitivecontent](/uploads/95b988098def0d6bc5b859a890a6f7c0/sensitivecontent.png)https://git.pleroma.social/pleroma/mastofe/-/issues/89Unable to load more posts in lists2021-07-22T18:41:15ZOniriCorpeUnable to load more posts in listsHi!
The lists display 20 posts by default, and should load more once the scrolling is finished
However this feature does not work, and the "load more" button is not displayed either.Hi!
The lists display 20 posts by default, and should load more once the scrolling is finished
However this feature does not work, and the "load more" button is not displayed either.https://git.pleroma.social/pleroma/mastofe/-/issues/87Can't use Cmd+Enter on Mac to send a toot2020-08-17T23:04:56ZGhost UserCan't use Cmd+Enter on Mac to send a tootI recently upgraded from Pleroma stable to develop and sometime between those releases it seems certain hotkey functionality was broke or removed.
I used to be able to send a toot by pressing Cmd+Enter, now, oddly, I can use Ctrl+Enter ...I recently upgraded from Pleroma stable to develop and sometime between those releases it seems certain hotkey functionality was broke or removed.
I used to be able to send a toot by pressing Cmd+Enter, now, oddly, I can use Ctrl+Enter but on a Mac that's not intuitive.https://git.pleroma.social/pleroma/mastofe/-/issues/86masto-fe does not follows instance's :allowed_post_formats2020-07-27T17:40:08ZGhost Usermasto-fe does not follows instance's :allowed_post_formats`allowed_post_formats` is not even in the codebase
edit: same goes for `:subjectLineBehavior`
![admin-fe](/uploads/815ba977cd407731450248015548495c/Screenshot_2020-07-26_Admin_FE_20200726084221.png)
![masto-fe](/uploads/84c3aab56c220...`allowed_post_formats` is not even in the codebase
edit: same goes for `:subjectLineBehavior`
![admin-fe](/uploads/815ba977cd407731450248015548495c/Screenshot_2020-07-26_Admin_FE_20200726084221.png)
![masto-fe](/uploads/84c3aab56c22062c1b917ead15ac6d3a/PrtScr-2020-07-26-103534_20200726084219.png)https://git.pleroma.social/pleroma/mastofe/-/issues/84Unable to set theming2020-07-30T09:58:28ZElias MårtensonUnable to set themingIt is not possible to switch Mastodon FE to light theme.
Steps to reproduce:
1. Select Mastodon FE
2. Click on the settings button
3. Click on User Preferences
This sends you back to the Pleroma FE preferences screen so there is no wa...It is not possible to switch Mastodon FE to light theme.
Steps to reproduce:
1. Select Mastodon FE
2. Click on the settings button
3. Click on User Preferences
This sends you back to the Pleroma FE preferences screen so there is no way to set the theme for Mastodon FE. This is a problem for people like myself whose bad astigmatism makes it impossible to use UI's with dark backgrounds.https://git.pleroma.social/pleroma/mastofe/-/issues/82Add support for local_only when posting statuses2020-07-27T14:22:52ZHaelwennAdd support for local_only when posting statusesAs seen in <https://git.pleroma.social/pleroma/pleroma/-/merge_requests/2289>, all the UI work should be done and only require API modification.
This issue is too make sure I don't forget about it.As seen in <https://git.pleroma.social/pleroma/pleroma/-/merge_requests/2289>, all the UI work should be done and only require API modification.
This issue is too make sure I don't forget about it.HaelwennHaelwennhttps://git.pleroma.social/pleroma/mastofe/-/issues/81Make mastofe work like all the other frontends2020-06-29T03:07:21ZlainMake mastofe work like all the other frontendsThis came up in https://git.pleroma.social/pleroma/pleroma/-/merge_requests/2400#note_65212. It would be nice if mastofe could work like the other frontends, live on `/` and be able to log in etc. Rebasing it to `/` is probably easy, but...This came up in https://git.pleroma.social/pleroma/pleroma/-/merge_requests/2400#note_65212. It would be nice if mastofe could work like the other frontends, live on `/` and be able to log in etc. Rebasing it to `/` is probably easy, but adding the basics for log in seems harder. Maybe we can pull in some stuff from @alexgleason's soapbox?https://git.pleroma.social/pleroma/mastofe/-/issues/80Filter by account2020-06-17T21:39:55ZKmNFilter by account### Environment
* Installation type:
- [ ] OTP
- [X] From source
* Pleroma version: 2.0.6-stable
* Operating system: (Docker) alpine:latest
* PostgreSQL version (`postgres -V`): 11.x
### Bug description
Mastodon-FE filters do not...### Environment
* Installation type:
- [ ] OTP
- [X] From source
* Pleroma version: 2.0.6-stable
* Operating system: (Docker) alpine:latest
* PostgreSQL version (`postgres -V`): 11.x
### Bug description
Mastodon-FE filters do not take author into account when filtering. If I'd like to filter '@user@foo.bar' from the Home TL (or similar with filters available) the filter rules will NOT match on author (or any other fields that aren't the main post). This makes it impossible to filter users from TL's that are also in lists.
Proposed: have an ability to filter by author / poster so users can be filtered from individual TLshttps://git.pleroma.social/pleroma/mastofe/-/issues/79Add emoji reaction support2020-11-19T15:15:44ZnormandyAdd emoji reaction supportThis is already supported in Pleroma-FE.This is already supported in Pleroma-FE.https://git.pleroma.social/pleroma/mastofe/-/issues/78`short_name` fields missing from `manifest.json`2020-06-01T11:18:16ZJoYo`short_name` fields missing from `manifest.json`The `short_name` field is a requirement? for installing to home screen (A2HS).
I am pretty sure it can just be the same as `name`.
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Add_to_home_screen#How_do_you_make_an_a...The `short_name` field is a requirement? for installing to home screen (A2HS).
I am pretty sure it can just be the same as `name`.
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Add_to_home_screen#How_do_you_make_an_app_A2HS-readyhttps://git.pleroma.social/pleroma/mastofe/-/issues/77OAuth token non-retentive2020-05-25T19:27:54ZMelOAuth token non-retentiveHi! I noticed whenever I use the MastoFE that the OAuth tokens aren't saved anywhere other than for a session, unlike the PleromaFE the MastoFE will ask for a new OAuth token each session. Is there by chance a possibility that by hosting...Hi! I noticed whenever I use the MastoFE that the OAuth tokens aren't saved anywhere other than for a session, unlike the PleromaFE the MastoFE will ask for a new OAuth token each session. Is there by chance a possibility that by hosting both MastoFE and PleromaFE on the same domain it interferes with the login tokens?
Is there any way of making sessions last in MastoFE like they do in the PleromaFE?https://git.pleroma.social/pleroma/mastofe/-/issues/75MastoFE displays HTML encoded characters as raw2019-11-25T21:47:55ZMew MewMastoFE displays HTML encoded characters as rawFor example, `'` is displayed as `&#39;`.
Thread where the issue was found: https://niu.moe/@Ste1lar/103200675829261397For example, `'` is displayed as `'`.
Thread where the issue was found: https://niu.moe/@Ste1lar/103200675829261397https://git.pleroma.social/pleroma/mastofe/-/issues/74Add subscription to a user (the bell)2019-09-13T19:07:01ZHaelwennAdd subscription to a user (the bell)https://git.pleroma.social/pleroma/mastofe/-/issues/73Add UI for post expiration2019-08-25T04:49:21ZHaelwennAdd UI for post expirationSee: https://git.pleroma.social/pleroma/pleroma/merge_requests/1595See: https://git.pleroma.social/pleroma/pleroma/merge_requests/1595