From: Robert Currey (Robert.Currey_at_AHand.co.uk)
Date: 08/06/03 13:30
Begin forwarded message:
> From: Robert Currey <Robert.Currey@AHand.co.uk>
> Date: Sun Jun 8, 2003 12:59:27 PM Europe/London
> To: "Simon Smith" <simonjohnsmith@btinternet.com>
> Subject: Re: FW: [hb_wireless] Club Identity
> Content-Type: text/plain; charset=US-ASCII; format=flowed
> Mime-Version: 1.0 (Apple Message framework v552)
> Content-Transfer-Encoding: 7bit
> In-Reply-To: <000001c32d57$529188e0$0201a8c0@kafka>
> Message-Id: <A78E2606-99A8-11D7-95B7-000393454FD4@AHand.co.uk>
> X-Mailer: Apple Mail (2.552)
>
> I'm pretty neural as to what the name of the club should be, but here
> are my thoughts:
>
> I wanted to avoid geographical names: because they're an obstacle to
> outsiders getting involved and I'm hoping our efforts on ad-hoc
> networking will get taken up (ie the locustworld solution is crappy
> but the only thing out there at the mo'.) More locally the use of
> hebden bridge seems to alienate mytholmroyd and todmordeners.
>
> Lily-hopping was an independent thought to describe the ad-hoc nature
> of the network. Later I find its not original (nice article give it a
> read): http://www.wired.com/wired/archive/10.10/wireless.html
>
> I have registered lilyhopping.net on our behalf - we don't have to use
> it though.
>
> hww.{net,org,com} have already been registered.
>
> Lily-Hopping has a warmer less geeky feel than tlas, has more scope
> for touching the right brain, helping with social aspects of the club.
>
> Not keen on using waterside for the network essid - would prefer an
> emotion-neutral, techhy type string eg protocol + lat + long:
> LH_N53:44_W02:00 ie reduce the loss of pride in adopting someone
> else's essid.
>
> The RR - radio repeater bit was so we could affiliate with WLAN but a)
> I got it wrong it should include 'amateur radio', b) whatever I did
> with the phrase it conjured up a club with the wrong emphasis ie the
> physics-y antenna side of 'radio' not the enabling network side of
> things. On balance the confusion outweighs the advantage of
> affiliating to WLAN.
>
> I would like to see this discussion continue
>
> Robert
>
> On Sunday, June 8, 2003, at 01:45 AM, Simon Smith wrote:
>
>> The image attachments in this email didn't seem to be kept when posted
>> to the gink list. So I attach them again.
>>
>>
>>
>> -----Original Message-----
>> From: hb_wireless-bounce@lists.gink.org
>> [mailto:hb_wireless-bounce@lists.gink.org] On Behalf Of Simon Smith
>> Sent: 08 June 2003 00:55
>> To: hb_wireless@lists.gink.org
>> Subject: [hb_wireless] Club Identity
>>
>> Content-Type: text/plain;
>> charset="us-ascii"
>> Content-Transfer-Encoding: 7bit
>> I'd like to continue the debate regarding group identity once again.
>> I
>> am by no means dismissing the great efforts to date; I would just like
>> to offer some further ideas into the mix for consideration.
>>
>> I should say at this point that I am not clear as to whether the LHRRG
>> name and theme are the agreed club identity. In this, I trust
>> reviewing
>> this is not viewed as disrespectful to the efforts rpc and others have
>> already made and that the sentiment is understood.
>>
>> During discussion with StartX and Hick in #DigitalHebden, we threw
>> around several ideas for the club identity. We parted from LHRRG
>> completely so as not to confuse the identity with any evolutionary
>> debate that may be current regarding that theme. Rather, starting
>> afresh we considered the following:
>> An identity that incorporated recognisable geography (place\location)
>> An identity that capitalised on the technology terminology
>> A name or theme that might be adaptable and flexible to a number of
>> situations but had the identity at its core.
>>
>> Without writing an epistle on the thought process, we agreed the
>> following would be a good starting point.
>>
>> .hww
>>
>> .hww = Hebden Wireless Waterside - the theme included was that of a
>> common place name 'waterside' & 'hebden' with the technology
>> 'wireless'.
>> It is also a clever play on the acronym used for sub domain names. We
>> might wish to use this as a private tld.
>>
>> This then evolved as follows:
>> .hww/a .hww/b .hww/g to incorporate the 802.11 standards but allow a
>> suffix to also represent a situation e.g .hww/a = hebden wireless
>> waterside active! hebden wireless waterside bridge and hebden wireless
>> waterside go!
>> Active meaning we are now operational, bridge could be used as a play
>> on
>> the word for both the place name and the 'bridging' technology
>> inferred
>> (wireless waterside is within the 'hebden bridge') and go meaning to
>> launch. These ideas are perhaps better explained in context.
>>
>> If we are to identify ourselves in a 'PR' exercise, we might wish to
>> use
>> any of these in the advertisement of various events we are holding.
>> For
>> example we might wish to wear t-shirts at the 'build' & 'game' event
>> with .hww/g (hebden wireless waterside - go!) as the launch strap
>> line.
>> To this end I include some very rough images to explain the kind of
>> thing I mean. (The images require Flash) - I have also dumped the
>> images
>> into word for anyone who doesn't have flash - obviously I haven't
>> accounted for those who have neither.
>>
>>
>> For interest I also list some of the other possibilities using .hww -
>> It
>> could continue as an identity throughout the group for all manner of
>> things
>> hww. hebden want wireless
>> hww. hebden wish wireless
>> hww. hebden wireless week
>> hww - Stealing your wires since 2003
>> hww/a - Admin
>> hww/u - User
>> hww/f - fionn
>> hww/s - startx
>> hww/h - hick
>> hww/r - rpc
>>
>> All of this may be a bit late of course and as I said, I don't wish to
>> be divisive especially if there is broad agreement on LHRRG. I do
>> know
>> that LHHRG was so because we needed the words radio repeater included
>> to
>> become 'officially' recognised. Nevertheless, I would appreciate your
>> feedback.
>>
>> Rgds
>> Simon aka Fionn on #DigitalHebden
>>
>>
>>
>>
>>
>>
>>
>> <hwwa.fla><hwwb.fla><hwwg.fla><hww.doc>
>
This archive was generated by hypermail 2.1.7 : 08/06/03 13:28 BST