-
I am a supporter of reducing the length of the posts. Anywhere between 250 - 500 characters should be sufficient. We already have an area where the contributor of the tip can submit the URL for further reading, so the length of the URL does not need to be counted in this limit.
commented on Feb 4 2012 12:24PM
|
-
I am also supporting restricting length of Tips in "Just Learned " section because there is reference URL is there for further detail then length up to 600 may be sufficient for this section.
commented on Feb 5 2012 11:27PM
|
-
(Just for clarification) The reference URL is not part of the tip content/text, so we are not counting it. So the length we are discussing is just the length of the tip text/body.
commented on Feb 6 2012 1:20AM
|
-
+1 sir! As you said, if the tip is long then it's not a tip - it's a blog post :)
commented on Feb 6 2012 1:36AM
|
-
My 2 cents,
I support it however it's between tweet and an average blog post so excluding the link, only tip should be somewhere between 300-350 characters. That should be sufficient to explain even quick tip/trick for programming.
commented on Feb 6 2012 7:17AM
|
-
Yes Sir, the length of the Tip should be between 200-400 or at max 500 and if it needs bigger post then we can create a post and put that post URL as its reference.
commented on Feb 8 2012 12:11PM
|
-
This definitely makes sense. There should be a differentiating factor between a short tip n a blog post. I support this idea.
commented on Feb 11 2012 2:27AM
|
-
If it includes code, will this be counted toward the maximum number of characters?
commented on Feb 11 2012 2:33AM
|
-
I support ur idea, as you said, if the tip is long then it's not a tip - it's a blog post :)
commented on Feb 11 2012 2:44AM
|
-
@Dishdy,
Yes, currently we were thinking that we will count the code also as part of the tip. In the past we had several tips that demonstrated very large code blocks. Such a tip is more ideal for a blog post.
However, we can make changes in the rule based on what the majority of people in this thread wants to have.
commented on Feb 11 2012 2:52AM
|
-
I support character limit <=500 including code, excluding reference link if there is any...
commented on Feb 11 2012 3:04AM
|
-
commented on Feb 11 2012 6:52AM
|
-
I agree with limiting the length of the tip. It should be short and to the point.
commented on Feb 11 2012 11:25PM
|
-
Limiting the size of the tip is a good thing to be kept focusing on the essential.
500 chars is nearly 3 tweets, so it seems to be not too much
commented on Feb 12 2012 5:46AM
|
-
In my opinion a character limit is an absurd notion. More information is better than less. Sometimes it takes more space to offer a tip, whether that be words or code. Nothing prevents someone from reading only the first 500 characters of a post. But a 500 character limit may well inhibit the complete thought intended.
commented on Feb 12 2012 11:23AM
|
-
I don't think we should explicitly limit the tip, but we may want to make it clear that the tip should be short. If it's longer, well, let it be.
commented on Feb 12 2012 3:57PM
|
-
I also support for tip is less then 500
commented on Feb 12 2012 11:02PM
|
-
I think, there is no need to explicitly limit the tip to any number of chars but rather we can spread this as an advice to the authors.
commented on Feb 13 2012 12:10AM
|
-
I think you should not limit the number of chars.
Instead you could have a warning when you reach 500 chars and, to be sure people care about that warning, hide the #>500 char(s) on the post until a "show more..." link is clicked.
So, when someone writes a tip with no more than 500 chars, nothing changes.
But when someone writes a tip with more than 500 chars, he's warned about it and will tend to summary his post to avoid the "show more..." "hinder".
commented on Feb 13 2012 2:17AM
|
-
I really like Sergejack's idea!
commented on Feb 13 2012 2:45AM
|