every time i try akkoma-fe it's just so so bad. Everything is outdated. Everything is misaligned. Everything is half-assed. Everything is poorly designed. It's like they don't care about front-end at all.
Timeline
Post
Remote status
Replies
32
@hj The top bar changes are crimes against frontend design. Settings profiles are interesting though. And MFM is something I would want to do some time, but it requires writing a proper parser like BBCode, the Akkoma one is a hack.
@phnt i think settings profiles are obnoxious and our implementation is better. Totally not having a NIH syndrome, totally not.
I think even a hack is ok for MFM, since MFM itself is a hack.
I think even a hack is ok for MFM, since MFM itself is a hack.
@hj MFM only works in text without any formatting, which is something I don't like. I would want it to be a switch you can enable for any input type and it act as a preprocessor that generates the HTML.
@hj It's just a series of $[something] directives, how hard can it be. Famous last words.
@phnt I wrote two HTML parsers and one binary parser (for unreal engine 1 (deus ex) .u files), I could easily do MFM. I just need permission.
@hj You don't need a permission I think. And it is just HTML with funky span tag classes. The MFM syntax is "$[directive1=value,directive2=value,... Post Content]". Here's a FEP that Akkoma implements.
There are two parts for this, the BE pre-processing parser that takes input when post has MFM enabled and generates a string with the MFM tags replaced with the HTML representation that is then sent to either another parser (like BBCode) or straight through. The second part is FE that provides the styling for the HTML.
For the BE parser, Nimble Parsec used by BBCode is pretty comfy at least to me, Akkoma implements their own lexer and everything.
You could implement it fully in FE, but then other frontends like Nicolium wouldn't be able to make use of it easily.
There are two parts for this, the BE pre-processing parser that takes input when post has MFM enabled and generates a string with the MFM tags replaced with the HTML representation that is then sent to either another parser (like BBCode) or straight through. The second part is FE that provides the styling for the HTML.
For the BE parser, Nimble Parsec used by BBCode is pretty comfy at least to me, Akkoma implements their own lexer and everything.
You could implement it fully in FE, but then other frontends like Nicolium wouldn't be able to make use of it easily.
@hj @lain @mkljczk It is a disaster waiting to happen, yes. When it is done on the backend, it's not as bad as the content is still sanitized on the backend.
The backend could also parse it in stages so "$[jelly.speed=2s idk] [i]italics[/i] the rest", would first be:
<span class="mfm-jelly" data-mfm-jelly="2s">idk</span> [i]italics[/i] the rest
and then:
<span class="mfm-jelly" data-mfm-jelly="2s">idk</span> <i>italics</i> the rest
The backend could also parse it in stages so "$[jelly.speed=2s idk] [i]italics[/i] the rest", would first be:
<span class="mfm-jelly" data-mfm-jelly="2s">idk</span> [i]italics[/i] the rest
and then:
<span class="mfm-jelly" data-mfm-jelly="2s">idk</span> <i>italics</i> the rest
@lolitechengineer @mkljczk @lain @phnt @i poast got hacked because of badly formatted HTML got parsed incorrectly and allowed script tag
@hj @lain @mkljczk
<span>$[whatever </span>]
would result into
<span><span class="mfm-whatever"></span></span>.
where the last closing span is the one inserted by the parser. An empty span isn't an issue I think, removing the first span is worse, because there now is a closing span tag for nothing.
Still, both of those should be sanitized before that matters.
<span>$[whatever </span>]
would result into
<span><span class="mfm-whatever"></span></span>.
where the last closing span is the one inserted by the parser. An empty span isn't an issue I think, removing the first span is worse, because there now is a closing span tag for nothing.
Still, both of those should be sanitized before that matters.
@mpg @hj
>do that for every single instance you're about to visit
Paste the link to the post into the search. Unless the remote instance deliberately killed of federation, it will give you the post and if it is a post from current Pleroma release/Mastodon/GTS also automatically fetch all replies to the post.
>What would be your solution for the same frontend including <canvas>-based attachment molestation enabled by default?
Disable it, or ask your admin to disable the option by default in backend config (this should now be possible for all settings in FE I think; possibly not in a release yet)
>do that for every single instance you're about to visit
Paste the link to the post into the search. Unless the remote instance deliberately killed of federation, it will give you the post and if it is a post from current Pleroma release/Mastodon/GTS also automatically fetch all replies to the post.
>What would be your solution for the same frontend including <canvas>-based attachment molestation enabled by default?
Disable it, or ask your admin to disable the option by default in backend config (this should now be possible for all settings in FE I think; possibly not in a release yet)
@khayyam @mpg @hj
>t. can't implement own standard wrappers for gcc
>using gcc
albanian-tor-terrorist.png
>t. can't implement own standard wrappers for gcc
>using gcc
albanian-tor-terrorist.png
@phnt @hj There are 671 active Pleroma instances: https://fedilist.com/instance?software=pleroma
Do you suggest asking admins of each of them to check whether they have it enabled by default? Posts with images federate, just so you know.
Do you suggest asking admins of each of them to check whether they have it enabled by default? Posts with images federate, just so you know.
@mpg @hj It doesn't bother most people as evidenced by there being zero issues in the repo about it being the default, outside of few users I could count on my hands outside git. It bothers you and few others, not everybody.
If you get so mad about webp attachments, maybe also complain to Misskey doing it by default and John Mastodon for re-encoding all attachments by default.
If you get so mad about webp attachments, maybe also complain to Misskey doing it by default and John Mastodon for re-encoding all attachments by default.