fearphage's dashboard

Jeff's reply to "I hate ow.ly" was just promoted to the most useful! fearphage and 2 other people think it's one of the best replies.

Hi all,

We've just rolled out an update to ow.ly that lets your followers choose whether they want to see the ow.ly social bar or not.



See the drop-down to the right of the close box? If you click that, you'll see a checkbox that says "Always hide the ow.ly social bar on this machine."

If you click that checkbox, any further visits to ow.ly links will redirect you straight to the target URL.

The bar itself is also much improved -- it's thinner, has a built in Twitter search tool and "most popular links" area, and allows spiders through (so your pages get all the Google juice they deserve).

Thanks for the feedback, everyone.

A comment on the problem "I hate ow.ly" in HootSuite:

Another alternative is to point them to a better URL shortening service. – fearphage, on April 28, 2009 15:33

fearphage replied on April 28, 2009 13:26 to the problem "I hate ow.ly" in HootSuite:

Here's a script I made that removes the frame in an extreme fashion (for chrome and opera). There is also a script for firefox, safari, and ie as well but it still fully loads the ow.ly pages unfortunately.

Enjoy!

A comment on the problem "I hate ow.ly" in HootSuite:

Well I'll have to resolve this myself I see. http://tr.im uses URL redirects AND they provide click statistics. There are alternative solutions. – fearphage, on April 28, 2009 10:07

A comment on the problem "I hate ow.ly" in HootSuite:

I think you're missing the point. The end user should be in control of their experience, not the person sending the link. – fearphage, on April 28, 2009 06:22

fearphage replied on April 26, 2009 06:53 to the problem "I hate ow.ly" in HootSuite:

This was filed 2 months ago. Any updates on how and when we can permanently full-frame redirects instead of the frames?

fearphage started following the problem "I hate ow.ly" in HootSuite.

fearphage marked one of Dave's replies in DevHub as useful. Dave replied to the problem "Opera is blocked from the editor for no reason".

fearphage replied on February 20, 2009 18:59 to the problem "Opera is blocked from the editor for no reason" in DevHub:

If you upgrade jquery, you will notice it also no longer relies on browser detection:

http://docs.jquery.com/Release:jQuery...

Also, would you mind adding Opera to the homepage of supported browsers?

fearphage reported a problem in DevHub on February 20, 2009 08:14:

Opera is blocked from the editor for no reason

The opera browser (http://www.opera.com/) is blocked for seemingly no reason. If I add firefox to my userAgent, I can get to the editor and all works fine. Why did you block a fully functioning browser from your site? Browser sniffing and browser blocking are old school. Get with the times. Object detection not browser detection: http://www.quirksmode.org/js/support....

A comment on the question "What characters make Twitter messages truncate?" in Twitter:

more sample posts:

http://twitter.com/fearphage/statuses...
http://twitter.com/fearphage/statuses...
http://twitter.com/fearphage/statuses...
http://twitter.com/fearphage/statuses... – fearphage, on September 24, 2008 15:24

fearphage reported a problem in Get Satisfaction on September 24, 2008 08:37:

html entities should not be converted in messages

When I type "& lt ;" without the spaces, that is precisely what I expect to be displayed. I don't need ou to convert it to the less than sign for me. As a test, below what is on the left side of the equals sign (=) is the same as what is on the right but without spaces:

& = & amp;
> = & gt;
< = & lt;
"e; = & quote
< = <

When I type something, that is what I expect to see when I submit it unless bbcode or wikicode is involved. It is damaging for you to convert these characters auctomatically.

fearphage started following the problem "Conversion of characters to HTML entities is ruining tweet display" in Twitter.

fearphage replied on September 23, 2008 23:40 to the problem "Conversion of characters to HTML entities is ruining tweet display" in Twitter:

This is a real issue. < is one character not 4 (<). If i write 138 chars and the last one is a < or >, then twitter will see it is over 140 chars. Also if you type & lt ; (without the spaces) in twitter it converts them to the encoded chars. what in the world?

fearphage replied on September 23, 2008 23:39 to the discussion "Tip from Tantek: Less than, greater than chars ('<' , '>') cost 4 characters not 1" in Twitter:

This sucks. THere is a reverse to this error as well. If you type & lt; without the space, twitter converts it to the less than char (<). That is just idiotic. I don't get it.

fearphage started following the question "Please bring back Twitter AIM!" in Twitter.

fearphage reported a problem in Plurk on August 14, 2008 23:07:

User profile pages are invalid XHTML

There are 9 errors on the user profile pages with the worse being nested anchor tags around user created links. There are two images missing alt attributes and you repeat the use of the id "show_all_friends". Also the inline blocks of js need CDATA tags around them.

w3c validator results

fearphage started following the question "Is it possible to share the todo list with other people ?" in Todoist.