https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

OMG, They Killed Twitter! (Not)

Huge foofoorah (for those who have any interested) over in the Twitterverse about an option that was taken off by Twitter. And I yawn and say ho-hum.

Okay, Twitter 101: You sign up. You find (through various means, more below) various people who are Twittering. You “follow” them, so that their Tweets show up in your message stream (what Twitter somewhat confusingly calls your “timeline”).

If someone says something you feel warrants a reply, you can reply to them. The reply looks like, “@doycet LOL, you are eating a sammitch on the sofa? ROTFL” (Note: not real reply.)

Previously, if you were following me, you could see me make that comment to @doycet (that’s Doyce’s Twitter user name) in your message stream. If you were not following Doyce, you wouldn’t have seen the original message that had me rolling in the aisle, but you would have seen my reply …

… if … and this is the big if … you’d turned on the option (off by default) to do so. Otherwise, you’d have never seen my orphaned reply, either.

Twitter has now taken away that option, feeling it was conflusing. Apparently, only 2% of Twitter users actually had it turned on, but they are a vocal 2%, decrying the death of Twitter and noting that these sort of one-sided replies from people they follow were a great way to find additional people to follow.

Um …

Okay, maybe I’m insensitive because I’m part of the 98% that had it turned off. Honestly, I didn’t want to read the umpteen zillion replies that Neil Gaiman makes to people on a daily basis. Well, I might, but I wouldn’t be able to see anything else. On the other hand, Neil (and others) do a great job both retweeting items of interest from others (basically forwarding a Tweet message to their own stream, which shows who originally wrote it), and in mentioning people in their Tweets (sometimes even as a specific recommendation).

Result? I get plenty of suggestions of new people to follow from the people I follow, even if I’m not privy to their individual replies to those folks.

I’ll take it a step further — I like not having my replies to others show up in my followers’ streams. Not only does it reduce their exposure to spam / false followers, but I tend to see those replies as IMs — I know they are (were) theoretically public, but they still felt private.

I will admit that, given a choice, I’d have left the option available to those 2% — I don’t specifically see the harm in it. But I also don’t think Twitter has committed some grievous wrong in doing this, and there is a virtue in simplicity and consistency.


 

I’ve been meaning to talk about my own use of Twitter of late, and this is as good a chance as any.

I’ve found it to be a nice way to make one-off observations, on the fly, that wouldn’t have warranted a full blog post previously (some would have ended up in one, others would not). 

The 140 character limit is irksome, but hardly impossible to overcome. Probably good for me. And fun to read — like an ever-changing book of koans, with links.

I very much like that these observations get wrapped up at the end of the day in my blog anyway. It makes it all the more “journally.”

I enjoy reading the bits that come through on my Twitter feed (following 41 people, though only a dozen or so of those Tweet with any consistency). They are an adjunct to other sources of info, and have a light air to them that is quite pleasant. 

I like.

73 view(s)  

4 thoughts on “OMG, They Killed Twitter! (Not)”

  1. Speaking as one of the 2%, here are my four (five?) points:
    1) I think a good 3/4ths of my finding people to follow have been through responses others have made. It reminds me of people I should be looking for, and more importantly, of people who are active and tweeting.
    2) I hate anything that reduces functionality. “Taking Away Features” is one of the things that tweaks me.
    2b) It’s not “the death of Twitter” and there’s certainly no question that I’ll still be using it (albeit just as quietly as I do now) without the function.
    3) I don’t believe anything posted on the web or e-mail is truly private, so I tend to keep that in mind when I write.
    4) I don’t “retweet.” I barely use hash tags. The latter I think is something I’ll probably repair as time goes on and my quantity of posting increases, but I don’t see the former happening. (For one thing, if I feel strongly enough about something, I’d much rather write a post on it than repeat someone else’s point.) I also don’t do a lot of linking, BUT…

    …and this it the big “but,” my Twitter usage is not oriented towards promotion or a lot of the other reasons people use Twitter.

  2. Twitter has backed away (a bit?) from this change ( https://hill-kleerup.org/blog/heroes/2009/05/testing-for-prizes.html ):

    This morning we received lots of great info about the replies setting we changed yesterday. Folks loved this feature because it allowed them to discover new people and participate serendipitously in various conversations. The problem with the setting was that it didn’t scale and even if we rebuilt it, the feature was blunt. It was confusing and caused a sense of inconsistency. We felt we could do much better.

    So here’s what we’re planning to do. First, we’re making a change such that any updates beginning with @username (that are not explicitly created by clicking on the reply icon) will be seen by everyone following that account. This will bring back some serendipity and discovery and we can do this very soon.

    Second, we’ve started designing a new feature which will give folks far more control over what they see from the accounts they follow. This will be a per-user setting and it will take a bit longer to put together but not too long and we’re already working on it. Thanks for all the great feedback and thanks for helping us discover what’s important!

    So you’ll see tweets sent to others you don’t follow — but only if they are manually typed in rather than from hitting Reply. I can’t imagine that’s a huge percentage of them.

    Second, it sounds like they’re looking to bring back in the feature they turned off, but a bit more slickly (though hopefully with care not to complicate the simple Twitter interface).

    More importantly, it sounds like the real reason the original feature was turned off was due to performance vs. some sort of philosophical vision. That’s fine, and actually a good thing — but I wish they’d been up front about it.

  3. And an even longer note on the subject: http://blog.twitter.com/2009/05/replies-kerfuffle.html

    Twitter evolves and thrives on how folks use it. Some of our best features are invented by users, so listening is extremely valuable. Replies and conversations are awesome and we fully intend to support and encourage their growth. We removed a setting that 3% of all accounts had ever touched but for those folks it was beloved. The use cases that folks loved about this setting will return in a new and improved form.

    We screwed up from a communications perspective this week. When I heard that this change was going out, I rushed to write a blog post. This setting had both product design flaws as well as technical flaws and I did not do my homework. My post came from a product design perspective but the technical perspective was the reason it went away so quickly. Normally, I spend more time understanding the issue before explaining it on this blog but in my haste I made a mistake.

    There are some good lessons learned here for anyone in development.

    Subsequently, there is now a lot of confusion about what this change actually was. 97% of all accounts were not affected at all by this change—the default setting is that you only see replies by people you follow to people you follow. For the 3% who wanted to see replies to people they don’t follow, we cannot turn this setting back on in its original form for technical reasons and we won’t rebuild it exactly the same for product design reasons. I’ve taken some time to break down both the product design and technical problems this feature had.

    Which is what needed to be done up front. But it’s good that they’re doing it now.

    Product Design Flaws

    Since last year we’ve been hearing from users and having discussions about removing this setting—feedback indicated that it was useful but also created confusion. People would change the setting and then not understand why their timeline had fragments of conversations. From the tweet author perspective, there was an unclear expectation as to who would actually see messages which often lead to trepidation when it came to using replies. Finally, even folks who understood the setting would complain that they couldn’t follow accounts with a high volume of replies because the replies overwhelmed their timeline. It was becoming apparent that we had an opportunity for improvement.

    If nothing else, a note of “Hey, if you turn this on you might not be able to see the forest for the trees” next to the option would be handy.

    Technical Problems

    Even though only 3% of all Twitter accounts ever changed this setting away from the default, it was causing a strain and impacting other parts of the system. Every time someone wrote a reply Twitter had to check and see what each of their followers’ reply setting was and then manifest that tweet accordingly in their timeline—this was the most expensive work the database was doing and it was causing other features to degrade which lead to SMS delays, inconsistencies in following, fluctuations in direct message counts, and more. Ideally, we would redesign and rebuild this feature but there was no time, hence the sudden deploy.

    I still suspect that the technical problems were more of a driver for this than the design problems. Regardless, based on the technical issues described (and the user-base impact), this change was pretty much a no-brainer … if communicated properly.

    (Concluding text skipped.)

Leave a Reply

Your email address will not be published. Required fields are marked *