jjj / publishiza Goto Github PK

Hey 👋

It seems the publishiza.com URL is no longer under your control. You may want to remove references to it in the repo.

Neat idea but the UX could be better. If needs to be much faster to create. WP posting is too slow for a "storm". If I built this I'd use CMB repeatable field. Create the whole thing and then publish. Send each field as a tweet then compile the all the fields into a nice post.

Note: I have not actually tried the plugin yet, I have just read @JJJ's tweetstorm. :)

IMO, each tweet in a tweetstorm is a reply to the last tweet in the chain. This way, when you open one tweet, you see all of the tweets above or below it.

It seems like the current output uses the initial tweet for all replies.

pretty much what it says on the box.

One of my biggest complaints about tweetstorms that people should write a blog post, if they used this tool and I wanted to read it all in one place, that link would solve that. See also the IndieWeb principle POSSE

Kudos for moving the needle on the topic and putting a tool out there.

Hi,

Are you really sure about that ? I've used this API quite often and [at that time] this seemed to be bad practice to use private keys in code. These keys are probably your keys, so it can be stolen to run spam campaigns not to mention illegal things.

[I said "at that time" but I don't see why this would have changed].

I've done this wrapper and it's workin fine without any private keys in code https://github.com/tweetpressfr/tokentome, there are probably a lot of libraries but this one is done the WP way. At least it tries to be wp-friendly :)

Please consider this. Your application (created with dev.twitter.com) could be blacklisted.
Regards.

I think I like the raining cloud better.

And the poo will probably need to go eventually, but I'm quite fond of the lil guy.

Scheduled storms don't cause any tweets.

I haven't tested, but I believe this is due to the nonce verification in publishiza_publish_post. Since