add "publish on twitter" support.

[tedder]

other changes:

• rename http to twhttp. Conflicts with 'import http.server' deep inside oauth2.
• add config example and docu to README

[timofurrer]

Why don't we allow to have multiple post tweet hooks and outsource the twitter publishing in a hook? There are other platforms like twitter - if we, one day, want to support them too - we'll end up in a mess of service specific code inside twtxt. The hook could be implemented as an external cli tool or as a twtxt extension..

[tedder]

Totally understand that idea. I thought about making the hooks a list. It certainly works well with the indieweb POSE model. On the other hand, dealing more natively with Twitter made sense too. Do you have ideas of how the extension concept could be implemented?

[timofurrer]

If we would implement extensions you'd have the advantages of both. I'd have some ideas. There are many examples around on how to implement extensions/plugins in python.. Do you think there'd be more twitter integration then just republishing?

[tedder]

I don't see there being much more depth to the twitter integration, but others may disagree (perhaps by combining it into the twtxt timeline?).

Want to put out a basic pull request with an initial extension framework? I can then rebuild this on top of it.

[timofurrer]

Let's wait what others thoughts are about this before starting anything stupid :beers:

[kitchen]

+1 on framework idea. I'm also bullish on integrating early, factoring out common things into extractable plugins later. Often you don't know the API you want to expose until you've written a few consumers of it.

I wonder if there are some app.net or identi.ca users who might want to help flesh out the idea some more?

On Feb 7, 2016, at 8:16 PM, Timo Furrer notifications@github.com wrote:

Let's wait what others thoughts are about this before starting anything stupid

— Reply to this email directly or view it on GitHub.

[buckket]

I really don’t like the idea to include Twitter (or any other service) support in twtxt. Keeping the main application clean and simple while solving only one problem is my main focus here.

But I can understand why people might want to use this, so in the long run implementing a plugin interface/system, which allows to add hooks seems the best solution.

[tedder]

@buckket are you thinking about extensions being in their own python module (pip install twtxt-twitter) or as part of this one (import twtxt.extensions.twitter)?

[buckket]

@tedder I’d prefer them being separate modules.

[buckket]

Closing this for now until we have a plugin system set up.