Skip to content
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

Automation Idea #11

Open
DeicideHD opened this issue Mar 9, 2016 · 4 comments
Open

Automation Idea #11

DeicideHD opened this issue Mar 9, 2016 · 4 comments

Comments

@DeicideHD
Copy link

Suggestions

Automatically pull tweets and broadcast them

Spam Filters

Simple 10 second cooldown

10 second preview before it posts(So no obscene images make it through)

Image option On and Off obviously

and finally the most complex yet probably the best way to really implement the idea.

Use the twitch, twitter, youtube, and or other api to pull followers, subscribers, contributors etc really this gives the freedom to have the audience that is following and contributing to your cast to be seen and promoted. It also opens up things like new subscription perks that benefit the community and broadcaster. Your subs now get to be interactive, their Im live! tweets get seen and the entire community grows.

@techguydave
Copy link
Member

This is definitely a great idea!

Right now my use case doesn't need it and it'll probably take quite a bit of planning and actual writing, but I would love to implement it at some point in time.

Side note, would a queue also work in junction with this? Maybe have stuff automatically added to a queue, but then display a panel where you can approve/disapprove individual tweets. While not completely automated, it's a lot easier than finding tweets and copying the links. Plus, you probably never want stuff from the masses thrown on-screen unfiltered anyway. Good way to get yourself in trouble! The queue could also be useful in manual mode, too.

@DeicideHD
Copy link
Author

A queue system might be the best idea, just have it parse the 5-10 most
recent tweets every few minutes, and the take/post options as is w/o having
to get the url yourself. I still think the API for subs/followers etc would
be godly, but thats a big chunk of work regardless. Now the queue idea is
great and I think there is probably an easy solution tbh.

On Thu, Mar 10, 2016 at 7:39 PM, David Thomas [email protected]
wrote:

This is definitely a great idea!

Right now my use case doesn't need it and it'll probably take quite a bit
of planning and actual writing, but I would love to implement it at some
point in time.

Side note, would a queue also work in junction with this? Maybe have stuff
automatically added to a queue, but then display a panel where you can
approve/disapprove individual tweets. While not completely automated, it's
a lot easier than finding tweets and copying the links. Plus, you probably
never want stuff from the masses thrown on-screen unfiltered anyway. Good
way to get yourself in trouble!


Reply to this email directly or view it on GitHub
#11 (comment)
.

@techguydave
Copy link
Member

Yeah, the thing about subs/followers is that you'd have to have some way to match the viewer to their Twitter account in order to verify that they're the same person. For instance, I may be "synth3tk" on Twitch but "JohnJacob" on Twitter. How to link those two is not trivial.

@DeicideHD
Copy link
Author

simple login page requiring both, not clean but very effective

On Fri, Mar 11, 2016 at 8:33 AM, David Thomas [email protected]
wrote:

Yeah, the thing about subs/followers is that you'd have to have some way
to match the viewer to their Twitter account in order to verify that
they're the same person. For instance, I may be "synth3tk" on Twitch but
"JohnJacob" on Twitter. How to link those two is not trivial.


Reply to this email directly or view it on GitHub
#11 (comment)
.

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

No branches or pull requests

2 participants