Home - Stay N Alive

House Committee Seeks to Tighten the Content You Can See in Government

Posted on July 8, 2008 by jessestay

Representative John Culberson, the Twittering and Qik’ing Congressman from my good old home town of Houston, Texas, has been on a rampage this morning about a proposed new regulation for the House of Representatives, which, he claims, will require all world wide web communications from the House floor from those in congress to receive “prior approval” from a Democratically-controlled Committee on House Administration before it goes out to the web. From the letter:

“

Official content posted on an external domain must be clearly identified as produced by a House office for official purposes, and meet existing content rules and regulations;

To the maximum extent possible, the official content should not be posted on a website or page where it may appear with commercial or political information or any other information not in compliance with the House’s content guidelines.

Any link from a House website to an external site on which the Member video is hosted must contain an exit notice.

CHA, the Office of Web Assistance(OWA), or other designated House entity should maintain a list of external sites that meet whatever requirements are established by the CHA

“

Per the above proposed recommendations, this would rule out any Twitter communication because by law, each Tweet would need to be prepended by a disclaimer, identifying it as being produced by a House office for official purposes and, as Culberson puts it, that will most likely in and of its self exceed 140 characters. Also, it would mean that any Congressman wishing to use a site such as Twitter to share publicly what is going on in Congress with their constituents will have to get prior approval, censorship essentially, before using such a site or technology.

I find it ironic that it is a Republican that is trying to show the Democrats how to use technology on this, but Representative Culberson has a point here, and we need to speak up if we’re to continue seeing social media propagate through our government. Social Media in government means a more open government, and that’s a good thing! I’d like to encourage all that read this to write your Congressman or Congresswoman about this (Pelosi is part of this!) and get them to see things straight rather than requiring censorship of our House floor.

You can read the Proposal here. (Which, were this proposal to take effect, I believe I would be breaking the law by sharing with you)

UPDATE: Want to discuss? Let’s discuss in a nice open format right below this post via the FriendFeed link below!

Twitter Bringing Rate Limits Back to Normal

Posted on July 8, 2008 by jessestay

On the heels of a post this morning by Biz Stone, it appears Twitter is beginning to bring the rate limit for posts through the Twitter API back to the 70 per hour it used to be. For the last several months, Twitter has brought that limit down to only 20 requests per hour. Per the Twitter developers mailing list just now, Twitter has now raised that limit to 40, and will gradually be raising it back up to 70 in the upcoming week.

This is welcome news in the week of months of API and service outages. What this means is that you, as the user will no longer see the “Rate Limit Exceeded” error you may be seeing through clients like Twhirl. In regards to the API this leaves mainly just the XMPP stream that they need to re-enable for developers – this may not be happening any time soon however, as Twitter may be looking to only enable a select few developers access to the stream.

Has this request limit affected you as a developer? How about as a user?

Is Twitter Down For Everyone or Is it Just Me???

Posted on July 6, 2008 by jessestay

Just today, the New York Times did a post on Alex Payne, a “24-year old internet engineer” who created a site called, “DownForEveryoneOrJustMe.com“. This site allows anyone to type in a URL and the site will tell you if it’s just you or down for the entire web. In all it’s a pretty useful site I would think.

The article goes on to show all kinds of examples of companies that have had this issue internally and how useful this site could be. What the article did not cover however is that Payne, the “24-year old internet engineer” is also one of the lead Engineers at Twitter, a site that is very familiar with this issue.

Twitter, known for its very frequent outages and user frustration, may be his biggest user. Leave it to Twitter to solve the world’s problems regarding determining if a site is truly up or not! The one thing we can now say is that at least one employee at Twitter will become successful as a result of Twitter’s outages. Thanks to Techmeme and the New York Times for making my day on this one!

UPDATE: it looks like the New York Times article has updated to state that Payne works for Twitter. It was much more funny when that wasn’t made known 🙂

Identi.ca Provides Users An "Open" Alternative to Twitter

Posted on July 2, 2008 by jessestay

Today I was introduced to a new service called identi.ca, which claims to provide Twitter-like functionality, in a nice, Open Source interface. The service implements the OpenMicroBlogging protocol which, from their FAQs, states, “you can have friends on other microblogging services
that can receive your notices.” This means complete transparency and no reliance on any one service to trust your data with. I am unable to find any other services that have utilized this protocol, however.

The service seems to maintain an open atmosphere across the board. They publish all the details of the code identi.ca is based on, stating they run on the Open Source microblogging platform, Laconica. They state that “soon” they plan to implement SMS updates and notifications, a Twitter-compatible API, Maps, Cross-posting to Twitter, Pownce, Jaiku, etc., Facebook integration, Hashtags, Image, video, audio notices, and even a multilingual interface. Relying on the open source community, on an open standards-based platform may just put them in direct competition with Twitter very soon.

All of your updates posted to the service are under the Creative Commons Attribution 3.0 license and you have to agree to this when you sign up. They seem to remain open across the board – and this will make them successful. I have talked previously about how the mistake Twitter is making is that they are not open enough – they are not basing their protocols on open standards and open techniques of web development. It is showing now, as they are stuck fixing their own problems as the world watches. With a service like this, were it to go down, ideally other services would also sync data and you would not be without service when one service goes down. This is powerful!

The founder of identi.ca is ironically named Evan – they seem to be going head-to-head with Twitter in an Open platform. Based on my experience with open standards in the past, I can already tell which one has the strongest potential. They state to have 1,000 users already and are growing very fast (in Evan’s words). I look forward to seeing them grow, and hopefully contributing as I can – will you join me? You can find me at http://identi.ca/jessestay.

FriendFeed: A Guide for Twitter Users

Posted on July 1, 2008 by jessestay

With all the frustration lately about Twitter going down, disabling features, and developers leaving the service, people still keep coming back for some reason. Frankly, there just isn’t anything that can fully replace Twitter. I think people have simply gotten so used to Twitter and have figured out their own ways to use the service, that moving to a new service and spending time adopting new ways of organizing communication is just too much for most people. Bring in FriendFeed – now, I know I have said previously that FriendFeed is not a competitor to Twitter, but they are getting closer and closer to being a reasonable alternative every day. At the same time, FriendFeed is just more stable and encourages conversation in ways that Twitter just can’t (especially when @replies are down!). I’d like to share with you a few ways that you can use FriendFeed to kick that Twitter habit, and utilize the full power of FriendFeed at the same time.

Not on FriendFeed yet? Sign up and see what you’re missing!

Joining is the first step. Be sure you have given it all of your favorite Social Networks, and especially your Twitter credentials. Don’t be overwhelmed though – the tips I’m about to give you will help ease some of that frustration, and most importantly, try it out for a little, give it a chance like you did Twitter, and you’ll begin to see why it’s so powerful. Remember that when you joined Twitter it didn’t make much sense at first either. It took getting in and using it for awhile before you were able to realize how powerful it actually was.

Find all your Twitter friends that are on FriendFeed and add them

One of my biggest worries of moving to another service from Twitter is abandoning the near 900 people following me. For some of you this number is much smaller, and therefore should be a little easier to migrate. There is a nice little program by Eric at InternetDuctTape (click on the link to get it yourself!) that searches through all your Twitter contacts, and then using the Google Social Graph API, identifies which of those are on FriendFeed. Run this now (sorry, Windows only – I ran mine on Parallels), and it will automatically send friend requests to all of your Twitter friends that are currently on FriendFeed.

This is only the first step to migrating your Twitter network over to FriendFeed and using the service on its own. Only those Twitter friends that are already on FriendFeed will be able to see your updates (you can actually post updates via the “share” button in FriendFeed), but now you can tell those other Twitter friends to come follow you on FriendFeed if they want to continue receiving your updates and join the conversation. The advantage FriendFeed gives you is that for every update and/or link posted to the service, users can actually have a discussion underneath that link as a community instead of guessing what it is they are talking about.

I fully expect someone to write a script (maybe socialtoo.com?) that will automatically post your “shares” on FriendFeed out to your Twitter account, with a link back to FriendFeed to discuss the shared post eventually. Look to see that soon, and all your posts can now be on FriendFeed with no worries of abandoning your Twitter network.

Get an imaginary friend (or two or three)

FriendFeed supports the concept of “Imaginary Friends” for all of those you follow on Twitter and other services that aren’t on FriendFeed. Simply click on the “friend settings” tab in the upper-right of FriendFeed, then click “imaginary” in the navigation. Click on “Create an imaginary friend”, and follow the instructions to create a name for that friend and what network they belong to. Now, those friends’ updates will appear in your list of other friends’ updates on FriendFeed, and you won’t miss a thing!

Reply to your friends’ Twitter statuses via FriendFeed

Now that you have all your Twitter friends in FriendFeed, on any post they make, you can reply, directly from FriendFeed! On any Twitter post, click on “Comment”, then comment and check “Also send this comment as an @reply twitter from (your username)”. Now, when you post your comment, not only will it appear under that user’s Twitter post in FriendFeed for other FriendFeed members to discuss, but it will also send an @reply to Twitter itself so the conversation continues on Twitter as well! I only suggest using this for those Twitter friends that are not on FriendFeed, because, hey – you’re trying to give up Twitter, aren’t you?

Get very familiar with FriendFeed mobile

Just today FriendFeed announced a new iPhone version of its service. The new design is very intuitive and easy to navigate, and I can only imagine will get better over time! The coolest feature is a link to their built-in ability to send photos to FriendFeed that you take on your cell phone. If you send any photo to yourusername+your_api_key@mail2ff.com it will automatically post it to FriendFeed for others to discuss and talk about. The iPhone version gives you the e-mail address you need to send to, but you can also get your api key via https://friendfeed.com/account/api if you don’t have an iPhone.

The other service to check out if you don’t have an iPhone is fftogo.com. FFtoGo.com gives a nice, mobile-formatted version of FriendFeed to your cell phone. Up until today I was using this, and it works very well at viewing what your friends are posting and discussing, what you’re posting and discussing, and who is discussing on the things you post.

Install the FriendFeed Comments Plugin for your blog

Okay, there’s really nothing in Twitter that compares with this or can compare with this, but it does demonstrate the power of FriendFeed. The FriendFeed comments plugin enables you as a blogger to allow your readers to comment to the blog post right on FriendFeed, and read what is being said on FriendFeed, right on your blog! It also shows who has liked it, and lets your users like it right from your blog. Ideally, you could really remove the current comments on your blog and completely replace it with this. You can see this in action right below this blog post above the Disqus comments by clicking the “show” link next to “Join the Discussion on FriendFeed”. Comment there and then go to FriendFeed and check it out!

RSS, RSS, RSS! — Learn to organize your FriendFeed data

Almost every page on FriendFeed has an associated RSS feed with it. Someone asked me today why Summize doesn’t support FriendFeed – that’s because FriendFeed has Summize functionality built into it! Open any page in FriendFeed, then scroll all the way down to the bottom, and click on one of the links next to “other ways to read this feed”. You can have new items on that page sent to your RSS Reader, Facebook, Google Reader or iGoogle, or even e-mail!

This has power. One way I use Twitter is I follow all those that follow me (using socialtoo.com), but I send all those I really need to pay attention to, and that are most interesting to my cell phone via SMS. FriendFeed doesn’t support SMS, but it does have another way to send you new updates of a particular user. Simply click on any username in FriendFeed (or just go to http://friendfeed.com/username or http://friendfeed.com/username/discussion if you want all of their likes and comments as well), and now all of their posts will be delivered to you via RSS! Add to this the power of Google Reader on your Cell phone and you have a superb way of staying up to date on the discussion of the most interesting people you follow.

One other way to utilize this is through the search box on the right of FriendFeed. Type in any text in the search box that you want to “track” (note that track is currently broken on Twitter), add the resulting page to your RSS Reader, and now all found discussions with that term contained (for instance, your brand, or your competitor’s brand) will be delivered automatically to your RSS Reader. This is powerful!

Use Twhirl for all the rest!

Now that you’re paying attention to all of the most interesting people you are following, you’ve brought over all those you can from Twitter, you’re tracking the terms you want, and you’ve integrated FriendFeed commenting onto your blog, you may want to skim over all the rest.

While the FriendFeed UI should be sufficient, Twhirl is an unbelievable tool for general FriendFeed use. From Twhirl you can skim over all of your friends’ posts and comment and discuss on the interesting posts, or just watch all of the posts you have sent to FriendFeed along with anything you have liked or commented on. If you click on the “Me” tab and “like” the interesting posts of your friends, you can then track the conversations that go on within each of those posts that you “like”.

USE the service!

The most important advice I can give to any Twitter user looking to move over to FriendFeed is to use the service! More people will talk about your posts, more people will “like” your posts, and your experience and conversation will get much better the more you use the service. If you just use it as an aggregator and don’t “like” or comment it will still be an interesting tool, but it just can’t replace Twitter until you start using it.

In the meantime, come follow me on FriendFeed at http://friendfeed.com/jessestay. Join the discussion below! I think you’ll start seeing me much more over there, and much less on Twitter as we all begin to utilize the full functionality of FriendFeed. Let’s just face it – we’re all getting tired of this Twitter downtime!

UPDATE: Sasha Kovaliov made the point (on FriendFeed) that I had the fftogo.com link wrong (I had it as ff2go.com). Thanks for the correction, and I’ve corrected it now.

Twitter Continues to Fail Developers, Why They Will Still Succeed

Posted on June 27, 2008 by jessestay

I’m going to dub this Part 2 of my Twitter Love/Hate fest – this should be my last installment for awhile on this topic, I hope. In reality, I really love Twitter. I have a good network on Twitter and frankly, I wouldn’t have met many of you if it weren’t for Twitter. Twitter, in many ways, has changed my career. For that reason I really don’t want to see it fail. It is perhaps this reason that I am so critical of it at times – it’s my hope that someone at Twitter can read these and at least see what the world is really thinking, hoping, and wishing at a given point in time about how their service is performing and being perceived.

Twitter is still continuing to fail developers!

It’s examples like the one I learned about recently where the service, Gridjit, was put offline entirely because of a rash decision on Twitter’s part to remove a feature from Twitter’s API with little to no notice for the developers to respond. In the time Gridjit was down, they have since added FriendFeed support, and I’m willing to bet they have other strategies that don’t include Twitter. Now that Twitter has re-enabled that feature, they are now back up and running, but Gridjit is just another example of the frustration that is occurring amongst developers in the Twitter development community.

Just today, for example, I noticed Twhirl was no longer working with @replies. I remember seeing posts on the Twitter blog recently stating that the @replies tab would be removed, but I remember no notice to developers stating that the features that enable this on clients like Twhirl would be disabled in the API (they did let us know the API was down today though – still no notice it would be down when they took down the replies tab, and nothing to the developer mailing list that I’m aware of).

Twitter tries, but not quite enough

I mentioned last week that Twitter was hiring on their site, but it just wasn’t enough because I think the problems they have exist at the management level. True, they even hired 3 new individuals recently, but they are developers used to being managed, not managing large groups of other developers. Twitter really needs one or two individuals at the top that have true Enterprise-level experience managing these types of IT issues, and very large groups of developers. Remember, Twitter isn’t just the developers that work for Twitter, but the vast group of developers that are also writing applications for their API. The individual in charge of development and IT efforts at Twitter has to have strong experience in managing very large development teams, and working with a very large user-base, in which any change to any part of the system could effect. Twitter needs a staging environment in place, and a system of testing every single change that goes into place before it actually goes out live into the production environment.

They are showing some promise though!

Just this week Twitter announced the inclusion of 2 new investment partners in their list of investors. One of those, Jeff Bezos, does have experience managing the types of issues and large development audiences that Twitter lacks. This is a huge move for Twitter, and long overdue! Jeff will bring Amazon’s firm experience in scalable web environments, and I hope, enable Twitter to enter the cloud more than they currently are, and reduce the tough scaling issues they are experiencing right now.

You can bet you’ll see Twitter begin adopting Amazon’s AWS Cloud services here soon now that Bezos is on board. Amazon has the capability to scale almost instantly as traffic spikes hit, and they seem to be doing it better than any other right now. Twitter really needs this service!

Why I think they’ll still survive, no matter how many developers leave

Twitter is a Marketer’s Paradise. Twitter is full of content about the every-day life of millions of individuals and their friends, who they connect and communicate with, and what their frustrations and interests are. Businesses are beginning to embrace this and use services such as Summize to track information about their Brand, their image, and even their competitors that they could never track before. Businesses can finally track real people instead of just “visitors”.

This is powerful and valuable information to many businesses out there. Because of this it doesn’t matter how many times Twitter goes down or how many developers stay or go from Twitter. So long as users still have networks on Twitter and the Twitter user-base continues to rise as it appears to still be doing, businesses like H&R Block and Comcast and even NASA will still flock to Twitter as a valuable tool in gathering data about their customers and fans. These businesses have it in their best interest to see Twitter succeed, and you better bet they’ll do their best to help out in that effort. Twitter isn’t going anywhere my friends, and I still haven’t retracted from that statement.

Developers Bailing on Twitter

Posted on June 19, 2008 by jessestay

I’ve been following various development mailing lists lately, and I’m seeing a trend of developers starting to bail on Twitter. This is a scary thought, because when the developers bail, so will the users. It all started with a conversation on the Twitter Developers’ mailing list with the subject, “Shame” by a developer named, “nath“, in which he said,

“Well, twitters always down or unusable due to the speed; the api’s
keep breaking and are down just as often; the groups now packed full
of spam which is littering my inbox.

“It’s a real shame to see such a great app crumble and die like this :(“

Alex Payne, a developer for Twitter, responded by saying,

We own Twitter’s speed a stability; my our metrics, it’s been pretty
solid over the last few days.

We do not, however, own spam prevention for this group. That’s up to
Google, and if it’s a hard problem for them, I’d imagine it’d be a
hard problem for anyone.

I go through and clear out spammy posts, but time they reach my inbox,
they’ve reached everyone else’s as well. There’s just not much I can
do about it. Please make use of Google’s “report as spam” features.

After which another developer that goes by “rlansky” responded:

Sorry, but I have to agree with the original author, it is a shame
that the service and the API are so unreliable. The potential for the
services that could be built on an API like the one offered by twitter
are endless. They really are.

Statements like this:

> my our metrics, it’s been pretty solid over the last few days.

don’t do much to boost my confidence. When you make an API available,
you are essentially saying to the world, “here’s our service, come and
build something great on top of it.” You can’t build anything of any
real value or widespread use on something that “has been *pretty
solid* over the last couple days (emphasis mine) .” You just can’t.
You need something that is rock solid all the time.

I’m not trying to start a flame war or bash twitter at all. Like I
said, I think it is a shame because the potential is so great. The
idea is great, the acceptance is great, the use is great, the
possibilities are awesome. But they just can’t be fulfilled given the
reliability of the service as it is today; try to build something on
top of the API that will see wide-spread use and you’ll find that when
you push the gas, the wheels fall off the car… at least that’s been
my experience. It’s been *extremely* frustrating and disappointing.

Peace.

After following a few threads on the Perl development library for Twitter, Net::Twitter, I recently found out that Net::Twitter’s original maintainer too has jumped ship. He has handed it over to a new maintainer, but developments like this are not a good sign for Twitter! It is very clear that frustration amongst Twitter developers has hit a maximum level and I fully expect to see this only increase in the short term.

At the same time, developers like Kee Hinckley are giving advice to Twitter, and they are graciously accepting it seems. Some great tips are being given on ways to enhance the API, and I even suggested they do a public bug tracker which they seemed to like. Twitter clearly doesn’t seem to have enough expertise in-house, although they do keep saying they are hiring. Their jobs page doesn’t seem to have any upper-management positions though which I think is really what they need right now.

I’m very worried for Twitter. As more developers jump ship and work on other platforms such as Plurk and FriendFeed (which really isn’t a direct competitor to Twitter), this great tool is going to be left in the dust with no new development and large networks of people moving elsewhere. Twitter’s largest traffic comes from the API itself, and as that traffic dies down, so will Twitter. Imagine, for instance, if Seesmic were to stop development on Twhirl due to the costs associated with keeping up with API flaws? That would be quite a chunk of Twitter’s users being forced over to the other Twhirl clients, FriendFeed and Seesmic itself – it’s such an easy transition were Twitter support to be dropped! What happens when Twhirl begins supporting Plurk?

Twitter needs to do something, and they need to do it fast. I agree they need to get their infrastructure in place, but before even doing that they really need to put every hack possible in place to keep the API up, keep it working, and work with the developers to ensure they are staying happy. A large revolution is about to take place, and I’m afraid it won’t be pretty.

UPDATE: See the little FriendFeed box below? Click “show” and join the discussion on FriendFeed about this right on my blog! Subscribe to my updates here.

Please Come Join me on FriendFeed

Posted on June 3, 2008 by jessestay

How did I get to spend a day with Robert Scoble? How did I get to participate in the interview with Twitter founders, Evan Williams and Biz Stone, that ended up on the front page of TechCrunch? I joined the discussion on FriendFeed.

I think some would probably consider me a Twitter power user. I think Twitter is great for posting updates, getting conversations going, and seeing what your friends and followers are up to. However, FriendFeed is where the true conversation is at. With threaded conversations, the ability to “like” and share items, it provides a much stronger catalyst for conversation that Twitter could never provide.

How do I use it? Well, I actually thought it was too cluttered at first. I am finding as I use it more I am coming up with my own ways to better organize my conversations and keep track of what is going on. First of all, I use the “Me” tab religiously. I often also click the “see both” link (just add “/discussion” after your username when on the “Me” tab) on the right sidebar to see not only the things I have posted and the discussions within, but also the things I have “liked”, and commented on. This allows me to keep track of the existing conversations I have entered.

Then, I skim the “friends” tab to see the interesting things others are posting (If you have over 100 friends, there’s no way you’ll be able to read it all like you do in Google Reader or some do on Twitter). I find as I join other conversations and like and comment on others’ posted items it shows them I have an interest in the things they too are interested in, and true friendships get nurtured from these conversations. Then, if you want a mobile solution, I use http://fftogo.com to read FriendFeed on my mobile phone (a internet plan for your phone is required, but if you haven’t signed up for one of those yet you’re still in 2007! 😉 ). It formats FriendFeed in a nice, easy-to-read browser format so you can track things in the same way you do on your computer. You can send photos to yourusername-yourapikey@friendfeed.com from your cell phone.

FriendFeed is not Twitter. Twitter is hard to replace in what it gives me. I will still use Twitter to post status and other items to get the discussion going, but I will now begin using FriendFeed to continue that discussion. Will you join me on FriendFeed? Subscribe to my updates at http://friendfeed.com/jessestay. You can see what I’m discussing at http://friendfeed.com/jessestay/discussion.

Twitter Kills Important Features on the API With Just a Few Hours Notice

Posted on May 31, 2008 by jessestay

I saw some very concerning issues on the Twitter development list today, and my frustration has only been increased after reading some of the claims of Blaine Cooke today on TechCrunch. Yesterday, the one thing that seemed evident, and perhaps I’m wrong on this, but Ev Williams and Biz Stone do not seem to have much of a technical background. They made this clear in the interview, and there’s nothing wrong with this, assuming they have the technical staff to handle it.

Today on the Twitter development mailing list something was made apparent – experienced developers and businesses on the Twitter development mailing list cannot trust the architecture of the API that runs on Twitter. Just yesterday, a crucial feature of the API which allowed the retrieval of an individual’s friends and all of those friends’ timelines was removed from the Twitter API.

About 1 week ago, Alex Payne, the developer Biz and Ev kept referring to in the interview yesterday as having a lead role in the development, announced on the developer mailing list that this feature was going to be removed and asked if anyone was using it. With only about 5% of the applications saying they needed it, Twitter removed the method Thursday with just a notification on the developer mailing list and about 8 hours notice, no other notification elsewhere or warning that it was happening at that point.

All of the sudden, application developers everywhere were saying they couldn’t run their applications because of this change. These were applications such as Hahlo, Twitterati, Twibble, and Gridjit. What’s the issue here?

The issue is Twitter isn’t communicating effectively. We addressed this yesterday – I think they realize it, but I want to reiterate it. I can’t help but wonder if the experience is even there to be able to communicate effectively. I’ve worked as a developer in several publicly traded companies, one of them a Fortune 40, and some of the decisions the Twitter development staff have made would have gotten me fired at previous employers I have worked for. Where is the experience, and how can I, as a business and developer using Twitter trust them to build something on top of? I want to see where the experience is before I build any more on top of the Twitter API – does the Twitter staff have LinkedIn profiles?

Now, I’m not trying to criticize any individual at Twitter – I want to think they have the experience necessary to handle this, but I’d prefer they not pull the wool over our eyes if there is not enough experience at Twitter to handle the API I am trying to build a business off of. I know for a fact there are many smarter people using the API that could help analyze the experience if they need that help, but we need Twitter to communicate with us and let us help them out. Because businesses are being built on the API we want to see them succeed (I’m writing this as I wear my “Wearing my Twitter Shirt” I got from them yesterday). I think, as they said in the interview yesterday, while it could take months to get things in place, we, as businesses and developers could help them out if they just let us and communicate properly with us.

The questions I asked yesterday were centered around the developer and how we could help them. They told us to communicate with them. I really don’t know how we can communicate effectively with Twitter if they can’t be open to us back. I even posted this on the mailing list this morning, and received absolutely no response. As a Twitter API developer and business owner, I don’t know how much longer I can keep my Apps on Twitter. I know many others share the same frustration, and once the Apps begin leaving, so will the users.

I think, and hope, based on the interview yesterday, that Twitter understands this. I’m optimistic they do. However, we need an open communication channel, consolidated, and the experience to know how to manage that channel effectively with the API, or new opportunities are going to arise very quickly wich developers will leave to.

UPDATE: It appears that Twitter has a pretty experienced crew, per their recent blog post. Again, you still have to keep in mind that it may take time to fix the problems that are already there – is it worth the wait?