WAN Show Bingo

[OS_Tycoon]

First time poster, but long time watcher of LTT. I was watching the Wan show a couple weeks ago (Before Christmas actually) and had a funny thought before it started. Wan Show BIngo! There's enough quirky stuff to go around on this show to fill a bingo sheet.

 

http://wanshowbingo.com

 

There's not much meat on it's bones. Other than some basic web socket stuff behind the scenes, you can see everything that is happening up front. I'll gladdly take any suggestions.

 

Short term todo list:

 

Winner Announcement / Detection - If the majority of players with a square have it checked, then it's a good square.

Twitch Bot to announce winners.

Twitch Integration - Login to track stats.

 

GitHub Repo Here:

https://github.com/OSTycoon/WanShowBingo

 

Right now I'm only opening up the client and will only accept pull requests to add squares (the list is in script.js). Once I have some configuration stuff obfuscated in the backend, I'll open up the server.

 

It's late, and I wasn't expecting the shout out. Github link later this week.

 

 

 

<3

 

 

Edited January 29, 2018 by OS_Tycoon
Added the GitHub Link

[mikat]

I sure am waiting for the github link

[OS_Tycoon]

5 hours ago, mikat said:

I sure am waiting for the github link

Link posted! (Not my proudest work as I originally made it during the show before Christmas in like 45 minutes)

[Mendelity]

maybe try contacting the LTT-staff/Linus to ask what bot you should code for... Or create your own bot with all the features from the current chat bot so you can offer it for them to use...

[vorticalbox]

On 27/01/2018 at 2:41 AM, OS_Tycoon said:

Once I have some configuration stuff obfuscated in the backend, I'll open up the server.

 

You sould have all sensitive information in a different file that isn't pushed.

 

For example if you're using node you store passwords to databases in an environment variable.

 

There is no reason to obscure any server-side code .

[OS_Tycoon]

2 hours ago, vorticalbox said:

You sould have all sensitive information in a different file that isn't pushed.

 

For example if you're using node you store passwords to databases in an environment variable.

 

There is no reason to obscure any server-side code .

I agree with you 100%, and configuration stuff should be in a separate file. I should have it ready to go by the middle of the week. Just had alot of stuff going on this weekend.

[vorticalbox]

7 hours ago, OS_Tycoon said:

I agree with you 100%, and configuration stuff should be in a separate file. I should have it ready to go by the middle of the week. Just had alot of stuff going on this weekend.

Out of Interest what are you using for the back end? 

[OS_Tycoon]

On 2/12/2018 at 1:07 PM, vorticalbox said:

Out of Interest what are you using for the back end? 

Its a really basic Node / Socket.io server on EC2. The static files are hosted on S3 and pushed out with Cloudfront. I haven't fleshed out the back end to the point that I want it yet. I was experimenting with some twitchbot stuff that I want to strip out before I upload it because I'm not happy with it yet.

[jincio]

One suggestion, for what the WebApp needs to do you really don't need socket.io, you could do the same things with the native Websocket object. At the same time, importing socket.io isn't very impactful, so it's fine either way.