We are not affiliated with MyToday

Lately, I am getting so many emails/comments/scraps complaining about MyToday.

Pavan started it, and then me and many fellow bloggers posted about how MyToday can be used to get scraps on mobile for free.

It seems like being a free service MyToday reached its limitations and they are failing to handle high volume of traffic.

Some users complained that they failed to get SMS in time while some other said they never received any SMS at all!

Tired of answering each of them separately, I have decided to make it clear by a post. So please note that we, orkutfeeds, are not affiliated with MyToday in anyway and can not be held responsible for quality of service they offer.

Our job is only upto serving valid RSS feeds. So if you can see feed content in normal browser we are done. Whatever you do next with other third party services, is beyond our control.

Please do not mistake this with any sort of arrogance. I just want to make clear few things which are affecting us… 🙂

Rest you can always contact me if anything goes wrong with our orkutfeeds! 🙂

Orkutfeeds User Guide [Documentation]

Usually documentation is the first thing done when launching a service. But being lazy and busy, I delayed it so long.

Actually most bloggers covered many details so I was never bothered in first place to write a manual. But for the sake of formality, the user guide is here.

I know documentation means a much longer and boring thing but as of now bear with it. I will write bigger docs in future.

As of now, added a small section – geeky notes, at the end which may be helpful if you are planning to (ab)use orkutfeeds programmatically… 😉

If something needs to be changed, corrected.. please feel free to comment! 🙂

Link: User Guide

Orkutfeeds is more stable & reliable now!

Although I said last night that community & topic feeds were back, they were keep breaking throughout the day…

So what I did is know separated code for all 3 types of feeds viz. scrapbook, community & topic feeds. The major advantage of this separation is increased reliability.  So as an example, if something goes wrong with scrapbook feeds in future hopefully it will not affect community & topic feeds.

Also I made some major changes apart from separating codes. These changes basically to correct minor bugs which pops out whenever orkut makes small changes to their original code. But this will not result in any disruption of service anymore.

Thanks for your patience… 🙂

Community & Topics feeds are taken down for maintenance. Sorry for inconvenience!

From evening (around 10 hours) I am receiving emails/scraps regarding problem in the feeds.

There is some problem is session management code which will take more time to figure it out.

I am using SVN here so I am reverting everything to old version where we didn’t have any support for community & topic feeds.

I thought its better than keeping whole service down in maintenance window.

So enjoy only scrapbook feeds for a while…

Once again, Sorry for inconvenience! 🙁

p.s. in between I will try to keep up community & topic feeds, but can not guarantee anything till next post!

Resolved – Community & Topic feeds are working again!

Just resolved community & topic feeds duplicate items issue.

Sorry all for inconvenience. 🙁

Please don’t get annoyed if something goes wrong again. Just contact me via comments/email or anyway as per your convenience.

This is my first project in PHP as well as in public domain so it will take some time for me to fix codes…

I am tried like hell now… so to all commentators, I will post my reply tomorrow!

Sorry again….

Good Night! 🙂

Open Issue with community and topic feeds…

Sorry for all community and topic feeds subscribers. If you are using Google reader then you may be annoyed with duplicates items…

Just saw this new issue while leaving my PC. Will fix in it in next 24 hours.

Sorry for inconvenience… 🙁

Thank You Darnell for First Donation…

Thanks for Donation

It has been more than a month since I have started OrkutFeeds. Since then this service received lots of support & appreciation from many fellow bloggers. But what I was missing honestly a review on insideorkut by Darnell Clayton – biggest authority on orkut.

Well the review by Darnell is here. And one step ahead to show his appreciation & support for this service he also donated to Orkutfeeds… 🙂

Now on this nice occasion I want to highlight something very important for orkutfeeds users. I was asked one question over and over again… “Whats your plan to monetize orkutfeeds?” or “Whats your business model?” or something like this only…

Everytime my answer was same and simple… First orkutfeeds is not a business to me. I always referred to it as a service. Its my payback to all orkut users for their love and support which helped me decide what to do with my life!

Technically yes, orkutfeeds is bandwidth incentive service and may burns hole in my pocket in future. But I am optimistic about few things…

  • First I am planning some major optimization to codes in June. They will bring down bandwidth requirement considerably.
  • I hope more generous people like Darnell will come forward to help.
  • My professional blog will generate some extra bucks to feed orkutfeeds…
  • Orkut will come up with this feature officially one day…

Still question remains why I am not advertising here to make some extra bucks. Although some feed advertisers showed interest in putting ads in feeds generated by orkutfeeds, I am not comfortable with this idea as the content in feeds are not written by me. I feel its evil to advertise on someone else’ content.

Next I also don’t want to clutter homepage of Orkutfeeds. In fact I am trying my levels best to help orkut user get feeds without ever visiting homepage! 😉

Now remains this blog. First this blog have no large readership. Next this is not a commercial blog. So I feel its contradiction to make money from a blog which is about a free service!

Finally orkutfeeds idea is not mine. The original idea was by Vikas and contents are by orkut user. So I feel its evil to make money by just coding for few nights on someone else idea and content!

So bottomline is, orkutfeeds will remain ad-free and if something go wrong in future I will release the codes in open-source so that people with spare bandwidth can host orkutfeeds on their servers!

Also I will try to give more time to OrkutFeeds now on. It has a long to-do list pending here…

Thanks again Darnell for being first donor!

Image Credits – “Thank You For Your Donation” by Shamufilth (via Flickr).

We are back… Sorry for downtime!

First I apologize for long downtime of almost 24 hours!

Act when I noticed it yesterday for the first time, I thought like previous time orkut server was down so ignored it for first few hours.

Act there is one similarity between last weeks and yesterdays downtime – Script was working fine on localhost i.e. my machine in India but failing on DreamHost server in CA, US!

Also I use SVN for my all codes so I am quite sure about changes getting synchronized properly everywhere!

Anyway this cud only justify 2-3 hours but what next! Next thing I did I went home (I was in office while conducting above tests) and worst was waiting for me. My SMPSs fan was jammed so system was experiencing thermal shutdown! 🙁

So it took me a little longer as I have to fix codes from my office. So everything is working fine now…

But I am still wondering why it went wrong in the first place! I mean it never stopped working on my localhost then why it went into problem on DreamHost servers???

My only conclusion from this fix is for CURL team. CURL is great without doubt but it should have handled cookies more transparently!

Anyway as a user of orkutfeeds, all I can promise to you… Never get panic if you see our DOWNTIME error message in feed! That only means things will working back soon. Do not unsubscribe! We will let you know that too either, if in feature we choose to quit permanently…

Update by Devdatta: If you have noticed my scrapbook content when you were expecting your scraps, then sorry again. I made a foolish mistake. All should be well now! (atleast… gush) 🙂