Re: FSD as a Git repository

[Lorenzo L. Ancora]

> in short, the best javscript is 'none', and the best web browser
> is 'none' - no need to re-invent the wheel - mediawiki already
> supports it

Very zen. I would have written 'coded as optional dependencies' and 'the 
most up-to-date', but that's okay. ~~ Less is better. ~~

> > has the regrettable presumption, that a web browser is required
> > to read/write data to/from the internet, or to do so in an
> > "accessible" way

That's true, and the worst thing is the World Wide Web Consortium shares 
this latest regrettable presumption <https://www.w3.org/TR/WCAG21/>. 
Also, all those who adhere to the Web Accessibility Initiative (WAI) and 
did implement their accessibility solutions as web browser integrations 
are indeed nearsighted. I'm sure all impaired users will be so bold (and 
also helped by another individual with enough 
time/experience/competence) to install a dedicated application only to 
browse the Directory this way.

Also, I was wondering: isn't beautiful to gift everybody with the 
ability to cut down in half the required efforts to clone & DDOS the 
Directory?

Putting aside the sarcasm, my heretic tip is that, before enabling any 
API and thus extending the attack surface, it might be a good idea to 
set API usage limits and make sure the database can handle the extra API 
overhead (aKa making stress tests during a moment of low traffic). I see 
the MW API more as an administrative aid for when there is the sudden 
need to apply complex mass operations and not as something to keep 
enabled for long time, but as with many tools, potential is often 
overlooked.

Il 14/07/21 06:17, bill-auger ha scritto:
> FWIW, mediawiki has a complete REST API - it can be accessed from
> the command line with curl, etc - all of the discussion so far
> has the regrettable presumption, that a web browser is required
> to read/write data to/from the internet, or to do so in an
> "accessible" way
>
> API clients are easy to write; and there are clients made for
> mediawiki already (weboob alone, has multiple plugins for
> mediawiki) - AFAIAC, that would satisfy the text-only use-case,
> just as well as gopher or anything else would, but without
> replacing the wiki, migrating all of it's data, or even patching
> any upstream code - the FSF would only need to enable API
> access, if it is not already
>
> if some web service has a complete remote API, that is already
> the ideal option for text-only, no-js, accessibility, etc - an
> API is fully accessible by its nature (no colors, no mouse
> buttons to locate, etc)
>
> in short, the best javscript is 'none', and the best web browser
> is 'none' - no need to re-invent the wheel - mediawiki already
> supports it

--
All messages from/to this account should be considered private.
Messages from/to newsletters should not be reshared.
TZ: Europe/Rome (Italy - CEST).

OpenPGP_signature
Description: OpenPGP digital signature