-
The Beat And Zen Of Indie Games
Posted on August 18th, 2008 No commentsA few days ago I stumbled across a great little game from an Indie company on Steam called Audiosurf. The best I can describe Audiosurf is that it combines the action of a Sci-fi racing game with Tetris and Guitar Hero. The $9.99 game requires you to supply the music. You pick the game type, tell it which MP3 to use and it will generate a game track based on the characteristics of that music.
An example of one game type with the game and music sped up a bit can be seen here on Youtube:
I have some European heavy metal that is insanely difficult on the medium and high settings. A great way to kill 20 minutes of time once in a while.
On the other end of the spectrum is a game still under development called “fl0wer”. From some of the people behind the flash game “fl0w” the game fl0wer is more of a meditation tool than what many would recognize as a game.
Here is a great video that shows off the basics:
An HD version of this video and other videos can be found on the GameTrailers website under fl0wer.
In my opinion fl0wer is something that could really only be enjoyable with a HDTV and modern sound system. The fact the game is coming out for the PS3 is not a coincidence.
-
Alarming Report On Office Politics
Posted on August 4th, 2008 No commentsThe most accurate and trustworthy American news agency reports on an alarming trend in office politics:
Study Finds Young People Remain Apathetic About Office Politics -
Comcast’s Possible IPv6 Deployment Plan
Posted on August 4th, 2008 No commentsA follow up to the post named “The Future of IPv4“:
In the Network World article “Comcast pitches IPv6 strategy to standards body” the Cable ISP discusses their current plans on how to migrate their customers to IPv6.
The summary of what happens once Comcast runs out of IPv4 address to give to its customers:
Customers get a new cable modem or router device that does real routed IPv6. You get a real IPv6 address or range of IPv6 addresses and your home network is a directly connected fully functional member of the IPv6 world.
Newer customers won’t get their own IPv4 address anymore. Existing customers would retain their ability to get an IPv4 address for a while but nothing is guaranteed. The modem or home router will hand out private addresses to your home computers and devices. Any attempt to contact the outside IPv4 world will be blindly tunneled over IPv6 to a NAT router that Comcast runs in one of their data centers. Multiple customers will share the same IPv4 address and NAT will be used for all IPv4 connections. This will hurt or possibly prevent many forms of P2P over IPv4. Assuming they didn’t firewall off all incoming IPv6 connections these P2P tools would work normally over IPv6.
At a quick glance it doesn’t seem like an unworkable plan. Of course being NATed by your ISP and not by a router you control will just plain suck. I’d strongly suspect any “NAT” solution they implement on their servers will have to do some inspection of connections (similar to Linux’s conntrack modules) and do a bit more than straight NAT to work around common application problems. Unfortunately if the ISP can’t get any new IP allocations at a reasonable cost and is truly out of IPv4 address then the customer is crap out of luck. The question is exactly under which conditions the transition would start and what restrictions they would place on the IPv6 end of things. And I hope they will read their RFCs and hand out the RFC recommended number of IPv6 IPs to every customer. That is half the point of IPv6 after all.
Update: Comcast’s approach seems to be covered in the IETF document Dual-stack lite broadband deployments post IPv4 exhaustion. On the topic of NAT and IPv4 application compatibility the document says:
Most applications that today work transparently through an IPv4 home
gateway NAT should keep working the same way. However, it is not
expected that applications that requires specific port assignment or
port mapping from the NAT box will keep working. Details and
recommendations for application behavior are outside the scope of
this document and should be discussed in the behave working group.Translation: We chose not to care.


