Play it now.

Alternatively, visit the repo.

password has been updated to v1.1:

• the game now starts after you press [Space]
• you gain points for victories (score is not saved between reloads)
• UI is a little nicer

v1.2 planned features:

• adjustable difficulty, via either or both of password length and time per round
• zen mode: longer rounds, no score tracking, calmer UI
• persistent personal high score you can compete against

I almost feel like this is not worth an update, but people have been curious and supportive of the game.

You can see all planned features in the issues section. Suggestions on gameplay and visuals are welcome.

EDIT: updated hosted version to not reset score on loss (only resets when you start over).

I’m going to be making an fully libre, tactical, co-op, WW2 FPS in the ioquake3 engine. I need an idea for a name. Anyone have ideas?

It's going to be kind of like Day of Infamy, if you've ever played it. You're going to be working through the enemy's base (Axis or Allies, depending on which side you choose) with your friends, trying to complete an objective. You can either be stealthy, go guns blazing, or anywhere in between. There's also going to be TDM, where you either attack or defend against another team of players. I'm hoping to increase longevity by making it completely open source.

A simple web game I made to combat depression.

To play, go here. Warning: the game starts as soon as you enter the page.

To view source, visit the GitHub repo.

How to play:

• Press the keys you see before yourself. The key turns green if it's been "solved".

• Once all keys are "solved", you start a new round automatically.

• If the timer runs out before all keys are "solved", the game is over. Press [Space] to start over.

• There's no score. Play whenever and for as long as you like. Quit whenever you've had enough.

Hi all,

I'm looking for some advice regarding how to set up a basic CI regression / testing suite. This isn't my full time job, but a side project my group at work wants to spin up to... shall we say, give us a more real time monitoring of functionality and performance regressions coming out of the underlying software stack development (long story).

As none of us are particularly automation experts, I was looking for some advice from my fellow Tilderinos. Please forgive me if any of the below is obvious and/or silly.

A few basic requirements I had in mind:

1. Can handle different execution environments: essentially different versions of the software stack, both in docker form and (eventually) via lmod or some other module file approach (e.g., TCL), and sensible handling of a node list.

2. Related to one, supports using the products of builds as execution environments. Ideally we'd like to have a build step compile the stack and install it to a NFS from which we can load it as a module.

3. Simple to add tests. Again, this isn't our full time job -- we mostly want to add a quick bash script / makefile / source code or the like to the tests when we run into an issue and forgot about it.

4. Related. We should be able to store the entire thing as a git repo. I have seen this to some extent with Travis, but my experience with Jenkins was... sub-par (is there a history? Changelog? Any way at all of backing up the test config?).

5. Some sort of post-processing capabilities. At a glance we need to be able to see the top line performance numbers for 20-30 apps over the different build environment. Bonus points if there's a graph showing performance vs build version or the like, but honestly a CSV log file is good enough.

6. Whatever CI software we get has to be able to run this locally. Lots of these are internal only numbers / codes. FOSS prefered.

7. A webui for scheduling runs / visualizing results would be nice, but again this could be a bash script and none of us would bat an eye.

Any thoughts would be greatly appreciated. Thanks!