What is the BL code?
A proposed Message Code for Twitter and any social network.
The BL code means "broken link." It tells someone that a link they sent out was defective.
Geekly speaking, it should be "resource," but I won't get into why. I think the average Twitter user can remember, "Broken link," Busted link, Borked Link, etc.. Not going to spend much time writing this up formally, yet, but feel free to comment/disqus it below. Perhaps we can make it grow!
As always, I reserve the right to completely discard or discredit this idea at any moment, and without warning or notification of any kind. #SoSuckit
When To Use The BL Code
Anytime you click someone's social feed links, and get any type of fail, and want to quickly, with a minimum of keystrokes, tell the sender that the failure happened, so they can fix it, hopefully before their bad link gets too much traction with their followers, retweeters, etc.
The failure may have been due to:
- Failed links (404s, etc.)
- Video, page, or widget failure.
- The earth gets hit by an asteroid and we all die.
What are Message Codes?
Among the many needs we have in the social space, is more codes to give some quick semantic or semiotic meaning to social media messages (tweets). Twitter has become the 21st century telegraph, on many levels. But it still lacks its own modern morse code for daily use.
Mostly for my own fun and use, I am creating a few codes as the need for them becomes apparent. Most languages and syntaxes get set in stone far too quickly, but you can be sure the social namespace is going to get crowded, as our social nets evolve. I'd like to see an organic, bottom-up evolution from daily use for the most ubiquitous daily codes. Let local dialects flourish! Hopefully there will never be too many at the root level. I'd like to see lean, mean and very clean (and thus, easy to adopt).
Twitter is the proverbial herd of cats, and the only way anything can happen is over time, with enough people doing it. It gets easier if what we want people to do is really SIMPLE. Thus, I have come up with these few…
The Tweet (Or Transmit) Codes:
Substantially changed to mock or clarify, but may have altered meaning. Be sure to check original, if it could matter.
Follow anyone, anytime #FF Hashtag.
Please repair & resend… and/or delete bad original.
CC = Carbon Copy Recipent List [proposed]
Do Not Retweet. Recipients only need to receive it ONCE (and not be tweet-bombed).
DR = Don't Retweet/Retransmit [proposed]
Do Not Retweet. Only copy & paste the message/URL it is linked to (or ignore/discard/keep as just a memo).
Why Define These Codes?
Because I can, of course. And because they are needed, and because I want to use them right now, myself, and feel my 6000+ followers would, as well. Each is based on years of daily practical tweeting. Few would argue that I do and read a lot of that, and I feel my years of programming and interface design skills makes me at least as eligible as anyone else is to make hideous mistakes.
I am sure others, with an interest in such things, will come up with a more robust standards scheme to build on my meager beginnings, or just overwrite them completely. I'm down with either outcome. For now, Shoq codes are an intuitive and useful language start, that could assist in the evolution of more useful tools (quickly).
See Also: My "MT" signal idea
Can you do this on Twitter… just make stuff up?
So who's gonna stop me, you? Yes, you can just make stuff up :) Twitter is a community defined tool; many of the better ideas, including the RT, #hashtags, and other conventions came about via an ad hoc adoption by the community itself. What works is what people decide is useful, and they just start using it. As of September 10th, 2009, I had been using the BL signal for about a week. I intend to keep using it. If others find it a good idea, it will endure, and future digital anthropologists may find this page and understand its origins. If it doesn't, it's just one more of my thousands of bad or failed ideas nobody will remember a month from nowTweet