Jeromakay

I’m happy to announce this. We’ve put great energy into this, and now the OpenScore it’s live for every of the 24k businesses on the site.

What is the OpenScore?

The OpenScore is a social media alalysis result that we provide, after analyzing different elements of a business, based on the feedback we have about it. In other words, we can tell how involved is a business in the online environment, from Twitter to YouTube and lots of other services in between.

For more information on this launch please read this blog post on the official site.

Join the live web presentation

If you’re around today (28th of October) at 2 PM GMT time, just drop by to see a quick presentation and ask questions.

The URL to join is: http://www.present.ie/loopthing1. We’d love to have you there.

Cheers!
Vladimir

Now, as I was playing with Vimeo’s API, I stumbled across this video:

Now, I wonder what’s the connection between the dead animal singing and the lyrics which say “You are so beautiful…”.

LOL

Vimeo implemented OAuth support on their end, the announcement was made here.

Seems like the old web authentication methods are already marked as deprecated, however they still work 4 days later.  The deprecated methods are

• vimeo.auth.checkToken
• vimeo.auth.getFrob
• vimeo.auth.getToken

The new OAuth specific URLs are (Twitter alike):

Request Token: http://vimeo.com/oauth/request_token
User Authorization: http://vimeo.com/oauth/authorize
Access Token: http://vimeo.com/oauth/access_token

I noticed a big similarity between Vimeo’s and Flickr’s authentication API, and probably Flickr will do a switch soon as well, there’s no OAuth implementation on their end at the moment.

A thing I noticed is that the Vimeo API now requires the OAuth specific data and valid tokens which kind of forces everyone to switch to the OAuth tokens, instead of the old ones extracted via the deprecated methods.

Loopthing needs an unexpected code update because of this right after launching the authentication feature on our end last week, but I’m happy security has been tightened around the video hosting service.

Update: The OAuth specific URLs for Vimeo does not support SSL because of the improper setup of the  certificate and the weird redirects. In the best case you’ll get a 401 error with the message “Invalid nonce”.

Finding information should be easy for people. It must be accessible, fast, and flexible.Flexible, thanks to filtering.

I’m happy to say Loopthing’s search got a new dimension, it’s a lot more relevant, and it is crazy fast.

The way it works is simple: one enters the search string into the search form, selects the type of results to return (businesses or individuals) and hits the “Search” button.

The results are extracted from the database and the less relevant ones don’t show up initially, unless the user is willing to expand that list.

Here’s a sample search for the keyword branding. If you have any ideas and questions, please send them over, I’m more than happy to adjust or comment.

Summer is still with us, so here’s some fun links:

• Screenjelly – a screen capture utility, capturing everything straight from your browser
• Drunk russians yoga via Damien Mulley
• why you must hire top employees not top candidates (article)
• have you ever wondered what is your web site’s ARPU
• an european startups blog.

Ah, and in the end a Facebook fun happening:

Getting caught on Facebook by your boss whose inside your friends list is stupid, saying you don’t like your job but keep doing it, is called waste of everyone’s time – including yours.

Got to close this post with a big LOL!

If you’re getting an error like “403 Service Over Qps” or “ERR_403_SERVICE_OVER_QPS“, you’re probably playing with an API provided by the Mashery.com webservice.

Some of the sites serving their API content via Mashery are The Guardian, and compete.com. The trouble I have comes with compete.com, however, I’ve seen people dealing with theguardian.co.uk as well.

The reason why you are seeing this is probably because you are sending over too many requests in so little amount of time.  To prevent this from happening, you should check the API’s service limits, and also test it against the real possible limits, e.g. if they say 5 requests max per second, try 4 requests per seconds, the limit may be lower than documented.

This error also comes with a HTTP response code of 403, Forbidden.

Thanks for taking part of this experiment! In exchange I’ve got something rewarding to give you back, please read on.

I know you’re willing to learn more on social media and how you can apply this to your business, that’s why I invite you to  follow @loopthing on Twitter, and then submit your business to Loopthing.com.

This is it!

If this doesn’t make any sense to you, it’s OK, it wasn’t designed to. This post is part of an experiment related to this tweet.

Time for a new set of half-geek links. I’ve got some good ones this time as well, check them out:

• email marketing benchmarks based on business industry
• bash tips, for unix fans, thanks Gupi
• nice flash components
• got to love these soft looking icons
• ride the flickr bikes, great PR stunt, shitty pictures

See you next time!

This summer is being a blessing for Loopthing, the business networking platform. We just finished integrating the Twitter functionality for business profiles, and there’s few more other features integrated as well.

A sample page where twitter is the news feed page of the Loopthing company profile.

Besides the Twitter integration, we also added RSS feeds news feeds reader which also adds content to the profile page of any company joining Loopthing.

Two more other features were also integrated into the networking functionality of the site. The networks members can now upload media files (audios, videos and images), and they can also store files into the repository of each network.

I’m going to keep you posted on updates related to Loopthing, but for now, this is it! Here’s the official blog post announcing the Twitter integration feature.

Party time for 14.7 seconds