Looks good to me so far!
(For some reason, I'm getting "install" links on every link on the
page, not just ensocommand links, but I don't think that's your fault,
I think my local Enso JavaScript is broken :))
> It is
> still missing some community features, but it already can be used to
> publish commands.
There's certainly a use for this sort of thing. I designed the
installation-from-a-webpage routines so it was easy for anyone with a
webpage to publish their own commands, but this actually makes it
easier for people who don't work with the web, which is a good thing.
> Additionally, I'd like to spark dialogue about several aspects of this
> 'platform', I welcome any contribution and some of this has been
> talked about before:
>
> 1. Safety/Trust (enso scripts possess any right the account has under
> which it has been startet.) - How should we communicate/calculate/
> mark/.. a single script's integrity? Some of your buddies/ the enso
> core developers trust a script - can you trust it, too? Will unsafe
> script simply marked unsafe or should they be deleted?
I really don't think we can get into this. A script is software
running on your computer. It can therefore do everything that you can
do. There is no real way to prevent someone writing a script which
does os.system("rm -rf $HOME/*") or os.system("deltree /y c:\\"). This
is not an Enso-specific problem.
> 2. Quality - does quality equal popularity? Can people vote for a
> command? Will there be an enso canon featuring 'good' commands?
I'd be a little wary of this, because ensohub won't be the only place
to get commands from; a high vote on ensohub suggests that a command
is better than others on ensohub only., so we'd need a separate "best
enso commands ever" page somewhere else *anyway*. Personally, I
wouldn't worry about voting; it makes things complicated, and then
people have to register to do it, and I don't think it's worth it.
What ensohub does now (allow you to publish commands, and allow you to
install them) is excellent. I really don't think it needs anything
more. If you get to the stage where there are a million commands
posted on it and you need some way of sorting them, then think about
voting, but for the moment I wouldn't. :)
> 3. Location - (I won't have the time to maintain and develop this
> thing 24/7) Should we put it on ensowiki.com and leave it to the
> community? Is someboy interested in developing this with me (which is,
> actually, my preferred option)?
Ahem. Ensowiki, while Shu and I have access to it, isn't our server.
We can't just run arbitrary server-side code on it :-)
sil
--
New Year's Day --
everything is in blossom!
I feel about average.
-- Kobayashi Issa
A little legal thingy: As the ensoguys account is kind of public,
there are commands being released under that name. If you wrote a
command and published it some time ago some place else, please check
wheter it has been uploaded by the ensoguys account at
http://ensohub.alwaysdata.net/scripts/filter/?userid=3 and if it did,
please tell me whether you want it to be deleted or released under
your username.
So as far as I can see, the basic ensohub features are running: you
can register, publish and download/install scripts. There are however
some rough edges – no search, 'reputation' is of no use yet and there
is obviously a problem with a regular expression extracting imports
from your code.
But anyway: I invite you all to register and publish your scripts.
Please consider giving feedback, too. I'm always interested in hearing
what can be imporoved, even though I don't have that much free time
right now.
@shu, @sil:
ensowiki seems to have a database connection problem, do you think you
can fix it?
- skiqh