The question is who has the stronger claim to using LCA?
Am currently at work so can't do the research to see who, ahem, came first.
Each January Linux luminaries from around the world descend on Australia and New Zealand to attend Linux.conf.au, an antipodean penguinista gathering of sufficient gravitas that Linus Torvalds himself often makes the trip. The event is referred to as “LCA”, and for the 2015 edition has used #LCA2015 as its hashtag. But …
If the penguin is a gentleman, the lady will come first....
Fantasy is...
You cum together.
Reality is...
The Lady has multiple cums then claims thirst, rolls over and keeps you awake on the wet patch with her impression of a road drill until the wet patch dries out and then shunts you into the corner of the bed and robs the quilt.
YMMV
If you read their list archive, this wonderful reply to Cherie Ellis from Russell Coker:
I think going for #LCAAuckNZ is just a continuation of the problem. Much as "server-hugging" is now discouraged[1] I think we need to start discouraging hashtag-hugging. I mean the very point of a a hash function is to prevent collisions.
A quick Google indicates that sha256 is generally[2] considered secure so I would therefore suggest that our official hashtag be:
$ echo "linux.conf.au 2015 in Auckland, New Zealand" | sha256sum
642a96183278655cb7c90e704a42180e68e059c9cda0e4a5dc9c5562a1b38962 -
I am happy to see that this hashtag is unique in both Google and twitter. Now while some people might say that putting a 65 character hashtag on the end of each tweet is excessive I think it is the best way to go forward to avoid these problems.
I would therefore request we go with:
#642a96183278655cb7c90e704a42180e68e059c9cda0e4a5dc9c5562a1b38962
as the official hashtag for Linux.conf.au 2015.
Proper geek humour
When anyone can make a hashtag, there's no central registry, and multiple uses can collide, the hashtag namespace is not a suitable way of grouping anything remotely important.
I never understand why quite reputable organisations use Twitter as a comms platform, when it's just a kid's chat app.
I can understand using it to inform customers of time-critical issues (such as service outages) or contests. But then customers would 'follow' the account, not the 'hashtag'. IN this situation, why couldn't the linux group just create a new account for this event?
I can't believe I said something positive about Twitter, excuse me while I go brush my teeth to get rid of the taste of vomit in my mouth...
To me, it would actually make more sense (especially once they realized there's a has collision) to use #LCAu2015 for the Linux Conference Au, particularly since there's a Linux Conference North America (which people might refer to as Linux Conference America and abbreviate to LCA.... this'd then be #LCNA2015.)