<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for toddml</title><link>http://disqus.com/by/toddml/</link><description></description><atom:link href="http://disqus.com/toddml/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 16 Nov 2010 08:57:06 -0000</lastBuildDate><item><title>Re: Bit.ly Introduces Bundles: Multi-Link Sharing With One URL</title><link>http://mashable.com/2010/11/15/bit-ly-bundles/#comment-97808151</link><description>&lt;p&gt;Alex, you can add/remove/rearrange links once you've created the bundle, and there's a handy box at the top of your bundle creation page that allows you to search through your history to find links, or paste in new links that you haven't previously shortened.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Tue, 16 Nov 2010 08:57:06 -0000</pubDate></item><item><title>Re: Bit.ly is Harmful to Your Reputation</title><link>http://cranialsoup.blogspot.com/2010/04/bitly-is-harmful-to-your-reputation.html#comment-49138023</link><description>&lt;p&gt;Todd from &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; here.&lt;/p&gt;&lt;p&gt;From day one, we've prized security, transparency, reliability, and openness at &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;. Along the way, we've made a number of product decisions based on those tenets. Among those are link permanence (link destinations don't change once created), the avoidance of anything that interferes with user experience (we've never framed, nor will we), and a dedicated focus on spam and malware detection, so that our users can click on &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; links with a high degree of confidence.&lt;/p&gt;&lt;p&gt;We take our responsibility as internet citizens seriously, and you'll see this exhibited even in the small details of the ways in which we manage flagged links (you'll notice we never actually disable a redirect, and at most simply insert an interstitial which retains the end destination link).&lt;/p&gt;&lt;p&gt;In the course of analyzing content for spam, malware, and phishing attacks, we rely on a number of systems, both internal and external. Over the course of the past year, a number of spammers have attempted to use various levels of indirection through redirectors (some of which are reconfigurable), in order to obfuscate and cloak their efforts. In fact, the bulk of shortens to &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; coming through other URL shorteners have tended to be attempts to spam the system. While our crawlers do of course follow links through redirections, the inclusion of modifiable redirects in the stream, and our analysis of the preponderance of spam attempts via these vectors have made it necessary and appropriate in some cases to block the URL shorteners.&lt;/p&gt;&lt;p&gt;Just to reiterate, the only goal is and always has been to protect the end user clicking on &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; links, regardless of the link source. Given that multiple layer wrapping of URL redirectors tends to be an edge case based on inappropriate API usage, confused users, or in the preponderance of cases, attempts to spam, we think this has been a fair approach. As such, you'll note that we did in fact update our interstitial warning pages with language better reflecting the reasoning behind the status. We're happy to see a healthy, vibrant, shortening ecosystem, and have no intention whatsoever to put a damper on other sites in the space.&lt;/p&gt;&lt;p&gt;Some have suggested we simply not shorten URLs already pointing to 3rd party short URLs. While this is a potential possibility, our API responses and the innumerable clients and scripts that use these methods aren't currently designed with this state in mind. Consequently, any changes would have to be carefully considered.&lt;/p&gt;&lt;p&gt;As with any product, &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; is a work in progress, and we're always interested in finding ways to best serve our users, while maintaining the integrity and openness of the product.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Sat, 08 May 2010 23:15:33 -0000</pubDate></item><item><title>Re: shortening issues</title><link>http://blog.bit.ly/post/436893007#comment-39774709</link><description>&lt;p&gt;This may just be a side effect of additional bot filtering.  Please send details of any problems you may be having to support @ &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Mon, 15 Mar 2010 14:38:53 -0000</pubDate></item><item><title>Re: Bit.ly Responds to Goo.gl and Fb.me With Custom URL Service</title><link>http://mashable.com/2009/12/14/bitly-pro/#comment-25821357</link><description>&lt;p&gt;You can preview any &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; url (and get realtime stats) by adding a + to the end of the link.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Tue, 15 Dec 2009 00:12:38 -0000</pubDate></item><item><title>Re: Announcing bit.ly Pro</title><link>http://blog.bit.ly/post/284009728#comment-25818083</link><description>&lt;p&gt;You can always use &lt;a href="http://j.mp" rel="nofollow noopener" target="_blank" title="http://j.mp"&gt;http://j.mp&lt;/a&gt; , powered by &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Mon, 14 Dec 2009 22:51:15 -0000</pubDate></item><item><title>Re: Spam and Malware Protection</title><link>http://blog.bit.ly/post/263859706#comment-24963974</link><description>&lt;p&gt; Hi Madaco,&lt;/p&gt;&lt;p&gt;We've flagged this link as malicious.  In the future, you can send any problem links to abuse@bit.ly&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Sun, 06 Dec 2009 17:34:35 -0000</pubDate></item><item><title>Re: Preview bit.ly Links in Tweetdeck</title><link>http://blog.bit.ly/post/101079199#comment-24592756</link><description>&lt;p&gt;If you go to the "Services" tab of your Tweetdeck Settings menu, you'll see an option to add your &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; account name and api key.  If you do this, your links will begin to show up in your &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; history.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Wed, 02 Dec 2009 09:17:12 -0000</pubDate></item><item><title>Re: Summary Bit.ly Stats</title><link>http://blog.bit.ly/post/242811319#comment-22931987</link><description>&lt;p&gt;Yes, all of that is in the works. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Fri, 13 Nov 2009 15:34:31 -0000</pubDate></item><item><title>Re: History Upgrades and File Uploads</title><link>http://blog.bit.ly/post/202557277#comment-18558291</link><description>&lt;p&gt;It's coming, stay tuned. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Mon, 05 Oct 2009 09:04:06 -0000</pubDate></item><item><title>Re: History Upgrades and File Uploads</title><link>http://blog.bit.ly/post/202557277#comment-18305810</link><description>&lt;p&gt;"Each image you upload must be less than 1.5 megabytes in size. If it&lt;br&gt;is greater than that amount, your image will be optimized for internet&lt;br&gt;use. Flash files will be rejected if they are over 1.5 mb. Video files&lt;br&gt;must be less than 50MB and they will be automatically optimized by the&lt;br&gt;ImageShack toolbar before uploading."&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Fri, 02 Oct 2009 14:48:06 -0000</pubDate></item><item><title>Re: Overnight bit.ly Database maintenance</title><link>http://blog.bit.ly/post/166706372#comment-15265252</link><description>&lt;p&gt;History should be working normally.  Please try clearing your cache.  If you have continued issues, please email support@bit.ly so we can help you further.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Sun, 23 Aug 2009 13:43:27 -0000</pubDate></item><item><title>Re: Overnight bit.ly Database maintenance</title><link>http://blog.bit.ly/post/166706372#comment-15147203</link><description>&lt;p&gt;No worries.  We do our best to keep our users happy, and we take that responsibility seriously.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Thu, 20 Aug 2009 17:20:49 -0000</pubDate></item><item><title>Re: 301working</title><link>http://blog.bit.ly/post/159843105#comment-15062276</link><description>&lt;p&gt;the support email is simply support@bit.ly .  You may simply have a cache problem.  Try flushing your cache and reloading the page.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Wed, 19 Aug 2009 10:55:07 -0000</pubDate></item><item><title>Re: 301working</title><link>http://blog.bit.ly/post/159843105#comment-15055340</link><description>&lt;p&gt;The history reports haven't gone anywhere.  Email support if you're running into problems, and we'll take a look.&lt;/p&gt;&lt;p&gt;Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Wed, 19 Aug 2009 09:01:52 -0000</pubDate></item><item><title>Re: Weekend bit.ly maintenance</title><link>http://blog.bit.ly/post/158779639#comment-14501712</link><description>&lt;p&gt;As mentioned in the blog post, approximately one hour, at 4AM Eastern.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Sat, 08 Aug 2009 18:56:47 -0000</pubDate></item><item><title>Re: Spam and Malware Protection</title><link>http://blog.bit.ly/post/138381844#comment-13219260</link><description>&lt;p&gt;Hi Joe,&lt;/p&gt;&lt;p&gt;Your link shows up as not found.  Are you sure that was the link being passed around?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Thu, 23 Jul 2009 12:50:33 -0000</pubDate></item><item><title>Re: Metrics System Status Update</title><link>http://blog.bit.ly/post/134257153#comment-12442011</link><description>&lt;p&gt;Everything should be back to normal at this point.  Can you send an e-mail to support@bit.ly with details?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Fri, 10 Jul 2009 09:48:14 -0000</pubDate></item><item><title>Re: Historical Metrics System Status</title><link>http://blog.bit.ly/post/133539988#comment-12032237</link><description>&lt;p&gt;Hi Anna,&lt;/p&gt;&lt;p&gt;The realtime system is still working.  Our realtime metrics system only reports clicks that have occurred within the last hour, which is why you saw those numbers drop off over time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Thu, 02 Jul 2009 10:32:42 -0000</pubDate></item><item><title>Re: WARNING: Yet Another Twitter Scam Invades Trending Topics</title><link>http://mashable.com/2009/06/23/twitter-scam-myworlds/#comment-11616579</link><description>&lt;p&gt;We've blocked &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; links to the &lt;a href="http://myworlds.mp" rel="nofollow noopener" target="_blank" title="myworlds.mp"&gt;myworlds.mp&lt;/a&gt; and &lt;a href="http://low.cc" rel="nofollow noopener" target="_blank" title="low.cc"&gt;low.cc&lt;/a&gt; domains.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Tue, 23 Jun 2009 08:59:43 -0000</pubDate></item><item><title>Re: Metrics Migration</title><link>http://blog.bit.ly/post/107694580#comment-10754725</link><description>&lt;p&gt;Do you have an example?  Everything should be working perfectly fine.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Thu, 11 Jun 2009 15:09:45 -0000</pubDate></item><item><title>Re: Metrics Migration</title><link>http://blog.bit.ly/post/107694580#comment-10387533</link><description>&lt;p&gt;If you're using adblock, try disabling it on &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;.  In the meantime we'll track down the issue.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Tue, 02 Jun 2009 11:19:02 -0000</pubDate></item><item><title>Re: The Power Of Passed Links</title><link>http://avc.com/2009/04/the-power-of-passed-links/#comment-8294077</link><description>&lt;p&gt;We're working with various twitter (and other) clients to outfit their links with referral context.  Over time, you should see more applications filter into the referral data on &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; info pages.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Fri, 17 Apr 2009 10:07:14 -0000</pubDate></item><item><title>Re: Overnight bit.ly maintenance</title><link>http://blog.bit.ly/post/96992230#comment-8278552</link><description>&lt;p&gt;The window duration is specified up to one hour, but in reality we expect operations to be completed much more quickly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Thu, 16 Apr 2009 20:21:37 -0000</pubDate></item><item><title>Re: bit.ly blog</title><link>http://blog.bit.ly/post/95307408#comment-8110807</link><description>&lt;p&gt;It's been flagged as spam.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Mon, 13 Apr 2009 06:06:47 -0000</pubDate></item><item><title>Re: A Big Week for Little URLs</title><link>http://blog.bit.ly/post/93170671#comment-7899424</link><description>&lt;p&gt;Updated for attribution.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">toddml</dc:creator><pubDate>Mon, 06 Apr 2009 09:29:37 -0000</pubDate></item></channel></rss>