Making My Proposed ‘Twitter Killer’ Scalable

by Shelt Garner
@sheltgarner

I find myself thinking up a lot of different ways to make my fanciful “Twitter Killer” based on updated Usenet UX design more scalable. One solution I just came up with is using Google Docs-like collaboration when any particular user in-line edits a Post.

But this obviously raises the question of — when does someone get to spawn a new Post within a threaded discussion?

If you don’t allow that to happen, then each Thread would have just one Post that was completely torn apart by various people. Here is my solution — not only would you limit who could contribute to a Group’s Thread, but you also limit who can spawn a new Post within that Thread.

So, you would have a situation where, say, a New York Times reporter writes a 500 word post that is quickly inline edited by a few dozen people, all using different colors so as to not to cause confusion. But some Users would have the ability to spawn a new Post within the Thread or Subthread.

This newly spawned Post might have some conditions, like it can’t just be the old Post, you would have to use subset of the content from the original Post in your new Post in the Thread or Subthread.

Something like that. Something manageable.

And you might get a Notification in your Control Panel when someone you followed either edited a Post or spawned a new Post. Or maybe you could follow individual Threads in a Group to monitor that sort of thing as well. There are a lot of different ways you might go.

Author: Shelton Bumgarner

I am the Editor & Publisher of The Trumplandia Report

Leave a Reply