Timeline for URL should not count towards a comment's character count
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 21 at 11:32 | comment | added | Federico Poloni | Hello from 2024! Google's link shortening service goo.gl is scheduled to shut down in one year, and links will rot. | |
May 18, 2023 at 19:49 | comment | added | Alexander Guyer | @AaronBertrand Whether comments are meant to be permanent or not isn't the point. People treat them like they're permanent all the time. Many thousands of "unanswered" questions actually do have trivial answers posted in the form of comments. Treating those comments like they're disposable or temporary seems antithetical to SE's brand---sharing useful answers to useful questions. Some useful comments lean on external references, and I'd expect those comments to live at least as long as those references. | |
Jun 5, 2017 at 12:36 | comment | added | iBug says Reinstate Monica | I think it's best to count by "actually displayed" character number. So a plain URL will still count as many but a URL with titled text will only be counted for the title text. | |
Feb 1, 2015 at 20:34 | comment | added | Aaron Bertrand Staff | @Vincent again, it shouldn't matter. Comments aren't meant to be permanent. If you fear your comment will outlive a service like bit.ly, then post an answer instead. | |
Feb 1, 2015 at 20:33 | comment | added | O0123 | As for the URL shorteners, I just have the (maybe ungrounded) fear that they will expire at some time + if a given URL changes over time, the heuristic work to find back data (e.g. using data from Wayback Machine, would be made more difficult? --- Are my reasons to think this justified? | |
Feb 1, 2015 at 20:29 | comment | added | O0123 |
@AaronBertrand - I know too little of big data to understand the point (I guess, you might correctly make) about the cost and troubles coupled with expanding of the database columns. --- On the other hand, I think, from the viewpoint of the non-changing final readability and compactness of design and thus (at least in that sense) the unjust punishment of the end-user (who just happens to link to a long URL), ought to be avoided. --- My comment is also meant especially for [anchor text](URL) 's, as is inspectorG4dget's comment above.
|
|
Nov 26, 2012 at 0:49 | comment | added | user7116 | @AaronBertrand: twitter? Yes-ish (search is blocked). Facebook? Yes. Social Media? Yes. Link shorteners? Yes. Image hosting sites? Most (I got the SE imgur CDN whitelisted). Welcome to corporate and medical America. | |
Nov 25, 2012 at 15:44 | comment | added | Aaron Bertrand Staff | @sixlettervariables your workplace actively blocks every link shortener on earth? Sorry but that seems short-sighted (no pun intended). Do they also block twitter, facebook and all other social media? Twitter is a place where URL shorteners are quite useful regardless of what type of device or computer you are using. 140 characters is still 140 characters. | |
Nov 25, 2012 at 15:34 | comment | added | user7116 | @Aaron: link shorteners are almost universally blocked at two of my places of employment (for good reason too, they don't serve a constructive purpose for non-mobile devices). | |
Nov 25, 2012 at 4:51 | comment | added | inspectorG4dget |
I just realized that it's important to mention that I'm talking about using URLs in markdown like so: [anchor text](URL) , and not just pasting them in the comment
|
|
Nov 25, 2012 at 4:39 | vote | accept | inspectorG4dget | ||
Nov 25, 2012 at 3:56 | history | answered | Aaron BertrandStaff | CC BY-SA 3.0 |