Category: Service Updates


Mr Tweet Now Updates Daily

June 17th, 2009 — 7:53am

If you have been using Mr Tweet recently, you would have noticed the many UI improvements that we have been making in response to the user feedback we have received. In addition to those changes, we also recently did an upgrade that many users have been asking for - daily updates!

Over the next few days, we will be migrating all users over to this new schema. If you have not been migrated yet, you will see a link at the top allowing you to speed up that process. 

Mr Tweet Now Updates Daily

Users will recall significant scaling problems that prevented us from service our users as often as we would have liked. We invested March and April into developing a new backend that allows us to move forward much more quickly. While we cannot promise that these scaling issues will be a problem of the past, we will always try to keep up with the needs of YOU!

Users can of course sign in from MrTweet.com. If you have not received your DM yet, please head over here instead!

Comments | Service Updates

Explaining Service Disruptions (Part II)

April 15th, 2009 — 6:00pm

* Before we go into the nitty gritty details of these disruptions, would first like to offer a huge THANKS to YOU for being so patient and supportive as we work on making it even better for you!

Hi folks! Over the past month or so, we have been working hard on a fundamental redesign of our backend infrastructure. This new design will allow us to scale capacity to to serve you folks consistently, as well as facilitate even better discovery.

Because of our focus on this, there had been quite a few things that fell through the cracks. We are very apologetic to all our users, and we would like to explain what these are, and what we are doing to resolve them!

1) Suggestions were not being updated on time

The #1 comment that we receive is that suggestions are not being updated every 2 weeks. The reason is because we have not been able to keep up with the user growth we have been experiencing!

Resolution: If your list have not been updated in 2 weeks, you will have the option to update it manually. Just go to your homepage, and click on “Request Update!”

2) Slow Page Loading Times

Over the past 2 weeks, we have tried several methods to make the pages load faster. However, due to our uniqueness of the type of service we are providing, these methods typically used by sites to improve performance did not do much for us

Resolution: There is no quick fix here. =( However, page times will become much faster after we complete the rehaul mentioned at the start of this posting!

3) Slow Response to Users

This is the one non-product aspect that we feel really bad about! In the early stages of MrTweet, one of the things we tried very hard to do was to reply to every tweet and feedback that came in. However, the number of tweets and feedback grew exponentially at the same time the number of challenges we needed to tackle on the product front grew as well. Hence, we fell behind pretty badly,

Resolution: We are putting in more processes and manpower to make sure that we continue to respond in a timely manner that YOU deserve!

Again, would like to give a big THANKS to everyone for being so supportive so far… please rest assured that we are working hard to fundamentally improve the service for you!

Comments | Service Updates

Annoucing Bi-Weekly Updates

January 21st, 2009 — 8:34am

Very happy to announce that we have fully implemented the most commonly requested item by our users: Regular updates of their MrTweet service!

Note: It has been running for a while now, but we wanted to wait until we were sure we could deliver on a good service before announcing it. Yup, we are different that way. =)

Why take so long to announce it?

1) Lots of scaling to accommodate new users: Thanks to enthusiastic word of mouth and press, we had a constant flood of new users coming through. We were at work stabilizing and making the service faster for everyone.

2) Time to listen to feedback: We listened and talked to many users about what they liked and not like, especially with regards to how well the suggestions worked for them. Not perfect by far, but we feel we moved several steps in the right direction.

3) Evaluated new data-sets: 1) To determine the most important factors when it comes to updates. 2) To come out a reasonable idea of when there is sufficient change to warrant an update.

lolcat_fix 
Working hard behind the scenes to fix things up for you!

How will the updates look like? Do I need to learn anything new?

Nope, we designed updates such that the simplicity that you folks loved is still the same. =)

1) Receive a DM: When your update is ready for you (you will only get a DM for the first update, and not for subsequent ones)

 image

2) See a dashboard: That looks very similar to your first dashboard, with the emphasis that the suggestions are based on your latest activities and changes in your network.

image 

3) Get Refreshed Lists: Suggestions are ranked based on your most recent activity. Also, the indicators above the numbers on the list shows you whether this entry is new, promoted, or demoted.

image

Note: we are going to allow you to permanently allow you to remove people from your list 

We need your feedback to do better!

User needs (see this) are very diverse. This space of people discovery is very new space. As such, there is no 1 formula that works, and your feedback is the only way to improve. As such, please give us lots of it via comments on this blog post or our getsatisfaction forum.

What is next?

Besides working on more relevance and UI improvements, there will even more interesting items coming through. Stay tuned via subscribing to our blog via email subscription on the right!

Comments | Service Updates

Addressing Privacy Concerns

January 5th, 2009 — 12:35am

There is an current uproar happening these days over Twitter’s lack of security for it’s users. The phishing incident, selling of Twply within a week after launch (giving credentials to the unknown buyer), and the Twitterrank debacle earlier all foster a deep sense of doubt and lack of trust.

As one of the participant in this ecosystem, we want to share our thoughts with regards to this issue. We will touch on how this has impacted our product design, why we are in this for the long run, our plans, and why you cannot really blame Twitter.

1) We designed Mr.Tweet such that you do not need to provide your password

First and foremost, you do not need your password to use MrTweet. You just follow us like you would follow anyone else, so that we get DM you.

if you are a heavy user, you can follow easily in a single click. For users who perhaps intend to follow just a few, feel free to click on the name, and you will go to a new window with the user’s Twitter page.

follow  
No need to give us your password to use the service

passwordnopassword  
Click on the name to follow directly from Twitter. Again, no password required.

Of course, we would love a world whereby everyone trusts us, but we highly advise all users to be careful about who they provide their credentials to, and that clearly includes us.

Honestly speaking, there are a few features we are looking at that we think would kick total ass, but would require password authentication.

2) We are in this for the long run. Your trust is paramount.

We have invested lots of effort in developing the discovery technology behind MrTweet, and we are extremely happy for the reception we have received and the value we have added so far. It will be dumb for us to break that.

The fact that we are in this for the long run is also the reason why we invest a lot of time in our sharing our thoughts in  blog postings, contributing back to the developer community, and communicating with users. We also share a lot of our internal beliefs in interviews, as per the recent one on Net@Night with Leo and Amber.

usontwitter  
This is us on Twitter. Hit us up with some nice @(s) if you have any doubts about your privacy

All in all, we try to communicate as much as we can given all the constraints. We are not going to be perfect by any means, but we try!

3) We will support authentication methods the moment it is implemented

We know Twitter is working on implementing OAuth on their site, and we will support that the moment it becomes available. That way, users can choose to provide passwords, or just authenticate using OAuth.

That said, OAuth is NOT the perfect solution. The user experience for alternative security methods still require many steps (logout of gmail and try this), and carries with them their own hazards to the user, perhaps even much more than normal.

Untitled-4  
Alternative security methods comes with their own inconveniences and hazards. Read
this article on why this encourages phishing

4) Convenience and Security are Tradeoffs, so do not blame Twitter (ok, you can, but just a bit)

When unpleasant incidents like these happen, there is an overwhelming tendency to blame Twitter for not implementing better security measures, especially for 3rd party apps. 

However, it is important to remember why you love Twitter - because of its simplicity and vast variety of wonderful applications.

Neither the simplicity nor ecosystem would not have been possible if Twitter had insisted on a high level of security right from the start. See, convenience and security are tradeoffs. I used to be in the military for a couple of years, and the first thing they taught us about security is to think of it as a door. You can leave the door unlocked, and that is the ultimate in convenience, but of course completely lacking in security.

The upside to this is that it does encourages lots of trust and convenience. When Twitter first got started, the neighborhood is a safe place, and the bad guys do not care, we loved this no lock policy. Now neighborhood is becoming richer, and the bad guys are starting to notice, so we must start locking our doors, we criticize Twitter for being haphazard about security.

In other words, please understand that Twitter’s main concern is not the engineering effort needed to implement tougher measures, it is the YOUR user experience they are most concerned about. 

Folks like @al3x and @ev are relentlessly focused on the user’s and developers’s experience, and I believe that focus is a bottleneck in implementing these!

image  
A diagram showing the tradeoff between convenience and security in biometrics. Not like I know anything about biometrics, but it looks cool.

That said, I think Twitter can be A LOT more communicative to their users. Kris Colvin has a very well written rant here. Also see GetSatisfaction where there has been no response to this problem. I believe a well written blog posting would do wonders for its users where they communicate the difficulties involved.

5) Change your passwords right now

In the light of all these, we will end with one statement. To put your minds at ease, change your passwords now, and be careful about who to give your passwords to.

Alright peeps! That is all, and again, please hit us up if you have any questions about privacy and security. I am personally reachable at mingyeow@mrtweet.net / @mingyeow / facebook. See my blog for my cell phone numbers.

Take lots of care, and rock on for the new year!

Comments | Service Updates

Explaining Service Disruptions

December 12th, 2008 — 6:05pm

 

Due to a Twitter error, our Followers list have stopped updating again since the 8th of Jan (see Disruption 1). Do ping @al3x and @ev to fix it, so we can service you folks! =)

Updates for (Disruption 1): We have received the followers list from Twitter for folks who joined between Dec 5th to Dec 11th, and will be serving all of you like, now

We listen to comments very closely on timelines, DMs, and GetSatisfaction. The overwhelming reason why users are sometimes unhappy with our service is because of service disruptions. As such, we want to explain the most severe disruptions that had occurred, and the reason they did, and what we are doing about them.

*Some errors listed below are due to Twitter, but 1) the Twitter staff  (especially Alex) have been incredibly helpful through the process, and 2) we are a “special” case because we have been working their system in so many different ways!

1) Twitter Error: Followers List was not updated From Dec 5th to Dec 11th

image

What happened: Followers list essentially did not budge as a (severe) Twitter error prevented the list from being updated.

Impact:  Folks who followed us were successful in following us, but they did not show up anywhere in our system. A couple of nice folks also had difficulty unfollowing us. HEHEHE (dream feature) *evil grin*

Working On: We are waiting for Twitter to fix the error on their end ASAP, so we can know who these followers are, and serve them accordingly!

2) Twitter Error: Approximately 900 users who signed up in a period between Nov 27 / Nov 28 did not get their DM

image

What happened: Twitter accidentally deleted a bunch of names from their developers list. Unfortunately we were one of them. :(  Hence our DMs were sent, but not received by our dear users.

“…looks like some database maintenance inadvertently truncated our table of whitelisted users” - Alex (Twitter)

Impact:  Lots of users did not get their DMs from us, even those whose reports are actually done up already. We were not aware that such a problem existed until we received lots of people who told us that they have not received their DMs. These comments usually came with a big ” =( ”

Working On: 1) Being responsive to people who complained of weeks-long delay, and sending DMs to them manually.  2) Working on identifying who these people are, and notifying them accordingly!

3) We are sorry, something went wrong….

image

What happened: There are a couple of cases whereby either we were processing someone like Jason Calacanis or Robert Scoble, each of follows about >20,000 followers, and servers would crash. Either that, or we are deploying some fixes.

Impact:  Server required an reboot. Which means I will wake @ambivalence up at 3am*

image

*Like you know, the famous 3am phone call. Only that it is a Scoble and not a nuclear disaster. Oh wait… there is a difference?

Working on:  Identifying and minimizing these errors. We put on hold folks who follows more than 10,000 people, so as not to disrupt service for the rest. In fact, we process them manually. =(

Alright, that’s all folks, hope we shared some insights into what and why these errors occurred, and how we are handling them. =)

Comments | Service Updates

Status updates on common requests and issues

November 27th, 2008 — 10:01pm

Hello Twitterverse! First off, extremely grateful for the incredibly enthusiastic welcome from everyone. We have received tonnes of great feedback on how to improve via the public timeline, direct messages, and our forum at GetSatisfaction.  We will address the most common issues here, which are:

  1. Long waiting time of generating a report
  2. Re-updating of created reports
  3. Emphasize more “Interesting People” rather than “Celebrities”
  4. Upcoming features?

We will address each of these briefly right now, and will provide an new blog posting as we move forward.

1) Dude, where is my report?

image 

Status: The average time for someone who just joined will be about 48 hours.

Why? Under a deluge of requests, we had to make a tough choice between speed of processing and stability, and we decided to choose the latter. Earlier followers might recall that we crashed after Scoble used our service, and that caused lots of inconvenience to many users, which we were extremely sorry for. After that, we re-engineered for stability, putting the high networked users (>5000 followers) on whole as we cater to the rest of the users

What is next: 1) Gross negligence of bedtime as we ramp up capacity and optimize processes. 2) Sending new users a DM with an estimate of the wait time.

image image

*For Fun: Conversation with Scoble

2) I came back everyday, but my report remains the same!

image

Status: We will update your reports again with a new set of rankings and based on your last changes.

Why not update now?: Updating is a very intensive process. Given our limited capacity, we want to make sure that we can get more folks their initial reports asap. Just as importantly, we have learnt lots about what works (and what does not), and we will need sometime to finetune and create more substantial improvements, as opposed to marginal tweaks.

What is next?: We are likely to implement a weekly update, with recommendations based on the changes for the week. We cannot promise a concrete timeline, but will be sometime Dec.

3) I do not want to see “Internet Celebs!”

image

*First and foremost, our goal is to help create meaningful relationships, not fan clubs. This is definitely top of mind for us.

What: For veteran twitterers, the feedback is that they often have to flip a couple of pages before they get to the really interesting people. Before that, they see celebs they know about already. Hence, feedback is that we should downgrade the “internet celeb” effect

Status: We already have several checks and balances to downgrade the “internet celeb” effect (finetuned thrice already), but we are sure we can improve further!

What is next: Using both user feedback and datapoints to finetune rankings that create meaningful relationships. Re-iterating, we are not out to create a fan clubs, but here to help make “marriage-worthy” matches, as Marta Strickland very eloquently pointed out.

We will get there, but we do need lots of feedback and support! In the meantime, please flip a few more pages!

4) Upcoming features?

What: There has been many great suggestions for features, ranging from ability to see your own statistics to UI improvements like checkboxes for one-click following.

Status: We have implemented some of them, but we are focused on scaling this week. We will implement somemore ideas next week, so stay tuned!

All in all, thank you so much for being such great users - we love you guys, and we are so glad we have a forum besides Twitter to communicate through! :)

Cheers,
Mr. Tweet

Comments | Service Updates

Back to top