This is good. Plus with the move to open source tr.im it's only going to strengthen your position. Keep it up.
LOJAC
· 3 months ago
I have always used tr.im by default. It looks professional and makes sense. If I had to use any other, I would choose is.gd, u.nu or something else before I would ever use bit.ly!
spatical
· 3 months ago
This will be very helpful and simplify our Twitter apps.
The one other request I have for the API is making it available over an SSL connection as well. My online app runs mostly on https and SSL would keep both the credentials encrypted and allow us to do jsonp calls to your API without any Security warning in the browser.
I would even be willing to donate towards a couple of thawte SSL123 certs or something like that. SSL is one thing bit.ly hasn't implemented yet either.
Please try these again. I have reconfirmed everything. There has been some disruption as we separate tr.im from Nambu, but this is behind us now.
scascot
· 3 months ago
Just tried to tr.im a link within Nambu, and it get a "Request Timeline Failed. Reason: *blank*" error.
poke
· 3 months ago
Now both urls show the "UP!"; the shorten API method works however. But I would prefer continue using the trim_url.xml one because I prefer working with XML data..
Eric Woodward
· 3 months ago
This is finally resolved. I am sorry this went for this so long.
scascot
· 3 months ago
Now getting "Request timeline failed. Reason: Forbidden (403), Twitter understood your request, but is refusing to fulfill it" from within Nambu when attempting to tr.im a URL.
:-(
Edit: It appears that KTVB.COM (local TV station website) is blacklisted as spam on tr.im. This makes no sense to me.
Eric Woodward
· 3 months ago
I have removed that domain name. Thanks for reporting that. As for those errors, are timeouts to Twitter, not tr.im. Not much we can do about Twitter's never ending problems with DDOS attacks.
scascot
· 3 months ago
Maybe I should clarify - I was receiving that error message after pasting in a URL, and hitting the shorten link button, BEFORE attempting to post.
Edit: I guess I don't understand why Nambu would pass the request to shorten a URL through Twitter to tr.im, thereby generating that error message, instead of contacting tr.im directly. *shrug* Maybe that's why I'm not a programmer.
poke
· 3 months ago
Yes, it seems to work fine now, thanks :)
gacott
· 3 months ago
I'm, amazed at the lack of comments. I think this is one of the biggest things to happen to open source for quite some time. I think the releasing of tr.im to the community is huge.
So how is the progress in the transition?
Eric Woodward
· 3 months ago
It is going fine, actually. There are some ugly spots still to refactor, but overall it is going as planned. There are not many projects like tr.im that will run in open for everyone to see how it is implemented, and help add features if they so choose.
Lopo Lencastre de Almeida
· 3 months ago
By the way. Tr.im is made with?
Eric Woodward
· 3 months ago
tr.im is Ruby on Rails to a MySQL backend.
Lopo Lencastre de Almeida
· 3 months ago
Only comparable to Laconi.ca (now StatusNet) as a compatible FOSS replacement for Twitter.
while http://api.tr.im/api/trim_url.json?url=http%3A%... returns {"trimpath":"y9PX","reference":"BttQ5bXZwYZO384H03qrDVaeMGt0fT","trimmed":"2009-09-08 06:52:30 -0700","destination":"http://google.com/","trim_path":"y9PX","domain":"google.com","url":"http://tr.im/y9PX","visits":0,"status":{"result":"OK","code":"200","message":"tr.im URL Added."},"date_time":"2009/09/08 06:52:30 -0700"}
Anonymous
· 3 months ago
I don't know enough to play with an api myself, but is there any chance you guys could throw up an igoogle gadget? The only way I can access twitter at work is via igoogle (plus it's handy for passing on links from my reader account etc which are all on the one page) and the url shortener gadgets already available there are garbage.
HealthCareOz
· 3 months ago
I am having trouble authorizing my Twitter A/c's - HealthBrand & HealthCareOz, Please advise
Many thanks
Michele
Voyagerfan5761
· 2 months ago
It's true that mimicking an existing API from the field you're trying to break into is one way to make it easier for people to adopt your service. However, who's to say bit.ly has the best response structure? ;-)
Good news, though. If other services follow your lead, it'll make it easier for shortening services to compete on the basis of features rather than who has the easiest API.
Anjanesh Lekshminarayanan
· 1 month ago
I like tr.im. But please try providing branding options - like we can using Short Links service in Google Apps. I would really like to use tr.im's service under my own brand like mydoma.in
All Comments
The one other request I have for the API is making it available over an SSL connection as well. My online app runs mostly on https and SSL would keep both the credentials encrypted and allow us to do jsonp calls to your API without any Security warning in the browser.
I would even be willing to donate towards a couple of thawte SSL123 certs or something like that. SSL is one thing bit.ly hasn't implemented yet either.
:-(
Edit: It appears that KTVB.COM (local TV station website) is blacklisted as spam on tr.im. This makes no sense to me.
Edit: I guess I don't understand why Nambu would pass the request to shorten a URL through Twitter to tr.im, thereby generating that error message, instead of contacting tr.im directly. *shrug* Maybe that's why I'm not a programmer.
So how is the progress in the transition?
http://api.tr.im/api/trim_url.json?url=http%3A%...
returns
json_callback(null)
while
http://api.tr.im/api/trim_url.json?url=http%3A%...
returns
{"trimpath":"y9PX","reference":"BttQ5bXZwYZO384H03qrDVaeMGt0fT","trimmed":"2009-09-08 06:52:30 -0700","destination":"http://google.com/","trim_path":"y9PX","domain":"google.com","url":"http://tr.im/y9PX","visits":0,"status":{"result":"OK","code":"200","message":"tr.im URL Added."},"date_time":"2009/09/08 06:52:30 -0700"}
Many thanks
Michele
Good news, though. If other services follow your lead, it'll make it easier for shortening services to compete on the basis of features rather than who has the easiest API.
I would really like to use tr.im's service under my own brand like mydoma.in