Shotbeak.com

I haven’t tested Tweekly.fm with OAuth implementation, but by the looks of it, the code looks about right. I’ll probably test it soon. OAuth won’t go live until I am able to sit by and see if all goes according to plan. Tweekly.fm updates runs on Saturday night. I won’t be here to test it and sit around to see that things go down without a hitch. So, the implementation will have to wait a week or two.

I’m also considering moving the updates a tad earlier (can’t find the link now, but Twitter slows down on the hour because of automation services). The other option I’m considering is moving Tweekly.fm to early monday morning and affixing the popular #musicmonday tag to it. It is the spirit of music after all.

I’m also thinking about perhaps purposefully lengthening the script that sends all the tweets. The influx of users looking at the userpages is seriously slowing the server. I could always upgrade the server, but I don’t have the money. Which reminds me, I’m still looking for advertisers! This past Tweekly.fm tweet-run, it got 30000 pageviews alone.

————

In other news, I’m So Nerdy is going rather well! The nerdy-ness keeps on rolling in!

————

On the music front, me and my bro have been cranking out some tunes. You can go listen to them on MySpace!

———–

That’s all I have to say for now. Cheers!

Today, I spent close to 6 hours trying to implement a workable solution to running OAuth alongside my current basic authentication for Tweekly.fm. I got close to getting it working.

Yes, OAuth is great. But it is not great when you already have userbase of basic auth users. My problem is that IF I do implement OAuth, I’d want Tweekly.fm users to come back and switch. It’s a nightmare, since Tweekly.fm isn’t exactly a service where you use your login credentials again. I’d somehow have to get all the users to come back to switch. The only thing connecting OAuth with basic auth in my system is the last.fm username. Because of the way Tweekly.fm works, I can’t run both OAuth and basic auth. So, if someone wants to switch, I have to delete the basic auth, which is just too much effort for the user. Because the way Tweekly.fm works, I might also end up deleting another person’s subscription (you can choose any last.fm username, not just your own).

All I ask Twitter, is 1 special API method. Use basic auth to get the access tokens. This way, I can easily switch my whole userbase to OAuth without them having to do ANYTHING! You can even deprecate all the other functions of basic auth. Just allows us to get access tokens if we use basic auth.

It will even drop all the hurdles to get authorization in the 1st place (go to site, click, authorize on twitter, come back). Desktop apps will like this too. This way, you keep the ease of basic auth and have the security of OAuth (switching off rogue apps). The user won’t be phased. The developers might have trouble though. Basic auth is much better to learn than OAuth.

So, Twitter, if you want to switch to OAuth, at least make it easier for us to switch existing userbases to it.

I just stayed up to check to see if the update went through successfully (added some optimization, not much though).

Unbeknownst to me, in my slumber, Tweekly.fm was trending on Twitter. I never saw to what point, but it trended none the less! Here is some evidence of another great milestone.

http://twitter.com/twitscooptrends/statuses/2158416986

Tweekly.fm now grows with about +-200 users every week. Now that it started trending, it will probably reach the tipping point. Next time this week, Tweekly.fm will have more than 2000 listeners sharing their favourite music!

—-

There are still some features that I am going to implement. The biggest one, is adding OAuth support. Twitter hasn’t really made it easy to switch, so instead I must develop a way, to take yourself out of the old database and onto OAuth. Will take some time.

Thanks for using Tweekly.fm.