Loading Profile...
Bit.ly links are posting to Twitter as "u.mavrev.com"
Instead of using the shortener that I chose (Bit.ly) my feed is posting to Twitter with "u.mavrev.com" links.
I’m frustrated
16
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?I have the same problem. Out of 3 posts, 1 was URL shortened by bit.ly, 1 bu mavrev and 1 by a third service.1 Comment
Add a comment
This solves the problem
-
My problem has been solved, with the new TwitterFeed UI and using the API key. Perhaps it's RTFM but in any event I'm happy. -
Inappropriate?I have the same problem, and I am trying to use the bit.ly api to track my stats... I have configured it with the long api key supplied by bit.ly but it still doesnt work..
of course the API is a secondary problem first the links actually need to be shortened by bit.ly
Thank you!
I’m sad
-
Inappropriate?This is done because TwitterFeed could not shorten the link using Bit.ly, and instead went to the next shortener in the list - In this case urlShort (u.mavrev.com) to ensure a working link was tweeted. I recall reading that at some times Bit.ly's API is very picky about user info, and that the solution was to just remove and reenter it.
1 person says
this solves the problem
-
1 Comment Add a comment
This solves the problem
-
There isn't any way to stop TwitterFeed from using a secondary shortener (right now) because it's doing that to ensure your feed content is tweeted in a way that is still usable. I could be wrong, but there isn't anything you can do. You'd have to wait and hear from @mario to be sure though.
-
Inappropriate?If you're using your own API key and the issue happens all the time (rather than just every now and then), then it's most likely there's a problem with the bit.ly API info you used - bit.ly can be fussy about this, e.g. upper/lower case etc., so try and make sure that this exactly matches what you see in your bit.ly account page.
If the error is intermittent, then it's most likely a temporary problem, where twitterfeed didn't receive back an "OK" and shortened link from the bit.ly API, so it then goes and uses a different shortener in order to be able to post a link at all.
1 person says
this solves the problem
1 Comment Add a comment
This solves the problem
-
I know you're busy this month, but this really needs is a "test login" option. Without being able to view the password (which would be a security hole) there's no way to tell if the bit.ly login is entered correctly until I post the next blog entry.
-
Inappropriate?This is a big issue for me too. It would be closer to OK if there was a disclaimer saying the connection to bit.ly does not always work well...I am expecting some tracking info on my links and can't get it now :(.
I’m a bit annoyed
1 Comment Add a comment
This solves the problem
-
If you'd rather have your links either be bit.ly or nothing at all (and lose any traffic to your stories) then I'm sure Mario can do that.
Stop being a dick about it. The reason Mario did this is to ensure that your content is tweeted, even if the service (bit.ly in this case) fails or is unreachable. Plus, it's not like you're paying for Twitterfeed - It's free. Maybe you should read the terms (http://twitterfeed.com/terms), specifically part 4.
"THE SERVICE IS PROVIDED BY BETAWORKS AND ITS LICENSORS "AS IS" AND "AS AVAILABLE." "
Bit.ly is not Twitterfeed's responsibility. If it isn't working, it has to move to another, or not tweet your content. That's the hard truth of it.
Sorry if I sound like an asshole for this, but I don't like when people complain about free services, especially when reasons for problems have been stated dozens of times. -
Inappropriate?Yes Twitterfeed was originally done on a shoestring, but now there's VC and it's going to be a real company. If you're trying to be a real company -- whether or not you charge -- then you need to fix bugs, or people will go to a competitor. Maybe this isn't the most serious bug in terms of its consequences, but clearly it is a bug that is often seen and that is important to a number of customers.
Until a bug is fixed, a programmer only has a working hypothesis as to why a bug happens. Bit.ly works reliably with a manual human login, so perhaps the bug is with bit.ly or perhaps it is with TwitterFeed. Since bit.ly is losing traffic, it has an interest in helping to fix the bug. When I worked with other software companies to chase incompatibilities, I found that at the engineering level they were curious to find out what was wrong and (if their managers let them) spend time investigating how to fix it.1 Comment Add a comment
This solves the problem
-
The thing is it isn't (from what I've seen/read) a bug. It has purely to do with establishing a connection to bit.ly to shorten the URL. If their server is unreachable at the second the request is sent, then Twitterfeed assumes there is a problem, doesn't try again, and goes on its way. I may be wrong, but it doesn't seem to have any pattern (aside from people who incorrectly enter their API info) in failing. Mario would be the one who would know, but it certainly doesn't appear to be any kind of pattern, especially when in some batches of 5 entries to shorten, 3 work and 2 don't (someone posted about this here). It definitely isn't consistent at least.
-
Inappropriate?This is the official bit.ly tech support answer
If your bit.ly account isn't working, then it can't match up to your api key. Try one of two things - either log into your account via recovering the pw for it with our lost pw link when you are logged out, or create a new account. Once in there, reset your api key and then put the new api key that is associated with your bit.ly account into the twitterfeed settings.
It doesn't seem like an intermittent bug, since the past 12 postings to my blog went through mavrev.com (many of them posted after midnight when server load is likely to be pretty low).1 Comment Add a comment
This solves the problem
-
The reason they go to urlShort (u.mavrev.com) is because it is next in the list after bit.ly, for whatever reason. As far as the timing goes, I've just looked at urlShort's stats and there isn't any clear point of low traffic because quite frankly not everyone is in the same time zone, and the internet doesn't sleep. Maybe I'm alone in thinking that it isn't a bug in software of either Twitterfeed or Bit.ly, and that it's rather just quite simply a connection error but who knows. Us going back and forth isn't going to change it. Someone from Betaworks may though.
-
Inappropriate?There is something more deterministic about this bug than people are assuming.
I have 2 blogs that always post through mavrev and one that always posts through bit.ly, even though the TwitterFeed is configured to send all through bit.ly. I've re-entered the bit.ly login just to make sure.1 Comment Add a comment
This solves the problem
-
If it continues to happen, could you contact me directly at mario at menti dot net with the bit.ly API info, so I can test things manually.
-
Inappropriate?I have the same problem but just updated my bit.ly API on Twitterfeed. Hopefully, this will straighten it out. Either way, the other u.mavrev.com works, and like Matt says (although maybe not as diplomatically as he could have), it is a free service so I'm happy with it.
I’m confident
1 Comment Add a comment
This solves the problem
-
Yeah, I'll admit, I was acting like a dick. Hopefully your bit.ly links will work now, and it isn't just some other issue. Cheers!
-
Inappropriate?It seemed to work after I mentioned it here, but now that I've mentioned it again, maybe it will stop working. The Murphy rules of the universe? I hope not. :)
I’m kidding
-
Inappropriate?Are you using the API KEY or the password?
I had the same problem and solved it using the API KEY to post to twitter.
You can get your API KEY from http://bit.ly/account
EMPLOYEE
