I see that you can post to Hive and have it go elsewhere...but what about posting to Twitter and having it post to Hive?
That would bring content here, and content brings users
You are viewing a single comment's thread from:
I see that you can post to Hive and have it go elsewhere...but what about posting to Twitter and having it post to Hive?
That would bring content here, and content brings users
Yes, it can work both ways. Once Hive have set up a service on IFTT then automatic sharing can be set up with any other service on iFtT in either direction.
We launched using the idea that @kodaxx commented above but our users were downvoted to oblivian by #BernieSanders.
Had some development delays and are now geared for DBuzz-to-Twitter instead of the other way around since we didn't get enough support for Twitter-to-Hive.
I guess what you are doing is a share to Twitter link on d.buzz, but with IFTTT set up, a user could choose to share all buzzes to Twitter (after a one time setup) without needing to click a share to Twitter link each time. This word be my definite choice.If a user did not want to share every buzz, then the one time setup could include an IF #tw (or other #code) is in the buzz, only then would it be shared. Still easier and faster than clicking the link, therefore more buzzes to Twitter.
No, we actually had the 2nd one plan, just ran into delays with making it happen.
Would you have to input your posting keys to IFTTT? Hope woke would it have permission I guess
How else* damn autocorrect lol
Hmm. Not sure. Not the keys I don't expect. Perhaps with Hivesigner or Peak connect
That is what we originally did but we were downvoted by #BernieSanders to oblivion.
It set us back a few months 😔