POLL: Character Limit on Identi.ca
One of the features of the StatusNet software has been that notices are limited to 140 Unicode characters, which (usually...) fits into a single SMS message, and which is the character limit for Twitter tweets. Some users love the limitations that 140 characters entail. Others find it unnecessarily restricting.
Our software, StatusNet, with its 0.9.0 beta versions, now supports a variable limit on number of characters; the administrator of a site can change the limit to (practically) any number or set no limit at all. Many users in enterprises or on remote sites report a more enjoyable microblogging experience with higher limits.
For our flagship site, Identi.ca, which runs on the status.net cloud service and uses the 0.9.0 beta, we'd like to open up the discussion of what an appropriate character limit should be. Setting a site-wide limit is a community decision we'd like to leave in the community's hands. In a conversation on Identi.ca we've solicited some candidate character limits that we'd like people to decide on.
- 140 is compatible with Twitter; in many languages a notice with 140 characters fits into a single SMS message*
- 280 can fit into two Twitter or SMS messages
- 300 is a fan favorite
- 420 is Facebook's status limit and 3 Twitter tweets or SMS messages
- 500 is a little bigger
- 1000 is bigger than that
- Unlimited
- Other
Here's our preferred ways to send input:
- Below is a polling form with the candidate limits. You should be able to vote there.
- We'd love it if people use tags to indicate their preference, by posting a notice on Identi.ca with #limit420, #limit500, etc. (People tags are good here, too.)
- Comments on this blog post
- Discussions on Identi.ca itself
Remember: these are non-binding polls that we're using to survey interest. There's not much value in cheating, except to slow down the process and aggravate everyone.
Thanks to everyone who's expressed their interest so far; I'm looking forward to seeing how this decision pans out.
* But it's a little more complicated than that. An SMS message can fit 140 bytes; that's 160 7-bit ASCII characters (English), 140 8-bit characters (like Latin languages), or 70 full Unicode characters (Japanese, Arabic, etc.). Twitter uses 140 Unicode characters, regardless of language.


Comments
still 140
There are still 140 Characters used and I'm really happy about that.
If there were more Characters I would not be able to maintain an overview. The strength of Identi.ca is that it can be used like a Newsticker and therefore messages have to remain as short as possible!
Identi.ca doesn't have to
Identi.ca doesn't have to perfectly copy Twitter's way of posting messages. I think 300 characters is enough for a paragraph.
140 meanwhile, forces you to post an update in one sentence. And one sentence can't describe everything you want to say.
length
140-280 is good enough. Its supposed to be a quick post not a diary. Its micro blogging not blogging. If you have a post that is too long, split it into multiple posts...it's not the end of the world.
Why unlimited is better than any arbitrary limit
So far I have read excellent point for going "unlimited".
I would add that with Unicode information density is not tied to length of a message in characters, so the whole point of having a message length limit by character would encourage the use of characters which carry more bits information.
Best points I have found so far:
* You could limit length of received messages, instead of sent messages.
* Messages which are too long for one service or another, could simply be truncated.
* * This would also encourage people going to identi.ca to read the full message.
* Microblogging services like identi.ca are now used for conversations where 140 characters is just not enough.
* Instead of imposing an hard character limit, you could simply warn the user when the message is too long for another service.
* Most services allow much more than 140 characters. Why not have the opportunity to make full use of them?
280 is adequate
I think 280 is enough to say something and add extra information or even an explanation. Sometimes when you are quoting something you hear on the news, you only have enough space to quote and then not enough to add additional comments or thoughts.
This would also make identica more appealing to twitter users, who will feel restricted by just 140.
56% of the people who voted in this poll want something larger than just 140 chars.
300 is best
I feel that 140 is just too short if you wish to say something important and also perhaps include a link, any bigger than 300 and you're writing a book...
I voted 280, although I'd be
I voted 280, although I'd be fine with 140, 140 is just a little short. And shorter than an SMS would fit (SMS is 160). The compatibility with twitter and facebook I do find important, but compatibility shouldn't stiffle innovation.
On the other hand, bigger messages would turn it more into a blogging system, they key to microblogging is that you can read in a very short line what something is about, or what is going on. Providing the possibility to scan lots of information at once and follow many subjects at once.
I think 160 or 280 would still be short enough for quick parsing, but the extra length would give the benefit to be more clear on the subject.
Way... toooo... short!!! :)
I think it is way too short, i had to rewrite my bio 4 times, each time deleting vital information about myself. Now people may think i am not very interesting and i am, i promise xx
Tips
Unlimited is great option.
Still on the Fence
Still not sure. The 140-limit is taken as an advantage by several people, especially in certain geek crowds, and it's probably going to be applied by people even if it's lifted in a given microblogging environment. But there's a lot to say about giving other users more freedom. Microblogging isn't just about one usage pattern.
I'd probably favour a hybrid solution. Posts are limited to 140 bytes but some bytes may be used to extend content. Instead of tiny URLs, a better way to safely encode/decode URLs. Machine-assisted text summaries. Metadata, media content, and other extras (such as longer texts) could be added in a byte-efficient fashion. Usernames don't count in the character limit. SMS versions could still be central to the whole deal, but there'd be ways to expand from that.
No forking
If Identi.ca and Status.net are to lead the OMB federating revolution (which they should) forking micro-blogging data elements is suicidal.
>140 is why blogs and URL shorteners were invented.
After using Google Buzz...
I changed my vote to 1000. Because Buzz does a good job of demonstrating that an interface can accommodate longer than 140-char posts (via showing only a subset of the post after an initial read, until you expand it again), and I've found it easier and faster to quickly write 3 paragraphs than to try and summarize complex thoughts in one or two dents.
Character Lenght
I think 280 characters is good.
it will give people & organizations a change to share information about events which people might want to know about.....
300 or more would be good
Maybe then I'd start posting notices in my mother tongue -- our words tend to be long and I *hate* SMSing abbreviations.
I'm torn
On the other hand, I think longer messages would be a good idea (and I might as well vote for 420), but on the other hand, I think Twitter compatibility is pretty important. If there'd be automagical splitting, that'd be nice.
I voted unlimited
because postings of unlimited length just make life easier. The first 140 characters are forwarded to other systems (sms, twitter) minus a link for the rest of the message.
Automatic sizing
I heavily use the Identi.ca to Twitter bridge that reposts tweets. If Identi.ca were to resize, say to the Facebook limit, then there would have to be some kind of auto-parsing to slice larger dents into tweet-sized dents.
Thanks for the discussion!
Cheers, Jeff McNeill http://seoindochina.com
300 chars
300 characters is just perfect! More than that is just spamming and not needed.
140 is fine. its easy to read
140 is fine. its easy to read and understand message.
I voted 140 because of the
I voted 140 because of the SMS standard, it is of interest to anyone who wants to tie it to an SMS broadcasting service.
Warning + Automatic selection of services
Keep 1000 as char limit. If char limit is crossed, automatically ask for subject and post to blog(if configured, else, just disallow).
If not crossed, allow to keep typing, but keep warning like this :
" 15 more to fill 4 tweets/SMS
295 more to fill 2 facebook statuses
440 more to switch to blog mode."
What is Identi.ca being used for?
While the 140 character limit works fine for publishing short thoughts (microblogging), it seems that microblogging services such as Identi.ca are in a large way being used for conversations and discussions where 140 characters simply isn't enough.
When I solely used Identi.ca for microblogging, specifically pushing out interesting thoughts that occurred to me, I had no issues what so ever with the 140 character limit. However, once I started getting into discussions the 140 character limit got on my nerves.
In most if not all cases I only really need about 20-30 characters more.
Perhaps Identi.ca isn't the proper medium for conversations and discussions, but that is exactly what it is being used for right now, if you want to separate these forms of communication from microblogging then, without making things harder, something new has to be thought up of.
Best regards,
Bruce
Time Management – The Pomodoro Effect
Try to understand and convert Ur characters to seconds http://www.mclemons.com/blog/?p=16
Be Compatible
I feed my identi.ca to twitter an other services as well (Facebook for example). I need at least a charcount for messages. So I'm with Bob Jonkman, feel free to go unlimited, but help users who need/ want to send their messages to other services (which have limits) as well.
What I do not like about unlimited messages:
Microblogging is about Microblogging...unlimited is called blogging.
size
If it can be configured automatically to take the excess amount & supply a URL for that, so that it's consistent with Twitter, then the larger the better. If not, stay with 140.
The ultimate answer was in a proposed answer.
If you look with a good eye at the numeric value 420, you can easily spot a '4' and a '2', who are the two components of the holly answer to the great question about life, universe, and other random things.
280 is a good number
140 is too short for a message, 280 is fine, more that this number is excessive and boring
140 + 260
Keeping the #hash tags and urls in the text is important i think because
its usefull to read and find #information. My idea is to show a ------- line when you are over 140 Chars in the input box and allow a max of 400 while hiding the other 260 chars by default (body)
- there could be an option in the profile to change the default view for followers.
this way you are compatible to Facebook, you can still say its mircoblogging and you are able to add more information + have a simple header/body system.
wich allow the writer to seperate between most important and lesser important information.
140+urls?
I voted 280, but that was before I read the "140 but URLs are attached as metadata not counted" idea... that really seems like the way to go.
--Susan
280 as a start
I always found the limit of 140 stupid. It really does not increase the quality in the sense of less is more. In fact people rather link to larger texts than to write it down. So most information is not in one message. 280 is good because we just double the length and can see how it works out. I am for implementing a setting so that people can set the length shorter than the default. Some might even want 70 characters. If you count the numbers please take into account that those who vote for more than 280 might actually prefer 280 over 140 characters. If we want we still can increase the value if we see the effects.
333
333
e.g http://swisen.com/
Think about languages outside 'your' English?
I am all the way with Damien Clauzel's comment.
I encourage people to consider the problems some people in the world have, who do not know or still have not learned the modern "lingua franca" (yes, English).
If you speak more than 'just English' and it's not Japanese or old Latin (no whitespaces back in their days and still a very efficient lingo) you stumble very early on to the limits of 140. Consider the message having a link and or another name you want to mention and you are having a hard time to make a point.
Short, but not too short
#limit280 looks a good compromise: it forces messages to be concise, but at the same time gives enough space for information.
URI take space, and a lot of languages (French or German, for example) are less concise than English. Don't forget that identi.ca is not monolingual!
Language weights
That's not so obvious.
According to http://meta.wikimedia.org/wiki/List_of_Wikipedias_by_sample_of_articles (look at "Weight" column in the table; it's based on an excerpt of the Bible) most of the languages are actually more concise than English or within a +/-10% range.
The study is not very thorough or precise but gives some information on the subject.
poll : character limit on identi.ca
I think the 140 character limit used to be appropriate for microblogging (this is not blogging !), but now the message often includes one or several @username, !group, #hastags (not to mention URLs) so the real message is reduced to a few words. It is not enough.
I vote for excluding the @username, !group, #hastags and URLs from the count (maybe put some limit on @ ! # also otherwise spam could take advantage of it)
Excluding URLs from the count would allow full URLs to be used (shortened URLs are not lasting).
Then, keep the 140 character limit for the message alone.
For those wishing to repost to twitter, i don't know what become now the @ and ! groups and # internal to identica ? either skip them or as suggested, automatically cut the total message in 2 or 3 parts of 140 to ensure interoperability. the URLs remain a problem to repost (some exceed 140 alone) so urls shortening may be necessary on repost. Anyway, do we really need twitter ? ;-)
Unlimited and meta-data
I'd like the opportunity to post longer items in order to better communicate an opinion without having to go to another service to do that i.e. link to a blog post.
I agree the 140 char limit is actually a good thing and helps keep things 'focused' however if we (author & community) could annotate dents with meta-data such as unlimited comments, extra hashtags and so on then the 140 chars would be able to also serve as a summary or introduction and then the reader could, at will, browse the meta-data and view specific items of interest.
Adding filters for meta data browsing would also be useful.
the
the shorter the
140 characters should be enough for anyone
Famous last words?
I think that SMS compatibility is still important at least for the next few years (the number of people I know who don't roll an Android or iPhone is the majority).
M
140 characters should be enough for anyone
How about if 140 is enough for everyone who is twitting from a phone, and for the rest, using the computer could type just a little more? I think that would be neat.
140 chars hide/shorten urls
I believe that we should stick with 140 and not have urls count towards the characters and/or shorten all urls by default. This is a "microblogging" service so 140 chars it should be. If it was a blogging service then unlimited is the way to go but that is not the case.
All URLs are shortened by
All URLs are shortened by default.
I rather like the size of Facebook messages. The microblogging going on there is still microblogging. I mean if you give people a small box to type in they aren't going to write a blog in it. I didn't even know that Facebook had a limit really. The choice isn't between unlimited and 140 after all...
If the poll was still open, I'd have said 140 BUT...
...it would be much better if meta-data like @username & #hashtagtags were counted outside the 140.
It's good for me to keep the verbiage down...
Just a short answere
ACK
The poll is still open!
However, we've already received a vote from your IP address. You could always vote from a different address -- but as Evan said, just expressing your opinion in the comments here, or on Identi.ca, is fine too.
Using IP address to identify voters
"we've already received a vote from your IP address"
So, the poll only allows one vote per company? Per library? Per school? Per family?
Good thing I got my vote in before the other 10,000 rabble behind this IP address. Especially the 9,999 who disagree with me.
--Bob.
(C'mon, IdentiAdmins -- you've got the best programmers on the planet working there. Surely there's a better way than IP address to limit ballot stuffing.)
That's the way this poll module works
We're using the default poll software built into Drupal, which we use for the status.net home site.
If the poll software isn't working for you, there are at least 3 other ways to express your (or your 10000 friends') opinions about character length.
Under no circumstances are we diverting important development effort to devise the perfect Drupal polling system.
That's not what StatusNet users want us to do.
280
Well, this is not exactly a 'blog'. The original 140 or 280 is more than enough to share few words with the world!
I vote for 255 characters.
I vote for 255 characters. It's 1.82142857142857 longer than SMS, but not overly long. It's not a simple multiple of 140, but who cares? 2**8-1 is a byte size message length for all to enjoy!
420 or unlimited
At first I was leaning towards 420 (that's how I voted), but after reading Exador23's reasoning, I think we should go unlimiited.
The micro- in microblogging doesn't have to mean that everything is done with less characters. It's also about minimalism in terms of "ease of use, knobs to twist". I am not about to have a blog plus a microblog, as I have nothing I want to separate and segregate out as a blog.
If you like short character limits, by all means, use them! If you don't like longer-winded people, don't follow them! Let the market (in this case, your micro-society) work it out!
I vote for unlimited (site admin limits as they see fit), with outbound limited to some system configurable amount, where dents are truncated and a link appended, all under the limit. This allows admins to choose SMS or Twitter compatible, Facebook compatible lengths, etc. Let the application that bridges the two apps deal with the length as well as the embedded link to point them back to identi.ca.
The sky is not the limit
I voted 140, and here is why (and I think it's important for everyone to be cognizant of why people will choose certain limits):
There is a marked tendency for people to mix everything into one big mushpile, whatever format or app is used for any sort of communication. You see this on discussion boards all the time for instance, where most people simply will not stick to the topic at hand. They are always bringing in their pet peeves/raves, etc. There is no intent towards the least self-discipline -- because, after all: who has to? Here, we see the same logic at work: people clearly intend to send full emails, etc., in a medium which is intended first and primarily for cellphone SMS. And so while it is good and proper for you to put this up for democratic duscussion and vote, it would be a complete mistake for people to actually vote to shoe-horn in emails-full of info, into a system fully geared to sending 140-character datagrams. And no more.
Upping the limit will simply wreak havoc on the intended goal of this service -- whether we use it from the Web, or otherwise. Keep it at 140 characters. If people want to send emails to cellphones -- let them use some other software. You can't please everyone, and you can't be all things to all people. Be what you are, and do what you are good at -- and no more. Remember UNIX/Linux? Remember what Microsoft actually means..?
nonsense
Think about the term "microblogging". It's mere nonsene to expand the limit. Why? Becasue if I want this, then is use something like a weblog aka "blogging".
140 and URL shorteners
Getting the URLs completely out of the messages would bring a few important improvements. The character limit would seem a lot less arbitrary because it could be roughly based on the length of a normal sentence. Also, it could put an end to the necessity of URL shortening services. These services go in the opposite direction of making meaningful URL for the Web. Finally, moving the URLs out of the message and into the meta-data would allow some clients to use some UI abstraction (i.e. a link button), or not display it at all, like for Ubuntu notifications [1].
[1] https://wiki.ubuntu.com/NotifyOSD
The brevity of these status
The brevity of these status updates is what makes microblogging unique. Instead of increasing the character limit, I would change the system so that posting a URL doesn't count towards the 140 character limit. Just my 2 cents. :)
I understand people's
I understand people's frustration with "arbitrary" limits. But longer-form posts is what blogs are for. Besides which I like the idea of having universal standards. As "status updates" establish themselves as part of the fabric of internet communication, they need to be clearly defined. I voted 140.
Besides which, 140 is less arbitrary than you may think:
http://www.techcrunch.com/2009/07/04/short-is-sweet-postcards-begat-sms-...
interesting article. thank
interesting article. thank you. Friedhelm Hillebrand was pretty close. If you plug 160 into the scatter diagram here http://ur1.ca/l1g3 it scribes a line from a 32 word sentence on the left axis to 23 on the right axis. That's roughly the 70% point. 80% is the ideal from Pareto's principle. that happens closer to 170 or 180. then you need to add room for metadata instead of subtract it. The postcard example is also interesting, but it's one-way delayed communication. When you're communing with the real-time stream, being at the 80% point is important to minimize delays from reconstructing sentences or going the slightly quicker route of abbreviating and dropping vowels. Meanwhile the conversation has moved on while you were doing battle with the limit.
I personally like 280 because that makes it easier to notice when the counter hits 140 if that's where you want to stay for whatever reason, versus the 160 oddity that comes with 300c. I have noticed that quotes in the 280-300 range start becoming less readable and/or too ambitious. going beyond 280 has diminishing returns in other words. I'm not opposed to a higher limit, but it starts generating the deleterious effects many are concerned about.
140
140 is best way to keep it tuned with twitter. Can we have twitlonger or something for identi.ca?
I voted 280 but I like
I voted 280 but I like restriction on principle; forces me to be concise. If I want to ramble, well, I have a blog for that.
300 or 420
I've voted for 420, but 300 would be fine too. I'm annoyed of having to abbreviate words and make sentences less readable just to fit an arbitrary, way too small, limit, and would already have switched to Brainbird if I knew how to reply to people on Identi.ca from there.
+1 on 140+
I vote for #limit140+; 140 characters shown, with longer decks hidden in an AJAX-y fashion; it'd be like Identi.ca would have a built-in and integrated TwitLonger.
1000 just like del.icio.us comment...
When bookmarking with del.icio.us, the limit for comment is 1000 and I find very convenient for putting a small abstract plus some comments. 1000 seem to be a good balance.
voting
I will likely to continue a self-imposed 140 limit no matter the outcome, but voted for 280. I like small/short/brief for the reasons others have noted.
I like the brevity of 140, but if it is frustrating to others, then I say increase it a tad. Spirit of giving, you know? 280-300? Not significant other than the pleasure of numbers.
That said, anything over 420 is too much. :-)
Complete solution - The best of all suggestions
Unlimited, so we can say more and consequently use less our blogs.
If we use AJAX, we can have a clean timeline, and with some extra features, as AJAX-ly display images and other special contents.
When updating to Twitter, we can use two tweets if message have less than 240 characters, or post the two first lines and a permalink to the full message if message have more than that.
With the new HTML5, we can via AJAX, direct display videos and audio, so user dont need to open a new tab.
Ajax + Unlimited + HTML5 = Wide possibilities
Say Hello to the Real World
I didn't realize folks were commenting here. I should say my peace.
"New technological environments are commonly cast in the molds of the preceding technology out of the sheer unawareness of their designers." ~ Marshall McLuhan - Take Today: The Executive as Dropout (1972) [140c, 205c with full attribution]
I came to my >140 position by way of real-world data. I started quoting, in part, to hone my brevity skills. what I discovered is brevity has nothing to do with 140. brief, concise, powerful quotes are often >140 characters.
This study http://ur1.ca/l1g3 looks at sentence lengths in newspaper articles. please take a gander at the scatter diagram and distribution charts. An average sentence is 148.8 characters ~before adding any punctuation~. [really (mean word length + 1 for space) x (mean sentence word count) - i'm not a statistician]
Factor in meta-data (@username, #hashtag, !bangtag, http://ur1.ca/xxxx, attribution etc. (62c for this generic example)) and you realize that fewer than 1/3 of the sentences in that study would fit in 140 characters under typical microblogging practices.
140 came about because of SMS - an expensive technology not directly supported by identica, and destined for the bit bin with the advent of smarter and smarter mobile tech. Even so, it doesn't work - I have SMS enabled for DMs on twitter - invariably they come to my phone as two SMS messages, not one.
Why people would conflate brevity with twitter heritage tech is beyond my comprehension.
"Environments work us over and remake us. It is man who is the content of and the message of the media, which are extensions of himself. Electronic man must know the effects of the world he has made above all things." ~ Marshall McLuhan - Take Today: The Executive as Dropout (1972) [217c/283c]
Lets look at those effects: bad grammar, horrible sentence structure, dropped vowels, real-time flow of conversation is interrupted to edit for length (often resulting in dropped vowels), ambiquity, generalizations, questionable tone leading to unnecessary arguments, etc. etc.
In a nutshell, microblogging at an arbitrary limit instead of one ≥ the magical 80% point is dumbing down conversation. Does the world really need to be dumbed down more than it already is??
"In most people there is a deeply seated fear that prevents us from taking control of our lives and shaping them to suit us. It is a fear that keeps us average, keeps us doing all the same things everybody else is doing, simply because it is the familiar thing to do." ~ Meredith Keeney [287c with attribution]
I can't help but think sumbunall favoring the status quo do so without a grasp on what a real definition for brevity would mean, coupled with a general fear of the unknown.
to those fearing "people will become verbose","my screen will fill up", "i won't be able to scan my stream" and similar "the sky is falling" outcomes... Please, take a deep breath, then look at the public stream of brainbird with it's 300 character limit: http://brainbird.net/
To those fearing "it will anger my tweeps"... I occasionally bridge from brainbird. Not a single person on twitter has complained, in fact, when I've been in conversations with people there, they've gone to twitlonger to be able to match the edge given by brainbird's character-fu. And because my posts are truncated with a link, it drives traffic to brainbird, and I've fielded several questions regarding what brainbird/statusnet is all about.
On the other hand, I have had people on identica complain when I forwarded quotes to the first group I started on identica - group q. I think the complaints were less about the length of the quote and more about how it gets truncated, with a link to the full quote. Quite frankly it chaps my ass that I now can't access the group nearest and dearest to my heart, here in my self-exiled omb ghetto. to see what you've been missing: http://brainbird.net/group/q
To those fearing "look what happened to jaiku," bullshit! we've lost a lot of people to Friendfeed, which has a huge limit. Facebook has a 420 limit and millions of users (many of whom access it via mobile tech) - way more than twitter. In fact, I think plurk, twitter, and identica are the only viable microblogging platforms that are still in the dark ages. nice company - NOT.
Brainbird.net/exador23 is where I will remain until the limit is at least 240c - allowing for the possibility of just one single coherent, intelligent sentence. Is that too much to ask for? Life is to short to spend it butchering language to meet some rule made up by a company we all hate anyway.
Peace,
steve.
Well said
@exador23 makes a compelling (to me) case for raising the character limit for identi.ca
To me, Facebook is a strong existence proof that a higher limit [420 chars] than Twitter's 140 chars does not produce a lot of very long posts.
A new limit in the 280-420 character zone would be OK/Fine.
Just do it already. ;)
Exactly!
You hit it!
I changed my vote to #limit500 for the following reasons:
1) Why follow Facebook's when we can set and start our own standard micro-blogging length?
2) There is no point going less than Facebook's 420 character limit.
3) If the third-party cannot handle Identica's 500 characters, the message gets truncated into a URL like BrainBird's
4) It promotes Identica (and StatusNet, and FLOSS, for that matter) because Twitter and Facebook users will surely click on that URL to read the WHOLE, UNcannibalized, and WITH Sense message.
It is not up to us as to how each user will use the 500 characters limit. But as was said by many, there are other factors that eats up character space - "RT", "@{putsomelengthynamehere}" + another "@putsomelengthynamehere", the RT'ers own reactions, + the original message of course, plus some shortening URL that isn't really short when you think about 140 characters.
I vote #limit500 as maximum and #420 minimum. No more and no less. Let them follow us, not us following them.
Very well said indeed. 140
Very well said indeed. 140 characters really just is too short for coherency. Thanks for the interesting statistical link.
Microblogging is micro
What sets microblogging apart *is* the very tight character limit. I voted #limit140.
There are zillions of weblog applications and services for people to choose if they want to be more verbose. The great thing about microblogging is that *every* post is short, so it's possible to get it at a glance.
Identi.ca should remain a microblogging site, with the 140 character limit.
I voted "Unlimited", but in
I voted "Unlimited", but in fact I think 300 should be fine _IF_ the URIs don't count in the character limit.
Accept 1024, but only show
Accept 1024, but only show the first 140 in timeline (reveal the whole message AJAX-ly if the user wants to see more).
140 UI
I voted for 140 because, while I try to exclusively post via identi.ca, my dents get relayed to Twitter. Hopefully someday that will change.
If the limit *does* go up, please do something in the UI with the character counter so one can see when a dent passes the 140 Unicode character (Twitter) limit. I would not want to be sending split dents. That would be ugly.
140 chars with continuation
It is already possible to link a followup post to the one it's continuing: click reply to yourself and then remove @yourname, replacing it with an ellipsis (or someone else's @username, if you're continuing a reply).
I think this has an advantage over limit280 in that users can choose where to make the break for federating/twitter-bridging. You do, however, lose 3 bytes/chars per dent to the ellipsis, but you can still spill over into a third post if needed.
Ellipses
Counting Unicode characters and not bytes you can easily replace three dots with the single ellipsis character "…" ;-) [AltGr + .] or [Compose-Key . .] on the standard ubuntu qwertz layout.
The power of 2!
I voted 280, but I'd prefer 256, as the SMS multiplier is meaningless to me. And a little more room would be nice for full URLs instead of shorteners, and for @people_with_really_long_user_names
140+inf.?
I guess it'd be good to make it 140 (header, always visible) + infinity (body, hidden by default). I don't like to have 2 or more blogging sites, I'd like to speak short when needed, but not need to create another account elsewhere when there's something more I have to say.
140 plus tags and URLs
I voted 140, but after reflection, what I'd like is 140 char and the group tags and urls don't count to the total. For SMS and forwarding to 140 char services split it into as many as required (probably only one more, but...)
140 characters + URL
URL shortening removes too much information. There can be separate field for one URL - this is the common case.
Tags are generally short and OK to be part of the message
I voted for 280. I like the
I voted for 280. I like the general brevity of 140, but sometimes it's too short to contain even a single element/thought without resorting to some crazy abbreviations, so I think 280/300 would be an improvement.
It'd be even better if there could be a visual indication to make sure you know when you type past 140 characters, given that's the lowest common denominator.
How to vote on the poll
I wasn't able to vote on the poll. So I have to have an status.net account? An Identi.ca one is not enough?
Anyway, I prefer 280, but 300, 420 would be fine as well. Too many options might divide the ones that vote for increasing the limit, when some would be ok with any limit bigger than 140.
Voting issues
Not at all! You don't need any type of account to vote. You should see the poll box above these comments (or try the separate poll page). If you still can't vote, please let us know exactly what problem you are having.
voting issues
I enabled a session-only cookie for status.net sites, and it seems I'd be able to vote again today, in a new session. That's what I'm assuming, anyway, based on the fact I can see the voting options again instead of the polling results.
The point, though: for anybody who is trying to vote and can't: try allowing cookies, then refresh the page and see if that helps.
OMB
A further comment - whatever limit is selected, even if it stays the same, the OMB protocol needs to take the fact that there are differences in settings on different servers, and either allow discovery of the limit when sending to a remote server (so the message can be truncated, for example), or handle the same at the receiving end.
Currently Brainbird truncates all its outbound OMB at 140, so identi.ca can accept them. It has no way of knowing that my server will happily accept 300, so I get them truncated as well.
On 140, 160, 280 and 300
Nobody ever seems to get this, although I say it every time character limit discussions come up.
When you receive a message, you have the originator's name, some separation, (e.g. ": ") and then the message. Thus, I am pretty sure the 140 limit originated from that fact that you need to fit ALL this into 160 characters for it to fit into an SMS.
StatusNet complicated this by a) allowing excessively long usernames (twitter limits to 15), and b) supporting unicode properly from the outset. Nonetheless, the reasoning behind 140 remains. If you have a 160 limit, then messages will overflow the SMS limit just by virtue of the fact that the username is added.
For this reason, 280 is a silly option. If you follow the logic above, you will see that you don't want to double the 140 to fit it into two SMS messages, since you're then allowing for having the username twice. Thus, 300 is the correct way to fit it into two messages.
However, as I said above, this is all kind of irrelevant for StatusNet, with super long usernames (http://identi.ca/ohwellnowyouonlyhaveseventyfourcharactersifyouwanttores...) allowed. Any message that character (now renamed) sent would overflow an SMS if it was longer than 68 characters.
Anyway, all that aside, I voted for 300 because I like it, and it's compatible with both Brainbird and my own server. ;)
Unlimited is actually kinda interesting
I tend to follow or stop following someone's stream based on its content, which is in part how concise they can be. Making someone communicate a complex idea broken up into 140 character bursts isn't as useful as them just taking the time to spell it out in 400 characters. However, most folks will still probably do under 140 characters.
I think that on our internal installation I am going to turn off the limit, and observe how we use it. Sometimes it is definitely useful to have StatusNet act as forums for us as well as quick updates to each other.
Less is more, but could clarify some things
I agree with people saying less is more and would like to maintain the minimal haiku-like posting (not about the service). But it would be more enjoyable sometimes we can say just a little word more. Just a little bit. i voted for 280, but maybe it's an excess.
And, i think too we need more threading. I like redenting other people's thoughts, but i'm not a parrot to must saying exactly what they do. It would be nice if editing the dent, status.net stills accounting who makes the original dent and started all that meme-ing.
Said that, i love identi.ca. It's clearly an all in advance to twitter.
Unlimited! But only for comments
I like much the Jaiku/Qaiku model, i.e. 140 char for a post and unlimited (or very huge) for the comments. This help to develop very interesting conversation, without loosing the main advantages of microposts, IMHO...
Regards,
Marco
+1
+1 :)
that sounds perfect! @replies
that sounds perfect!
@replies should be longer than normal post (as most clients filter @replies nowadays and only show original post in the timeline).
I think this would make identi.ca even more useful!
More urgence than the char limit : anti-spam & anti-redundancy
I voted for 140, but anything less than 420 would be okay for me. But, I think there are more urgent tasks to achieve before enlarging the char limit.
1) Please, make the anti-spam fight more easy and more responsive.
2) Please, make all that is possible to avoid dent redundancies. The microblogging platform should strip off ! and # with any redent features. (People should not redent into the same group/tag, but could be able to redent a notice into another group/tag, or redent a notice from group !foobar into hashtag #foobar
3) Please, look at the mobile version and strip off there what is not really important, and what should not appear in every page viewed. The size of the mobile version should be compressed into less than 20% of the actual size.
The point is: I don't want to be fed with 3 spams of 420 chars / 12 urls, 7 re-dents of the same thing again and again, 6 mis-grouped discussions (discussion about apple in !linux group) in a total of 20 last feeds.
Responses
1) I'm not sure how much easier than "click a button to flag a profile" things have to be.
2) If you use the built-in repeat functionality, repeats are not re-distributed to groups. No, we're not going to strip anything out of notice content; that's a recipe for disaster. But we can control what we do with the syntax.
3) I think the mobile interface is really slim right now. What do you see that needs to be trimmed further?
Spammers
re #1: put a flag option on the subscriber list. I can usually tell a spammer just by the username and info so I don't need/want to click through to their profile to flag them.
140 - less is more
140 for me but not for compliance with SMS or the legacy micro blogging platforms.
Yes, there are plenty of times, I am forced shave a space character or lose an entire word to fit within 140 which is irritating but brevity is all.
Even now, occasionally (and I freely admit it's occasionally at the moment) I see truncated posts from Brainbird - with a link to the full post - and guess what, I never click through as I simply can't be bothered.
However, if the site wide limit was increased on status.net, I suspect occasionally would turn into frequently.
Micro blogging is spontaneous, it's for the moment - if you want to write essays, try Tumblr or Posterous.
Less is more.
140 or unlimited ... is this conversation or not?
I am torn between 140 and unlimited.
First of all, I really don't think it matters, whether the limit is 140, 160, 480 or whatever. I think people who are asking for more than 140 are in my opinion living under the illusion, that if they had a more space, they wouldn't hit the limit that often. I think it is not so, Parkinson’s law [http://en.wikipedia.org/wiki/Parkinson%27s_Law] has no mercy and it has no exceptions. “Expenditure rises to meet income.” and so if the limit changes average length of messages will grow proportionately and authors will hit the limit as often (if not more often) as now.
So, in my opinion, the question is whether we should have the current limit or no limit whatsoever. And here the answer lies in what is the primary intent of status.net. If the primary mean of communication should be just sharing status messages, then I guess the limit is OK, but it seems to me that more and more communications tends to degrade (evolve?) into two-way communication over multiple messages (especially supported in my opinion by things like identichat, where my identichat MUC is indistinguishable from any other Jabber MUC) and then the limit is pretty tiresome.
So, what is the primary mean of communication with status.net. Chat or statuses?
140 - makes it a newsticker
The main strength of identi.ca is for me that all messages are short and informatic. That makes it a kind of community newsticker.
If you increase the limit, then messages will get longer and I won't be able to get them at a glance anymore.
Unlimited, but maybe on a separate site
I voted 420 for conservative reasons. Why not ratchet it up to the length of a Facebook status and see how that works?
But ultimately the best feature of status.net to my eyes is the federated nature of it. I keep thinking, why the hell can't every non-micro-blog everywhere do the same thing? And of course they can but don't.
I'm not really in favor of sending dents as multiple tweets though; I'd be happier (and I think that it would support the site) if the tweeted echo of the dent were simply the first 120 characters of the dent plus a link to the dent on the originating site.
My 2¢
Want +140? Use BirdBrain!
I voted for 140.
I think it is part of the charm of microblogging. And even if we don't have the most robust SMS support at the moment, we shouldn't break the SMS barrier.
If you want more characters, go to BirdBrain or a similar site. That's the beauty of OMB!
160, Please
I think that 160 characters is the SMS standard, at least in English.
That sounds like a good compromise.
Anything > 140
Screw the legacy Twitter crap. 140 is too small of a place to think. Not all the time; sometimes it's alarmingly perfect. I just want the option to go over once in a while. 280 is fine, 300 is fine. Anything over 420 might be a little on the obese side, though. But I think it's time to ditch this arbitrary limit.
Microblogs, not Microsentences!
140 is just too short. 280 fits into existing schemes well. I would be ok with 300 or 420 too but I feel they are starting to get a bit too long and will cause the 140-lovers to riot. Some sort of threading syntax would be probably be the most peaceful way to fix this. Adding a "+" sign as the 141st character seems to be a good way.
Unlimited
It would be interesting to see how many people actually use a microblogging service with SMS. No, an Identi.ca client on your iPhone doesn't count.
There is no technical reason to limit the size of a message. Those who want to be brief can be brief, those who need more characters to dent a quote with attribution and a URL can do so too. Those who don't want to receive long messages can close their eyes after 140 characters.
Services that support only 140 characters can get multiple dents.
Feature request? Allow a user to limit the number of characters on RECEIVED messages. To target the largest possible audience, senders will have to keep their message short.
I wrote a simple messaging app on a PDP8 in 1978. It allowed 4 lines of 80 characters. It wasn't enough then, either.
--Bob.
limit on received messages
That's a fine idea, but right now we're just discussing site-wide limit.
"Allow a user to limit the
"Allow a user to limit the number of characters on RECEIVED messages. To target the largest possible audience, senders will have to keep their message short."
+1
Give us a syntax to do
Give us a syntax to do "threading" between messages, or reply to specific messages other users post, and leave the limit where it is.
SMS has 160 chars
but don't count R[D/T]:, http://, @, !, #, ♻
How about a 1400 character
How about a 1400 character minimum like woofer?
Dent limit
Identica is a microblogging service. It is not Blogspot or Wordpress.
I'd be fine with leaving the limit at 140 characters. But I voted 300 because I discovered recently that the complete URL of an attachment counts toward the limit for a dent. I had a dent that was rejected because I attached a photo.
My personal selection would be 250, which is PLENTY for what we all use identica for. But leaving the limit at 140 would also be fine by me.
SMS? & Limits
Evan, are there any stats on the number of people that use SMS messaging? I ask, cause just like BUGabundo 300 in brainbird is good, 420 is good too, but is there anyway to limit the viewable area to 140 unless someone clicks on the dent or clicks "in-context" ?
300 or 420
as u know i'm used to 300 in BrainBird, but i can accept up to 420 too.