Skip to main content

R.I.P Orkut!

Does anyone remember the social networking giant of a time "Orkut"? Perhaps not many.. Though it was the most visited site in India and Brazil at a point of time in history but gradually it lost its shine to other competitive sites and web applications offering much newer and advanced features like our very own facebook.com, twitter.com etc.

Bad news for its fans and those few who still use it to send and receive scraps.. that Google - the owner of orkut.com has today announced that it will be shutting the service down.

Google Engineering Director Paulo Golgher wrote in a post on the Orkut blog. "Because the growth of these communities has outpaced Orkut's growth, we've decided to bid Orkut farewell (or, tchau). We'll be focusing our energy and resources on making these other social platforms as amazing as possible for everyone who uses them."
Beginning today, it will no longer be possible to create a new Orkut account. Current Orkut users will be able to log in, play games, and use their account like normal until Sept. 30. You have until September 2016 to export your profile data, community posts, and photos using Google Takeout.
Google will be preserving an archive of all public communities, which will be available online starting on Sept. 30. If you don't want your posts or name to be included in the archive, you'll need to permanently remove Orkut from your Google account.
Truly, 10 years of remarkable service and my first social network experience ( I was personally very happy when i completed my first 100 scraps :P )... We'll miss you orkut... 
Maybe not that much!! :P

Comments

Post a Comment

Popular posts from this blog

Testing React loader with React Testing Library

 I have came across this situation so many times where I need to write a unit test for a component pattern I have developed so many times that I can write the code with my eyes closed. BUT what about unit testing! That's something my mind thought is the best candidate to get rid of in order to store more cat memes. Even when these patterns are used almost everywhere and we write the tests for each one of them (I hope you do) but still we (it can't be just me) tend to forget them and get even more confused with those pesky `act` warnings. So I decided to curate a recipe book for some common unit tests which I come across and might be useful for future me. Happy to share the github repo and also would love to see if anyone has more such common unit testing patterns which they can add or suggest. https://github.com/Charchit26/react-testing-library-recipes Now, let's talk about the one I have coded a dozen times and still take half an hour to struggle with its unit tests - Load...
Post a Comment
Read more

Recipe for chaos in an XP team

Our team failed! We failed in delivering value to the client, value to our users as well as we failed in showing the benefits of XP - eXtreme Programming to not only other teams but our managers as well. So here I am listing some of the factors which I think lead to the fall of the project, the practices and eventually the team itself. We were quite fine an year ago. We used to pair, practice TDD, interview users frequently and release awesome features to production almost weekly. I would not go to the extent of saying we were living in perfect times, since we faced some very common problems - Some people felt that TDD made them slow. Management kept questioning whether pair programming is really "fast enough" and not slowing us down. This gave birth to some "Duct Tape Programmers" in the team. (That's a real term! Google it.) "The Duct Tape Programmer is someone who is able to cobble together software that solves the immediate problem, but witho...
2 comments
Read more

Pair Programming - Is it really effective??

So, I have been working in a "strict" pair programming environment for about 5 months now and this is the first project of my career in which I have been subjected to sit with another person for the whole 8-9 hours of the day while I (or he) codes. Also I have been pairing remotely for half of those days (half of our team is at onshore). I learnt these practices and principles while working with another vendor for the same client in Sydney, Australia. Hence, I thought it will be a good idea to share my thoughts and experiences as well as point down the things which otherwise I have to re-iterate over and over for every person looking for advice from me before starting with this practice. Note: All the points that will be mentioned here going forward are from my own personal experience and specific to the project I worked in. Though I think most of the dev community who has worked in this setup would second my opinion. What is "pair programming"? Yo...
Post a Comment
Read more