Does every change == a new file?
Maybe some filtering/screening of changes...
A code-based captcha to test basic understanding of code?
Did have another suggestion but it would make correcting typos difficult
(so guess what it was).
Could the changes not be saved as diffs from the original?
It depends on the quality of contributions by visitors on wether it
would provide a considerable enhancement or not. Why not give it a
chance? I don't imagine a real big flood of traffic filling disk quotas.
On 19/09/15 16:33, Pall Thayer wrote:
So I finally finished the site for this project. But I'm a little
conflicted about one thing. It would be nice to allow visitors to save
their altered codes on the site and make them available to all. However,
I'm worried that it will get over-used. I.e. someone comes along, makes
one small change, saves it, then makes another small change, saves it,
ad infinitum. I'm thinking that I could curate it. That is, only keep
the good ones but that's going to make a lot of work for me. I'm
interested in hearing what others think about this. Do you think that
allowing visitors to save and make all available would make for a
considerable enhancement to the project?
Best r.
Pall
On Sat, Sep 19, 2015 at 11:06 AM Pall Thayer <pallt...@gmail.com
<mailto:pallt...@gmail.com>> wrote:
http://pallthayer.dyndns.org/objectsofart
--
P Thayer, Artist
http://pallthayer.dyndns.org
--
P Thayer, Artist
http://pallthayer.dyndns.org
_______________________________________________
NetBehaviour mailing list
NetBehaviour@netbehaviour.org
http://www.netbehaviour.org/mailman/listinfo/netbehaviour
_______________________________________________
NetBehaviour mailing list
NetBehaviour@netbehaviour.org
http://www.netbehaviour.org/mailman/listinfo/netbehaviour