[rfk-dev] robotfindskitten - web version
lighteater at gmail.com
Tue Mar 24 12:29:30 PDT 2009
On Tue, Mar 24, 2009 at 6:13 PM, Peter A. H. Peterson <pedro at tastytronic.net
> Yeah. I agree that adding nki is one of the great things about rfk,
> but one problem is the "editorial control" aspect. Like, a middle
> earth (or nethack) version of rfk is funny, but it's not funny if the
> official version is half middle earth and nethack references. The best
> way I can describe it is that nki shouldn't (in general) be obvious
> pop culture references, and above all, they shouldn't be predictable,
> because that ruins the zen nature of rfk.
I agree that the references should never be obvious, but thats the trick
with references everywhere - if theyre too obvious or too many it all
becomes bland... I guess the best idea would be to start with the official
nki list and build new lists as submissions come along, while allowing
players to choose which theyd like to use for their trip.
and we also run the risk of people stuffing the
> ballot box full of ALL YOUR BASE and whatever today's meme is.
True, but again if you make an intelligent reference to a meme it can make a
The main issue for me with control is that if it would be something
> integrated into the site, we'd want it to be a faithful representation
> of robotfindskitten. There are a lot of subtle details that people
> often miss for example, that it's robotfindskitten and not Robot
> Finds Kitten, etc. I tend to think that implementations of rfk should
> emulate the POSIX version as much as possible, unless constrained
This may seem like nitpicking, but to us, the charm of rfk
> is about the whole package.
> While the "editorial control" issues I described above are not
> strictly speaking part of the implementation, they do reflect on the
> quality and experience of the simulation.
I certainly would like to maintain that feel, without it rfk looses much of
On the issue of quality control - well, thats going to be hardest part to
do. Its easy to miss that thin line between being too restrictive and too
open. If anyone will be interested i might do a sort of 'approval panel'
with access for people who'd like to have a say in what goes in. However ill
start with something simple first.
Another issue, now that I'm thinking about it, is that an "official"
> that, rather than proprietary Flash (or even Java). There are several
> reasons for this; we don't want to require plugins in order to play,
> we don't want to require proprietary software to play, and we don't
> want it hard to maintain. We also don't want to be distributing
> dangerous code to users through the website, and (speaking for myself)
> DHTML, etc.) rather than third-party code blobs (flash, java, etc.).
and these tools are certainly more than enough to make a good web
implementation of rfk. Im all against flash and similar bonuses for this
This means that it wouldn't really be about adding lots of new
> features to rfk. (e.g., if one day you wanted to add a mode where the
> nki start roaming around the field, we wouldn't want that to be part
of the site, or possibly it would have to be some kind of experimental
> mode... but the point of the official web implementation shouldn't be
> (from our perspective) about having tons of "alternate modes".)
The only alternative mode, so to speak, ive given thought was to replace
ascii items with eggs on easter and maybe have robotfindseasterkitten, but i
really doubt ill finish in time anyway :)
> Again, I invite you to join the rfk-dev list if you haven't and we can
> discuss these issues there; I'm sure others will have thoughts.
Ive already signed up, thanks for the reminder tho :)
Thanks for everyone's input, cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rfk-dev