mythmon / crimsontwins Goto Github PK

Some sites use 301 temporary redirects to do random things. These redirects should not be followed during initialization, so that the resets show random content when desired. This might mean that we need to just ditch the idea of doing this processing and verification upfront.

• https://github.com/mozilla/zamboni/graphs/code-frequency -- Never loads, "Problem with HEAD request".
• Scrumbugs -- graphs don't load.

It looks like the server is not actually starting for Node 0.8. When I remove web.start() we see the same failure pattern across all versions. When I explicitly add an additional web.start() to the first test or move it from the before() func into the first test the tests pass.

Implement an HTTP API that has equivalent functionality to the bot.

look into setting up a FFOS app for webdev's CT install

If we deployed this on a server, people could run their own screen if they so desire.

At the moment, this will just add additional screens to the pool, which is not what we want.

Either we remove the pool and every client is just a copy of the main screen or we come up with a way to distinguish (login?).. hmmm.

There should be a list of URLs that are shown when nothing else is going on, and after a few minutes of showing whatever silly gif someone posted, it should return to a default url.

There should be an optional param to modify the content of the black bar. In it's absence the bar will display the URL, as it currently does.

This would allow us to add comic alt text to the bars, or include data from the IRC bot about what the dashbot query params were that lead to the image.

Actually, doesn't have to be nunjucks, but at any rate, currently the application code and templates are intermingled and they shouldn't be.

We might have to precompile the templates at start time, but this is node, we can do that!

/cc @jlongster and @tofumatt so they can tell me this is a horrible idea ;)

There should be a way to modify the resetUrls from the web interface, and be able to save these back to the config file, all of this without resetting the bot.

Make the bot independent of Crimsontwins. Leave the bot as a reference implementation or consider rewriting it as a Hubot plugin. May be blocked on issue #21

Consider adding the ability to stretch a single virtual screen across multiple physical screens. Will require CrimsonTwins has some knowledge of how its screens are laid out.

The two side-by-side iframes in the Hydra view should be zoomed out a bit as to show enough content.

*insert intelligent idea for a heuristic here"

When you restart the server, the clients get kind of confused, this could be a lot more robust.

make sure config is read only until auth'd

auth could be github, or persona, matched against a whitelist of names.

I think it is regenerating the entire preview page, which duplicates things.

Since this is a problem I propose that we could cut this problem in half by moving a tv to my wall.

we need the means to set a per request timing.

we also need to be able to specify indefinite as a time, both in config and per request.

When the server is temporarily down the client happily displays what it last loaded, but requires a refresh to reconnect. The client should be able to reconnect on its own and display some UI warning that it's disconnected or that it's screen does not exist.

flip black bars on and off via config

Pressing back works. Pressing forward or navigating to a page with a hash tag doesn't.

I'mma have to summon @potch to explain how we should best do this :) Somethingsomething context menu item.

crimsontwins: ?+oma?+ http://gifsongifsongifs.biz/gifcity.gif

I discovered CT through DevOps weekly and it's a perfect solution to my multiple screen problems - better than the hacky PHP page I put together. But I can't get the IRC part to do anything - I can add screens through the admin interface and the bot joins our IRC server but it doesn't respond to anything :-(

I've tried mentioning it and messaging it with URLs and they scroll past in stdout but they don't get added to the displays.

My very limited NodeJS experience means I can just about work out what the app is doing but I can't figure out what I'm missing.

Any suggestions?

The github status page formats timestamps incorrectly: "16:9" instead of "16:09".

Right now we are using LESS. Lets jump on the bandwagon and use Stylus.

Right now LESS is being compiled on the client side, every time. Lets stop that, and compile the CSS on the server.

clients should reconnect gracefully when the server goes down

Currently, the screens show only the first-ever URLs they were pointing to. Instead, the metadata should change whenever the content URL changes.

Video Lego Blocks RFC is a first stab at a fuzzy notion of auto-registering air mozilla components. It's a little long, so I've boiled it down into something more concrete --

Consider a live air mozilla setup -- mozcamp, mozfest, perhaps summit. Cameras turning on and off as different talks, keynotes, and social events start and stop. We have camera blocks that can 'check in' with a predefined url and then start streaming. With the proposed API these camera blocks could register a new CT screen at start up and stream to it, then deregister it when it disconnects. This may require a thin shim, but I think the idea is sound and this would be a necessary first step.