No Javascript Fall-back FE

PL-FE should maintain functionally when JS is disabled, or ship with a functional fall-back FE, as per W3C accessibility standards. Maybe a brutaldon port?

Edit: removed joke and added details from pleroma-fe crosspost

Use gopher and post with curl uguu

closed

lol

that's not web accessible, that's a separate protocol

also please see issue 632....

cool, we are not rewriting our frontend just to comply with W3C standarts, it is not like we fully comply with ActivityPub lol

@sunmaid If you really want it: There's also Brutaldon, it's a front-end that works without any JavaScript, also supported by Pleroma's Mastodon-API.

but it's not shipped with Pleromer, Pleromer should have a notice when a browser is too old or at the very least document what browsers are supported somewhere, it's actually an issue for some people with old devices

see

https://pl.smuglo.li/notice/9fjcPuTho55yVcNEtk

@orekix A notice would be sensible, I guess. Though I think the notice issue is rather a Pleroma-FE issue than a Pleroma issue (wrong repo)

@rinpatch not the same thing. if the FE was built for the web, it should've been written to follow web standards; if it wasn't and isn't, it should be an open issue with an intention to eventually resolve

@Toromino brutaldon requires providing their service your login information; and for some reason your email too.

maybe the solution is too port its FE and treat it as the default fall-back when JS is not available. In any case, a fall-back is necessary

sorry didn't realize there was as a separate FE repo

@sunmaid Set up your own brutaldon, if you don't trust any service. Or just curl on Mastodon-API. There are a lot of ways.

@orekix @sunmaid well sorry, but currently there is no one on the dev team interested in rewriting our entire frontend because of people with browsers older than Elixir itself. If someone wants to do it – sure, we will help with code reviews and probably even merge it

Age isn't the only issue. Many people disable JS for security or bandwidth optimization reasons. This only presents a problem with sites designed following bad practices.

I moved the issue over to pleroma-fe.

Edit: was closed, said it belongs in main repo.

@sunmaid

many people

https://blockmetry.com/blog/javascript-disabled

@rinpatch you misunderstood where the emphasis of that sentence lies. I meant that the reasons a user would have JS disabled include security and optimization as well as outdated browsers.

If you're trying to suggest the portion of PL users who would prefer non JS is too small to be relevant based on that statistic, you would have to consider PL users are a much more specific userbase than the internet as a whole, and one generally technically literate that they would have optimization, privacy & security as concerns as well as basic web standards-compliance such that non JS would be common; evidenced by it being fairly commonly discussed as well as browsers that don't support it, e.g. qutebrowser, and the general instance use rate of gopher support, etc. I'm certainly not the only person to have requested or noted the lack of a non JS FE.

If the status of this issue is "it's worthwhile but no one is currently interested in doing the work needed" then should it not remain open?

reopened

changed the description

changed title from no JS FE to No Javascript Fall-back FE