New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "tweetstorm" UI for chaining status updates with chained POSSE tweets #1907

Open
tantek opened this Issue Sep 21, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@tantek
Contributor

tantek commented Sep 21, 2017

While trying to do this:

Post a series of status updates on a single topic as a thread.

I encountered this error:

No easy way to do this, have to cut and paste URLs, doesn't chain POSSE copies etc.

Some other notes:

Context: @benwerd posted this tweetstorm which is very much about the need for more independence from power structures https://twitter.com/benwerd/status/910654790572449792

Known needs a tweetstorm UI that is as simple and easy as whatever Ben is using to tweetstorm to reduce the friction of using his own site to tweetstorm notes (with copies automatically POSSEd to Twitter and threaded to look like a tweetstorm there).

Related: http://tantek.com/2017/263/t2/imagine-posted-first-tweetstorm-second

@danito

This comment has been minimized.

Show comment
Hide comment
@danito

danito Sep 21, 2017

Contributor

👍 But do you really need a "tweetstorm" or would chunk a long text into bites which are possed to twitter with the in-reply-to set to the previous one good enough? Later would be much easier to add as Known plugin.

Contributor

danito commented Sep 21, 2017

👍 But do you really need a "tweetstorm" or would chunk a long text into bites which are possed to twitter with the in-reply-to set to the previous one good enough? Later would be much easier to add as Known plugin.

@tantek

This comment has been minimized.

Show comment
Hide comment
@tantek

tantek Sep 21, 2017

Contributor

I think yes (really need a "tweetstorm") and here's the two key reasons why:

  1. Lowest switching cost. Tweetstormers would easily be able to switch to using the Known tweetstorm UI instead of their existing behavior on Twitter. Lowering that friction as much as possible is perhaps key to enabling/encouraging use of Known first instead of Twitter first.
  2. "long text" UI is too distracting. "chunk a long text into bites" sounds feasible, reasonable, and a good idea, HOWEVER, it is vulnerable to the same problems as every other large (unbounded) text field, e.g. writing part of a draft of a blog post, and not actually ever posting.

The very existence of tweetstorms, especially by people who otherwise have blogs, typically even on their own domains, indicates that there is something else going on, and I hypothesize that a big part of that are the immediate constraints of the Twitter UI:

  1. Each point you make must be tweetsized when you write it. Can't edit it after writing the next one etc.
  2. You must make the next immediate logical point next (you can't write the points out of order, futz with re-arranging them, etc.)
    This "forced focus" of the Twitter posting UI is likely what enables tweetstorming, you're less apt to get distracted with tangents, lesser points, latter points, if the only thing you can do is to post the very next tweet-sized point in your series of points.
  3. You're compelled to "finish" quickly. The "real time" nature of Twitter provides a strong incentive to quickly make your points, including your conclusion, before others reply to intermediate tweets etc. perhaps distracting you from the larger point(s) you intend to make.

See also @kevinmarks's Noterlive app/UI for possible inspiration.

Contributor

tantek commented Sep 21, 2017

I think yes (really need a "tweetstorm") and here's the two key reasons why:

  1. Lowest switching cost. Tweetstormers would easily be able to switch to using the Known tweetstorm UI instead of their existing behavior on Twitter. Lowering that friction as much as possible is perhaps key to enabling/encouraging use of Known first instead of Twitter first.
  2. "long text" UI is too distracting. "chunk a long text into bites" sounds feasible, reasonable, and a good idea, HOWEVER, it is vulnerable to the same problems as every other large (unbounded) text field, e.g. writing part of a draft of a blog post, and not actually ever posting.

The very existence of tweetstorms, especially by people who otherwise have blogs, typically even on their own domains, indicates that there is something else going on, and I hypothesize that a big part of that are the immediate constraints of the Twitter UI:

  1. Each point you make must be tweetsized when you write it. Can't edit it after writing the next one etc.
  2. You must make the next immediate logical point next (you can't write the points out of order, futz with re-arranging them, etc.)
    This "forced focus" of the Twitter posting UI is likely what enables tweetstorming, you're less apt to get distracted with tangents, lesser points, latter points, if the only thing you can do is to post the very next tweet-sized point in your series of points.
  3. You're compelled to "finish" quickly. The "real time" nature of Twitter provides a strong incentive to quickly make your points, including your conclusion, before others reply to intermediate tweets etc. perhaps distracting you from the larger point(s) you intend to make.

See also @kevinmarks's Noterlive app/UI for possible inspiration.

@mapkyca

This comment has been minimized.

Show comment
Hide comment
@mapkyca

mapkyca Sep 27, 2017

Collaborator

I really like this...

Would it be as simple as having an inline comment box, which has the in reply to field automatically filled with the posse channel if one already specified?

Collaborator

mapkyca commented Sep 27, 2017

I really like this...

Would it be as simple as having an inline comment box, which has the in reply to field automatically filled with the posse channel if one already specified?

@rikmendes

This comment has been minimized.

Show comment
Hide comment
@rikmendes

rikmendes May 14, 2018

I love this idea...

rikmendes commented May 14, 2018

I love this idea...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment