Re: [H-source-users] Introduction

[bill-auger]

On Sat, 17 Jul 2021 23:04:01 -0400 Bone wrote:
> I would suggest converting the h-node web application into a Git
> repository.  This could be easier to accomplish as it can be done with
> stable existing free software.

PHP and python are also stable existing free software


On Sat, 17 Jul 2021 23:04:01 -0400 Bone wrote:
> I recently requested feedback on what people thought of the Free
> Software Directory (FSD) being a Git repository.

i admire your persistence and intentions; but my response would
be much the same as the FSD proposal; which is considerably
less enthusiastic than damien's

what this amounts to, is taking something which is very easy for
anyone to contribute to, with no technical skills required, and
converting it into something which requires proficiency with
software development tools, in order to do even the simplest
operations

to expect non-technical people to learn software development
tools, could only discourage participation more than encourage it

your arguments are more fitting WRT to mediawiki (access via
text-only, no-js, etc); but h-node is a much simpler website -
the "web application" buzzword is ridiculous when applied to
such a modest website - it needs to be nothing more than a
front-end to a database

all that is also ignoring the h-client program, which is the
preferred way to contribute data, and is much, much, easier then
using the web interface for that purpose - no web browser nor
terminal is required to collect all of the relevant hardware
data and upload it to the database - h-client does everything -
the user does not even need to understand what is happening, in
order to contribute complete and perfectly formatted information
- a few mouse clicks, and the entire process is done

there is another issue, which i dont believe that anyone
addressed in the FSD discussion, which is as relevant for
h-node, that is: login credentials - you are proposing all
"static web" pages - that makes it impossible for anyone to
register or login via the web; because there is no database
andno authentication service running

then what should be done with all of the existing registrations
and password hashes? - shall those go in the public git repo? -
surely, thats not a good idea - but without login credentials,
everything MUST be done with git; and all new contributions
would be anonymous - but that is a very loud invitation for
spam; so where do you put the captcha?