I like the idea of posting all of the updates to Twitter. Do you have any suggestions for how to handle the case where multiple games are going on at the same time? I feel like if we post absolutely everything to one Twitter account it will get overwhelming. Each AUDL game results in about 700 game updates, so if we have a bunch of those going on along with a bunch of non-AUDL games, it would likely be too noisy to be useful or interesting.

I'll look into how much pagination improves the page loading time and consider making this change too.

Thanks for the suggestions!

mliu wrote on Sun, 22 April 2012 15:32

I like the idea of posting all of the updates to Twitter. Do you have any suggestions for how to handle the case where multiple games are going on at the same time? I feel like if we post absolutely everything to one Twitter account it will get overwhelming. Each AUDL game results in about 700 game updates, so if we have a bunch of those going on along with a bunch of non-AUDL games, it would likely be too noisy to be useful or interesting.

Yah... that would be a pretty noisy feed. Hrmmm... you could have create a few generic game feeds. Something like: @LVgame1, @LVgame2, etc. ?

mliu wrote on Sun, 22 April 2012 15:32

Thanks for the suggestions!

Thank for the great service!

Now... if the AUDL could polish up their online offerings to be as smooth as yours, I'd be truly happy

Hmm, I think having a bunch of generic Twitter handles would end up being pretty confusing and I'm not sure many people would want to follow them.

We do have plans to build more customization for how to receive real-time updates, so I'll keep these ideas in mind as we proceed. One thing a developer in Amsterdam has in the works is a module to send automated text-messages to players that tells them their schedule and what field their next game is on. This is open source so one option is to use or modify that in the future.

A few of the teams do have web developers in their organization and we hope to integrate some of our data into their sites! There are some club teams we'll be doing this with as well this season, and we hope it reduces the burden of all the teams having to write lots of static HTML to put up scores, schedules, and stats.

It might just be for me, but once the scores got into double digits they became too wide for their box and stacked on top of each other (text wrapped?)

It went
9-8

10-8

10-9

10-
10

Anyway that all of the substitutions could be entered at once? Kinda sucks to see 14 spots filled up with substitutions, just list all the names and then have an "out."

Fixed. I just pushed the change a second ago:

I like the idea of posting all of the updates to Twitter. Do you have any suggestions for how to handle the case where multiple games are going on at the same time? I feel like if we post absolutely everything to one Twitter account it will get overwhelming. Each AUDL game results in about 700 game updates, so if we have a bunch of those going on along with a bunch of non-AUDL games, it would likely be too noisy to be useful or interesting.

I'll look into how much pagination improves the page loading time and consider making this change too.

Thanks for the suggestions!

Some ideas that come to mind...
1. Use one twitter account for each league/category of game. For example, an AUDL feed, an open feed, a D1 feed, etc.

2. If necessary, filter the feed for twitter to show the "more important" updates.

3. Make a twitter account for each team and
a. send every update to both feeds for a game (bad if someone follows both teams), or
b. send each update to only one team (e.g. the offensive team) and people need to follow both teams to see the whole game.

4. Don't use these twitter accounts for anything else except for live game updates (this one is important

5. Let people mix and match between 1 and 3 by allowing whoever sets up the game in LV to assign whatever twitter account(s) they want for the live feed (within reason).