@Takom@georgia@snacks i forgor why we moved, it was something akkoma had that pleroma didn't then (i think custom emoji reacts?) and no we don't move back because why. also modern pleromafe literally has a loading screen (sorry hj :pleadingcute: )
@lucy@Takom@georgia@snacks yeah, custom emoji reacts, which i left out on purpose of the regular emoji reacts because they lead to a few issues (like duplicated emoji) which i wanted to sort out first. in the end those issues didn't turn out to matter much because of the actual usage patterns that people have, so i suppose it's alright to just live with the problems.
@lucy@Takom@georgia@snacks you literally almost do not see it now. if there was no loading screen, it would be a blank white page for the same amount of time
@lucy@Takom@georgia@snacks the loading screen was bugged btw, it takes less than a second right now and i think theme compilation was made even faster recently
@lucy@Takom@georgia@snacks@vaartis it also shows error if something bad happens, or stage where something went wrong instead of blank screen. You can always close your eyes and pretend there's a blank screen. 🙄
Reminds me how at young age I would stubbornly prefer to buy motherboards with Award :award_bios: BIOS like an idiot until they stopped making them
@lucy@Takom@georgia@snacks@vaartis and hey, our loading screen has pleroma-tan (who also falls on the floor "orz" if error occurs) and bouncy pleroma logo (which also falls down if error) instead of generic spinner. It also randomizes between fox and non-fox versions of the art. All I'm saying is we (I) put a lot of effort to make it stand out and be less annoying.
Can't wait for akkoma adopt it and replace mascot wit (((copyright infringement)))
@hj@Takom@georgia@lucy@snacks@vaartis You literally put an "uwu we made a fucky wucky" screen like it's a fucking videogame instead of undoing whatever the fuck causes half a minute of load on each tab opened. An effort to be outright malicious to your own users, perchance.
@hj@Takom@georgia@lucy@snacks@vaartis Your FE is the face of the whole project. And said face is now bloated harder than Nikocado with nothing done to rescind the situation other than sprinkling it with glitter. We already have pisskey, you know.
@hj@Takom@georgia@lucy@snacks@vaartis Means nothing until the next release since the slower version was approved to be bundled with BE and thus is running on who knows how many instances.
@mint@Takom@georgia@lucy@snacks@vaartis pisskey has 3 separate loading screens and takes 5+ seconds to load a single post. At least we put effort in optimization.
@dcc@Takom@georgia@lucy@snacks@vaartis@mint then why y'all silent about it? Why you complain a month later instead before. Is 200ms load time too much? Do you want me to remove themes support? Show blank screen?
@hj@dcc@Takom@georgia@lucy@snacks@vaartis@mint because you tend to react very emotional to these issues and people don't want to hurt you and don't want the stress. I don't think having a discussion in this thread is helpful to anyone. you should enjoy your time at assembly instead.
@lain@dcc@Takom@georgia@lucy@snacks@vaartis@hj >people don't want to hurt you and don't want the stress I might've missed the part where that's my problem. The real reason is it's going to be as much of a fruitful endeavour as talking to a GNOME developer. Takes less time to fix it on my side by rolling back to the last good known commit and backporting changes when necessary. Sadly I'm reminded about the situation ever time I need to look up context beyond what's federated here.
@mint@dcc@lain@Takom@georgia@lucy@snacks@vaartis i AM considering making a separate PleromaFE build which doesn't have long loading time but doesn't have theme support and just uses default one forever
@mint@dcc@lain@Takom@georgia@lucy@snacks@vaartis we're not GNOME, we try to listen. We add configuration options for everyone to the point where it hurts us (too many options!). Please do give most recent develop a try and do tell me your experience after using it for a day or two, it should be much better than month ago.
Also it's not approved for next BE release, nor there's FE release with it yet because we're still gathering feedback.
On a related note, was it intentional that the status history button was removed from the extra_buttons component or whatever it's named after the switch to pinnable buttons or was it unintentionally left behind?
Also just to let you know, some of the CSS classes that are used for the extra buttons behind the 3-dot menu on posts and in other spots get picked up by some 3rd-party filters on uBO. Mainly the EasyList annoyances list and the obvious AdGuard Social widgets one. I know that these extensions are technically unsupported and trying to fix it is a never-ending battle, but maybe expect some complaints in the issue tracker from missing buttons whose outline only shows up when editing the pinned buttons.