Tag Archives: twitter

Medium may not last

On Monday, I launched my Kickstarter project about independent microblogging, with a focus on owning your own content and making blogging easier. On Tuesday, Lindy West left Twitter in a post about Twitter’s inability to deal with harassment. On Wednesday, Ev Williams announced that Medium would lay off 50 employees.

The message is clear. The only web site that you can trust to last and have your interests at heart is the web site with your name on it.

That’s the main goal with Micro.blog. Build a service and write a book that makes independent blogging more approachable. No one knows exactly what the web will look like in 10 years, but we can take the first step to get there. If you’ve been frustrated by the ad-based silos and waiting for a reason to post to your own site again, I’d love your support.

Microblog auto-link differences

One reason I like microblogging on my own web site is that I can control the links and simple formatting. I’ve noticed lately that Twitter can’t consistently auto-link even certain domain names, for example.

This difference is illustrated well in a post I made this morning, which included timetable.fm and micro.blog. Twitter auto-linked the .blog but not the .fm. The cross-post to App.net auto-linked the .fm but not the .blog.

Here are the 3 versions:

Link differences screenshot

In the final screenshot — the original from my own site, from which the others were pushed out automatically — you can see how I’ve specifically linked the domain and phrases I wanted to. It’s a minor thing, but it just looks better when the author has a little control over the formatting. (And while I don’t use it here, my own short posts can contain text in bold or italics via Markdown, too.)

Why I posted to Twitter again

Following up on my post about Twitter at 10 years, I decided to mark the actual 10-year anniversary of my first tweet by posting from my @manton account, which I haven’t touched in over 4 years. After so much time, you can be sure the tweet was going to be exactly 140 characters:

Hi! 10 years since my first tweet. 4 years since my last. You can follow the blog cross-posts via @manton2. This message will self-destruct.

Why post again? I’ve had some fun experimenting with cross-posting to @manton2. As I wrote when I first started this:

And yet, many people get their news from Twitter. Since I started microblogging on my own site, I’ve had time to reflect on the role of indie microblogging and cross-posting. I think the IndieWebCamp has it right: publish on your own site, syndicate elsewhere.

Overall I think it has been a success. I use my upcoming platform Micro.blog for the cross-posting, so using Twitter has helped me improve Micro.blog too. And I get more people who don’t actively follow RSS feeds to read my blog posts again.

As promised, I’ve already deleted that last tweet at @manton. I’m also not replying to mentions over there, although I try to reply or favorite tweets I see from @manton2. I know this Twitter strategy might seem like a strange compromise, but I think it’s working because it puts a focus on my independent blog instead of on Twitter.

Fake news as propaganda

In yesterday’s essay about Twitter, I also linked to my post on Instagram’s lack of native reposts. Jason Brennan has written a follow-up about fake news and propaganda, exploring what we can learn and apply to microblogging:

Aside from the normal reasons propaganda exists, it exists on social networks like Facebook and Twitter because it can exist on those networks. It’s profitable and useful for the parties manufacturing and disseminating it. To Facebook and Twitter, upon whose networks it propagates, it doesn’t really matter what the information is so long as it engages users. Facebook’s apathy to propaganda is regularly exploited.

Hillary Clinton also connected fake news and propaganda in a speech this week:

Let me just mention briefly one threat in particular that should concern all Americans, Democrats, Republicans and independents alike, especially those who serve in our Congress: the epidemic of malicious fake news and false propaganda that flooded social media over the past year. It’s now clear that so-called fake news can have real-world consequences.

The internet is at a crossroads. Entrepreneurs love free speech, scale, and money, but those don’t always align in a good way. As much talk as there is of making an impact, very few leaders in Silicon Valley seem to think deeply about consequences.

Twitter at 10 years

It was 2008 in Chicago, the C4 conference was wrapping up and I shared a cab to the airport with Alex Payne, who built the first Twitter API. I was so excited about the potential for the platform that I probably had a dozen ideas for Twitter apps. Alex and I sat at a cafe at the airport, waiting for our respective flights, and talked about the future.

Years passed. I did build and ship a few Twitter apps, including the popular Tweet Marker sync API. But I also grew disillusioned. I took a break from using Twitter.

Alex had left the company and Twitter was much different from a business and leadership perspective by the time the rest of the world started paying attention. Thousands of employees worked at Twitter. How many of them had experienced the early days of following friends’ tweets via SMS, when the service seemed genuinely new and important? The future had arrived but it was full of hashtags.

This year — with rumors of Twitter being acquired, with fake news and the election, with online harassment — many people have written about the future of Twitter. I’ve been paying attention again, experimenting with cross-posting. I missed the 10th anniversary of when I joined Twitter in July 2006, but not the date of my first tweet a few months later.

10 years is a good milestone to reflect on. I want to highlight a few posts I’ve read recently, and then wrap things up at the end.

What I like about this article by Faruk Ateş is that he gives a sense of the major changes Twitter has gone through, most of which were difficult to fully understand at the time. On the change with @-replies:

The second thing is that when they started hiding @-replies to people you don’t follow, they stripped the user experience of a vital ingredient for civility: peer transparency. The tone of discourse changed much for the worse over time, following that new behavior of the timeline. Before the rollout, all your friends would see if you behaved like a jerk to someone; after the rollout that was no longer the case. It removed the natural consequences of bad behavior, thereby encouraging people to reap the benefits of such bad behavior much more frequently.

This is a theme across many posts, that we didn’t realize what all these changes were adding up to. I have some related thoughts about Instagram and another post on why today’s social networks are broken.

Next, Sarah Frier writes for Bloomberg about how Twitter leadership is losing faith in Jack Dorsey. That despite new features such as live video, Twitter failed to ship other development efforts and fell behind competitors:

Advertisers see potential in the company’s live video strategy, but they’re also being wooed by photo- and video-sharing app Snapchat, and Facebook’s Instagram, which has recently become more advertiser-friendly. At the time of Twitter’s 2013 initial public offering, those services weren’t close competitors. Now they both have larger daily audiences than Twitter.

As long as Jack Dorsey has 2 jobs, it will be easy to blame him for being unfocused. I don’t know if that’s fair. But when streaming live football gets so much attention, there do appear to be competing visions at Twitter.

Twitter is too expensive to acquire. It’s also too flawed for a company like Disney to take a risk on. So instead there was another round of layoffs. From Kurt Wagner at Recode:

Last year, Twitter also cut 300 jobs shortly after Jack Dorsey took on the CEO role full-time. (Or part-time, given that he’s also running Square.) The current feeling among those close to the company is that Twitter is simply too bloated, and pays too much in stock-based compensation for a company that’s still not profitable.

There are no guarantees for an unprofitable company. The only certain thing is that something will change.

Back to Alex Payne. He wrote a post 6 years ago about his time at Twitter, and his unsuccessful attempt to convince coworkers to decentralize Twitter. It holds up very well:

Decentralization isn’t just a better architecture, it’s an architecture that resists censorship and the corrupting influences of capital and marketing. At the very least, decentralization would make tweeting as fundamental and irrevocable a part of the Internet as email.

It used to be impossible to imagine that Twitter could fail. And today, it’s still unlikely to vanish or even change much overnight. But the web will be better if we assume that Twitter is a lost cause. From the 10-year view, it’s clear that Twitter has already changed.

Acquisition rumors come and go, although they seem more real this time, and we’re reminded that few web sites last forever. It’s time to prepare for a web without Twitter.

Fake news and Instagram

Twitter has retweets. Facebook has sharing. But Instagram has no built-in reposting. On Instagram, there’s no instantaneous way to share someone else’s post to all of your followers.

The first version of Instagram was built by a very small team. They’ve always grown slowly and expanded the UI thoughtfully. I think the lack of a repost feature was deliberate.

When you have to put a little work into posting, you take it more seriously. I wonder if fake news would have spread so quickly on Facebook if it was a little more difficult to share an article before you’ve read more than the headline.

It’s not easy to build software that encourages good behavior. When I look at my Instagram timeline I see beautiful photos, hand-drawn art, and snapshots of everyday life. I see the very best of the world. It’s not the full truth, but it’s all true.

Instagram was no accident. The only question: was it unique to photos, or can the same quality be applied to microblogging?

Indie publishing is about control

Andy Baio redesigned his blog recently and argued that blogs still matter because of ownership and control. Of course, I agree. And though it may seem far off, there’s no guarantee that Twitter will outlast our own blogs. Andy writes:

Twitter, itself, may be acquired and changed in some terrible way. It’s not hard to imagine a post-Verizon Yahoo selling off Tumblr. Medium keeps pivoting, trying to find a successful revenue model. There’s no guarantee any of these platforms will be around in their current state in a year, let alone ten years from now.

Ben Brooks followed up:

Having my own site gives me complete control to do whatever I want, whenever I want, however I want. I don’t understand why people ever want it any other way.

Words are powerful. Especially right now, why let anyone else have control over the format of our words and how they spread? Having a blog is a statement: our writing exists apart from the whim of an algorithmic news feed.

Today’s social networks are broken

Brent Simmons has left Twitter, frustrated with the diminishing value of the service, Twitter’s inability to deal with harassment, and more:

And then it was part of the system that helped elect a fascist President. This tipped it over for me: it’s no longer worth my participation. The shitheads can have it.

Facebook has also been in the news for its role in letting fake news spread. Ben Thompson has a long essay this week on it:

I get why top-down solutions are tempting: fake news and filter bubbles are in front of our face, and wouldn’t it be better if Facebook fixed them? The problem is the assumption that whoever wields that top-down power will just so happen to have the same views I do. What, though, if they don’t?

Maybe. Though while we should debate how to balance Facebook’s enormous power, there should be a parallel effort to move away from the centralized publishing model that gave Facebook that power.

Facebook has confused itself into thinking it is the whole internet, and so the principles of a free press that apply to the open web, also must apply to Facebook. No. While Facebook has a great responsibility to do the right thing, because they are so big, Facebook is just a web site.

I want Facebook to improve. I want Twitter to improve. But I can do very little to effect change at those companies, and some problems are so fundamental as to be essentially unfixable. The web wasn’t supposed to be like this, with all the power and all the writing concentrated into so few sites.

It’s time for a new social network that brings discoverability and community without the baggage of an ad-driven network that must grow to a billion users. A social network that embraces the open web, and freedom of expression, while preserving a clean timeline that can’t be interrupted by harassment.

Not just one new social network. I hope that many developers will work on products that encourage independent publishing again.

It’s going to take time to build. That’s why I started working on Micro.blog 2 years ago. I’ve made great progress, but I’ve also drifted, unfocused, uncommitted to finishing it, as if I knew something was missing.

Something was missing. The election results have made that clear. I was thinking big, but not big enough. The way forward must include both a decentralized publishing platform and the tools to encourage a safe community.

If you’d like to know when the beta is finally ready, please subscribe to the announce list. Thank you. Update: Edited to reflect the new name for Micro.blog.

An open Twitter starts with the web

Dave Winer wants an open alternative to Twitter:

I want it to be friendly to Twitter, because as a user and a shareholder, and a developer who uses their platform, I want to see it thrive. But I also strongly believe we need the open system, the Central Park to Twitter’s condo buildings on Fifth Ave and Central Park West.

John Biesnecker, reading Dave’s post, suggested XMPP because it’s an open standard and federated. But as great as XMPP is for messaging, it seems too different from the web; it would be like starting over. The nice thing about building on independent microblogs is that we can leverage the existing open web infrastructure: all the WordPress installs, RSS feeds, and new work from the IndieWebCamp.

That’s what I’ve tried to do for Snippets.today. Learn from the UI innovations of Twitter — the fast timeline experience, the effortless posting — but without skipping the important first step of independent web publishing.

Core Int 242, Swift, and verified Twitter

From the show notes for today’s episode:

Manton reacts to negatively to the Swift 3 decision to disallows subclassing by default, while Daniel tries to see the bright side. The two discuss Twitter’s new invitation to apply for @verified status, and Daniel’s attempt to do so. And they quickly touch base on the upcoming Apple-sponsored reality show, “Planet of the Apps.”

Believe it or not, I was kind of holding back a little in my Swift ranting. But it was the most critical I’ve been on the show. And it’s totally okay for you to disagree! Maybe even good for the platform if you do.

Twitter and .blog

Dave Winer has a good comment for anyone questioning the web:

So when they tell you they know for sure that the web is dead, or that everyone wants to host their blogs in locked-up silos, or that you can’t build a great open social net on RSS, you might want to lower your glasses down your nose and look out over the top and ask Reallly? Are you sure?? ;-)

Nothing is certain in business. For every success, there are many “sure thing” failures.

I posed a question on this week’s Core Intuition as we were talking about Automattic’s upcoming .blog domain name registration. The gist of it was: what is more likely to survive for the next 50 years, Twitter or .blog? Twitter is huge, dominating the news and seemingly unstoppable, but social networks don’t have a great track record. I’d put my money on a new top-level domain, both because of the vision of empowering users to control their own content and also because domains were designed to last.

Companies aren’t exactly designed to fail. But that is their default outcome.

Core Intuition 236 and app subscriptions

We published Core Intuition episode 236 today, discussing the recent App Store announcements and a listener question about offices. We wrap up with plans for WWDC.

There has been a lot of great blog posts and podcast episodes already on the App Store subscription change. I listened to Under the Radar 31 and the Release Notes special edition today and recommend both. The most confusion seems to be around what kind of apps are appropriate for subscriptions, where by “appropriate” I mean “what Apple will approve”.

John Gruber also follows up at Daring Fireball on this question:

Professional apps that require “a lot of maintenance of new features and versions” don’t fit either of those categories. Would Twitter clients like Tweetbot and Twitterrific qualify for subscription pricing? After talking to Schiller yesterday, I thought so. Now, I don’t know.

As I mention on Core Intuition, apps that have a backend service with obvious hosting and maintenance costs — a music streaming service, an invoicing web app, or a blogging platform, for example — are easier for users to understand as needing to be subscriptions. Twitter apps are an interesting example because some are pure clients to Twitter’s backend, but many increasingly have their own app-specific services like timeline syncing or push notifications.

For years Apple has allowed apps to use auto-renewing subscriptions. I had an iPhone app and companion web service that was approved by Apple for auto-renewing subscriptions, after I made the case for the service as a “cloud” archive. From section 11.15 of the App Store review guidelines:

Apps may only use auto-renewing subscriptions for periodicals (newspapers, magazines), business Apps (enterprise, productivity, professional creative, cloud storage), and media Apps (video, audio, voice), or the App will be rejected

From my experience and listening to other developers, I’ve had the impression for a while that Apple would essentially reject most auto-renewing app submissions by default. While we still don’t know what “all categories” means in the new announcement, I expect it means that there will no longer be a kind of blanket rejection. Apple will still reject many apps as poorly suited for subscriptions, though, and maybe that’s okay for now.

(I’m conflicted on this point. John Gruber’s suggestion to approve everything and let the market decide is compelling and fits better with my instinct that the control should be in developers’ hands.)

“Subscription fatigue” is a real thing that I’ll occasionally hear from customers about. No one wants to pay $1/month to 40 different apps and services; it feels like a burden in a way that paying the same total price to just two apps at $20/month does not. Nevertheless, subscriptions are very powerful. Everything I’ve done over the last few years is to position myself to eventually have a recurring-revenue success.

Time to rethink blog comments

Twitter has lost some of what made it special for communities 5 years ago. I’ve noticed a few trends:

  • Twitter’s 140-character limit and easy retweeting encourage and amplify negative tweets. Sincerity is less common. Everything is an opportunity for a joke.
  • Widely followed, long-time Twitter users don’t find the joy they used to when interacting with followers. Some have retreated to private Slack channels, at the cost of public discussion and approachability.
  • Developers have never completely forgiven Twitter for crippling the API. This doesn’t directly impact most users anymore, but it’s a backdrop that gives every new Twitter feature a tone of distrust. Progress is slow.

Meanwhile, blog comments have slowly been killed off over that same period. The rise of social networks, combined with the technical problems of fighting blog comment spam, pushed most bloggers to prefer answering questions on Twitter.

Becky Hansmeyer writes about the intersection of these problems — that some Twitter users avoid public discussion, but most blogs no longer have comments to fall back on — by pointing to a post from Belle Beth Cooper:

“Belle’s post really resonated with me because it reminded me of something I think about a lot: when an ever-increasing number of blogs and media outlets are disabling comment sections, where do decent, thoughtful people bring their discussions? I only offer readers one way to contact me on this site, and it’s via Twitter. But what if, like Belle, you no longer use Twitter (or never did in the first place)?”

We didn’t realized how much we lost when we turned our backs on blog comments years ago. Just look at one of Daniel Jalkut’s blog posts from 10 years ago, which he and I discuss on an upcoming episode of Core Intuition. 53 comments! And they’re all preserved along with the original content. That’s difficult to do when comments are spread across Twitter and easily lost.

It’s time to take what we’ve since learned from social networks and apply it the openness of cross-site replies. That’s why I want to support Webmention. As Becky mentions, Civil Comments look great too. I think we can encourage both in parallel: distributed comments like Webmention for sites that can support it and better centralized comments like Civil.

Blog when you disagree

The echo chamber. We only follow people who we already agree with. We only jump on the bandwagon of snark and ridicule when it’s already the accepted narrative, and thus safe to be part of the mob.

But sometimes you’ll find an area where you aren’t completely in line with the crowd’s opinion. There’s a topic that keeps coming up for which you have something to add. The default story is missing an important angle.

When you disagree, that’s what you should write about, and you should post it to your blog. 140 characters thrown against wave after wave of mainstream opinion tweets will be drowned out. A blog post isn’t a cheap opinion; it’s a statement that what you think matters.

The evolution of linkblogging

In my posts about defining what makes a microblog post and guidelines for RSS, I talked a little about links but didn’t explore linkblogging. While many blog authors post primarily long essays, shorter link blogs are a common approach for bloggers who want to post new content several times a day.

Essentially two types of link blogs have evolved since the early days of blogging. The most traditional link blog can be seen in Dave Winer’s posts (click on the Links tab). These are links with a very short commentary. Many tweets are like this. In a way, this format is the purest form of microblogging.

The second type of link blog starts to fall outside the limits of microblogging. Instead of just including a URL, authors use a quote from the linked material as the foundation for the post. The majority of Daring Fireball posts adopt this format. While John Gruber is known for his full essays, those longer posts are infrequent today. He keeps his site active by linking to other interesting essays and tacking on his own brief opinion.

Daring Fireball has become so successful that Gruber’s approach to linkblogging has been copied by many other sites. MacStories, Six Colors, One Foot Tsunami, John Moltz’s Very Nice Web Site, and Marco Arment’s blog are just a handful that follow this pattern. All of these sites post the occasional essay, but most blog posts link away to an external site in the RSS item, not back to their own site.

At a technical level, this difference can best be seen in the RSS feed’s <link> and <guid> elements. These elements will contain URLs that either link back to the main site, or link away to an external site.

Here is where this evolving approach to link blogs starts to break down. Let’s take an example from Six Colors, one of my favorite sites. (I recommend subscribing. The members-only secret podcast with Jason and Dan Moren is really fun, and the email magazine is great too.)

In a link post about Hulu’s pricing, Jason Snell actually writes 4 paragraphs of commentary (plus a footnote). This is more like an essay than a short link post that points to the external site.

Another example is when MacStories linked to Twitter’s launch of Moments. A few paragraphs of quoted text, 5 paragraphs of MacStories commentary. The commentary is as important or even more important to read than whatever Federico is linking to.

Sometimes we read sites like MacStories, Six Colors, or Daring Fireball more for the commentary than for what is being linked to. But when using an RSS reader, there is too much confusion about where an item’s link goes when clicked if the site’s feed isn’t consistent about linking everything back to its own site.

And in fact Jason Snell acknowledges this problem by offering two separate RSS feeds: the default one, with a mix of links back to Six Colors for essays and pointed elsewhere for link posts; and another feed with everything linking back to Six Colors, where the commentary lives. He also attempts to minimize confusion on his own site by giving each type of post its own icon in the site design.

The less clear-cut the distinction between essays and link posts, the more confusion we introduce to readers. In some ways, this mixed approach really only works for Daring Fireball, because his feature essays are so long, and so obviously different in format to the rest of the link posts.

Good conventions for blogging have been at a standstill for years. While part of the appeal of indie blogging is there’s no one “right” way to do it, and authors can have a strong voice and design that isn’t controlled by a platform vendor, we must accept that Twitter has taken off because it has a great user experience compared to blogs. It’s effortless to tweet and the timeline is consistent. For blogging to improve and thrive, it should have just as straightforward a user experience as social networks wherever possible.

Luckily, RSS already has everything we need for clients to visually distinguish between link posts and regular ones. If the <link> element points to a domain other than the one for the site, it’s probably a link post. If the <link> and site domain match, it’s a full post.

I’ve adopted this in my new microblogging platform by exposing the domain in the UI itself, at the end of the title or microblog post whenever it’s a link post. If it’s a full post, the link isn’t added. And for either type of post, the timestamp links back to whatever was in the <link>.

Here’s a screenshot from one of Dave’s posts. Note that the link was not in the RSS text. It was added by my app automatically:

linkblog example

This has been a long post, but it boils down to two simple recommendations:

  • If you’re a blog author and you’re adding any significant commentary, the RSS feed should point back to your site.
  • If you’re an RSS client developer, the difference between link posts and full posts should be exposed in the UI.

I believe that adopting these will bring more consistency to blogging. Users won’t need to hover over links, or guess what will happen on a click or tap. It’s a small change that will make reading blogs a little better.

Concerned about user-generated content

On the latest Under the Radar podcast, Marco Arment and David Smith talk about ways to make your app more robust. That includes tips for scaling your app with a lot of data, and also dealing with potentially hostile user data. It’s that last point that I’ve been thinking the most about lately.

With the experience of building Tumblr and Instapaper, Marco is clearly now hesitant to ship app features that accept arbitrary user-generated content, because a small indie company just doesn’t have the resources to deal with spam and abuse. Instead, he suggests outsourcing whenever possible. For example, letting Apple accept and reject podcasts, and basing the Overcast podcast directory search on that already-vetted list.

Let’s say you’re building a Twitter-like service. As we all know, hate is widespread on Twitter. At times, it seems impossible to even have a G-rated Twitter experience. But the problem is less that users can publish terrible tweets, and more that it is so easy to be exposed to those tweets with search, trending topics, retweets, and replies.

As I work on my microblogging project, I’m trying to be aware of these points in the platform where bad content can leak out. So I don’t have global search or trending topics. I also don’t make it easy to stumble upon random users. But I do have replies, which by default will currently go out as push notifications if you have the iPhone app installed. It’s that area that I should focus my attention.

Two options that come to mind for minimizing abuse in replies:

  • Don’t allow replies from people you aren’t following. This solves the problem, but it comes at the expense of discussion. It removes the accessibility that many people love about Twitter’s asynchronous following model.
  • Quarantine or attempt to classify replies so they don’t bubble up in your timeline or as notifications by default. This would be like an over-aggressive email spam filter. Difficult to get right and possibly routed around by clever microbloggers.

After listening to Marco and David, and reviewing the full scope of what I’ve been trying to build, I’m pretty concerned about this. I’m looking at Akismet, and other metrics internal to my app for judging content and suspicious user accounts, but I may be a little in over my head on this issue.

River5 and twtxt

Two new microblog-related services have launched. This week, Dave Winer announced River5:

“So I decided it was time to do a restart of my JavaScript RSS aggregator, and it’s now ready for Node users — it’s called River5. […] This is a foundation for developers to build on, but it’s also possible for an adventurous user to set up their own rivers.”

River5 is built on a few XML and JSON formats, including River.js. I’m pretty interested in River.js as a format for aggregating multiple feeds together, so I’ve supported it in my new microblog platform. As a next-generation RSS, though, I prefer the proposal I wrote about in a post called RSS for microblogs.

Next up is twtxt, which attempts to recreate Twitter as a distributed, command-line based system with self-hosted text files:

“Instead of signing up at a closed and/or regulated microblogging platform, getting your status updates out with twtxt is as easy as putting them in a publicly accessible text file. The URL pointing to this file is your identity, your account. twtxt then tracks these text files, like a feedreader, and builds your unique timeline out of them, depending on which files you track.”

I’m less sure what to think of twtxt. The simple plaintext format is nice, but we already have a good infrastructure for this with RSS. And as I’ve noted before, having HTML in RSS with inline styles and links is nice for microblogs, and it’s not clear to me whether that would fit well with twtxt.

If you want to start an indie microblog, my suggestion remains to use existing blog software that can generate simple RSS feeds. Short posts, no titles. This is a widely-deployed format that we can continue to work with for years to come.

Algorithmic timeline now rolling out

Dan Moren reports that Twitter is rolling out their algorithmic timeline, where tweets aren’t strictly reverse-chronological. It is opt-in for now, and likely won’t apply to third-party clients:

“I’d also guess that third-party clients won’t be able to implement this for a while, if ever. So users of Tweetbot, Twitterrific, and others won’t really have a substantively different experience.”

I don’t see the setting in my Twitter account yet. As a user, I hardly care, because I don’t read the Twitter timeline directly anyway. But I’ll be watching how people react to this and how it might affect my own microblogging plans.

Matt Gemmell on Twitter ads

Matt Gemmell has started including shorter posts on his blog. Today he writes about Twitter’s decision to not show ads to some popular users:

“There are problems with that approach, the main one being the tacit admission that their ads are detrimental. If you’re rewarding people by reducing the hostility of their experience, maybe just fix the experience for everyone, and find something positive to charge for instead.”

Ads are the worst. I don’t know if it’s possible to build a large-scale social network like Twitter or Facebook without being mostly ad-supported, but I’d like to believe it is. WordPress.com — which has elements of a social network, even though we don’t consider it one — might be the closest successful attempt.

Long-form writing as a filter

Soroush Khanlou, looking for more new blogs to read, makes a great point that the process of blogging leads to better writing:

“Opening my RSS reading and finding 30 unread items makes me happy. Opening Twitter and seeing 150 new tweets feels like work. I’m not sure why that is. I think Twitter has become more negative, and the ease of posting quick bursts makes posting negative stuff easy. With blogging, writing something long requires time, words, and an argument. Even the passing thought of ‘should I post this’ creates a filter that lets only better stuff through.”

I think there’s something to that. It’s often only after writing our thoughts down that we fully understand how we feel about a topic.

And here’s where I bring this back to microblogging. Because when starting a post, we don’t always know whether it will be long or short. How often have you seen a series of tweets that in hindsight even the author would agree should have been a blog post?

This is less of a problem if instead of tweeting you start out with the intention of posting to your own site. Short post can stay short, and posts requiring more words can naturally expand to a full essay.

I don’t think that our short-form, seemingly unimportant writing should exclusively be on centralized networks. If it’s worth the time to write something — whether a thoughtful essay or a fleeting one-off microblog post — then it’s worth owning and publishing at your own domain name.