http://i.imgur.com/Ed4AV8n.gif

This is partially incorrect. There certainly is a 'dxlevel' flag, however all it really does is enable/disable some features. TF2 on Linux works by a translation layer that translates DirectX calls to OpenGL ones, and a different 'dxlevel' setting would affect which calls are being made, which *might* help with performance, but not necessarily, or not by much.

Not using Ubuntu, but I do get slightly better FPS than on Windows. It's not too noticeable of a difference, though -- maybe 10-20 FPS.

I would suggest trying it out; it's fast, secure and stable. (And if you care about TF2, it seems to run fine on it.)

As far as which distribution to use, I'd probably recommend Fedora or Ubuntu if you want something that "just works".

Just to clarify, the non-CLI alternative to using apt-get directly would not be downloading and installing it manually, it would be using a graphical front-end to apt (such as synaptic). Manually
installing a package is generally a bad idea unless you know what you're doing.

Have you considered implementing a persistent sidebar with health status for all players, similar to what the tournament spectator HUD does? This would avoid the bug where everything is frozen after a pause.

Game 2 here we go... LGRW!

https://i.imgur.com/jcfos5V.gif

The only files you need are those which you modify. If you do not make changes to either of those files, you can leave out the scripts directory entirely.

mpd + ncmpc on computer.
google play music (with subscription) on phone.

Perhaps you should elaborate on "didn't work". People cannot help you when they do not know what your problem is.

I think your best bet here would be to speak with enigma regardless of what you do.

For a mobile application, you probably want a way to query the site using some form of API that returns data in JSON, XML or some other easily parsable format. It will get rather messy if you simply strip out data from the HTML files, especially as any changes could potentially break your application.

Similarly, if you create a mobile site, you probably want it to be part of the main site code, accessible through a subdomain or something of that sort. Otherwise, your site would have to act as a relay, with all data flowing in and out. This would result in additional latency and excess bandwidth use. Of course, you can use client-side JavaScript to reduce this effect, but that sounds messy and will probably not function as expected across the many available mobile browsers.

I don't think a project like this is feasible without adding some needed functionality to TF.tv.

Not necessarily. An operating system is more than just a kernel, so it depends on how much Valve changes (and whether they open source those changes), as well as where you draw the distinction between operating system and user applications.

[edit]

To elaborate some more on what I mean... Do you consider the init system a part of the operating system? Basic tools such as coreutils and the shell? What about the display server?

I would argue that the existence of Steam and other Valve tools are integral in making SteamOS what it is and should therefore be coupled with the notion of 'SteamOS'. So what if some of the foundation applications are open source, they already were, so nothing changed.

Then again, even if you don't agree with my definition that the user interface should be considered a part of 'SteamOS', it still doesn't guarantee that the operating system in its entirety will be open source. It's entirely possible Valve could replace parts of the traditional stack and keep them closed source. For example, they could write their own display server. They could even take existing open-source code and not release their modifications, as not all of the standard Linux libraries and applications are released under the GPL, but under more lenient licences such as BSD or MIT.

Due to licensing, any changes they make to the Linux kernel and many other userland tools and libraries must remain open. This does not mean that Valve will have to release the Steam client and other applications they create under a similar licence.

Nowhere on the announcement page does it say this.

While there's no reason for them to be complaining, it's not as big of an announcement as some people are making it out to be. Despite all the marketing crap on the Steam website, it will most likely be just another ordinary Linux distribution, set apart only by the applications that come pre-installed and its default configuration.

Of course, there will be some good to come out of this. With Valve creating their own Linux distribution, it's inevitable that they will have some of their developers work on optimisations on both the kernel and user-space programs, with many of these changes pushed upstream. (I hope that Valve will be cooperative on this front.)

Perhaps this will also push NVIDIA and AMD (especially AMD) to take their Linux video drivers more seriously.

While Valve will be forced to open-source many of their changes due to licences, I highly doubt they will open-source most of their original work. I wouldn't expect them to change the licence of the Steam client or similar programs, so there's probably not much you will be able to change as far as the user interface is concerned. I only hope that I am wrong.