Evan Prodromou wrote: > Mads Kristiansen wrote: >> Just joined, so sorry if this is a recurring subject. I couldn't find >> anything about it in the archives, so I'll just take my chances. > Probably a good place to look first is the bug-tracking system: > > http://laconi.ca/trac/search?q=140+limit > > Where you'll find: > > http://laconi.ca/trac/ticket/208 >> I am getting really annoyed by the 140 characters limit for notices, > Why? Because it makes you think through what you're saying? I think > it's great to have _some_ limit, and so do most mublog users. Give it > some time; it's one of the things many microbloggers like about the > medium. >> so I just wanted to ask if anybody has made any patches to make this >> configurable in such a way that I can increase the number of >> characters I am able to post. >> >> I looked at postnotice.php and it seems straightforward to do the >> change. > You should probably know more about the system. If you think the > problem is in actions/postnotice.php, then you're probably going to > shoot yourself pretty badly in the foot. >> Is there any special reason why this has not been implemented. > When it comes up on identi.ca, users hate the idea. >> The OMB spec says that 140 is recommended, but there is no maximum to >> the number of characters - so shouldn't it be configurable (and >> default to something like 1000 characters or a multipla of 140)? > Laconica right now will bounce messages > 140 chars. So, if you config > this, you're going to cut yourself out of the OMB network. > > That said, I think it's a good idea to have it be a configurable > value. If a server receives a message longer than its own limit it > could truncate, or just store the value. > > The default will probably stay at 140 for the foreseeable future. >
To that end, perhaps it would make sense to change the VARCHAR sizes of notice columns in the DB to not match 140 exactly. It won't make a difference to those that leave the max size allowed in the code to 140 but will help those that want to increase it so they won't have to remember to ALTER the columns later. On my site, I have set the max notice (and bio) length to 512 so I made the notice and bio columns VARCHAR(512). One caveat is that in those running MySQL prior to 5.0.3, any VARCHAR over 255 is automatically converted to a TEXT data type. So perhaps set the notice column(s) to VARCHAR(255) by default? > -Evan > > ------------------------------------------------------------------------ > > _______________________________________________ > Laconica-dev mailing list > [email protected] > http://mail.laconi.ca/mailman/listinfo/laconica-dev > -- Mark Keisler Principal Software Engineer Motorola Open Source Technologies 630-329-2828 _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
