Slashdot Mirror
A Twitter Client For the Commodore 64
An anonymous reader writes "Johan Van den Brande has developed a Twitter client for the Commodore 64, allowing 140-character messages to be posted directly from this TV-connected 1982 home computer. This YouTube video shows how the Twitter client is — slowly! — loaded from a 5.25" floppy disk, how the latest Twitter messages are downloaded and shown on the TV screen, and how this tweet is posted. All that is needed is a C64, a TV, and a C64 Ethernet card. The Twitter client is implemented with the Contiki operating system, which otherwise is used for connecting tiny embedded systems to the Internet."
There is a Commodore IEEE-bus floppy drive that works great with a C64 with the right adapter. It takes 1.2 Mb floppies and it makes a 1541 look really sad. It was radically expensive at the time and I remember how annoyed my boss was when I told him the price.
We actually had it pretty good even back then. We had a Kontron 6510 ICE so we could go in and figure out exactly what was going on with that weird video hardware, and it was great for finding those odd bugs.
I still cannot believe how badly those 1541 floppy drives sucked. They are the most miserable pieces of computer gear I have ever encountered. It is just beyond belief that someone has managed to keep one working after all these years!
I liked the Atari 800 much better. The video hardware had a much cleaner design and it was a lot easier to code for.
After having to slog through a million and one boring PS3/Xbox360 fanboy wars on pretty much every forum out there, is there anyone else who finds the prospect of a spectrum/C64 slugfest actually quite appealing?
And have I been spending too much time on the Internet?
It's barely a hack. Each of the pieces is pretty much being used for its intended purpose (the C64 is being used as a general computing device, the network card is being used as a network card, there is some software, etc.).
Nerd rage is the funniest rage.
"Attack of the Mutant Camels" refers to completely different games (both by Jeff Minter, mind) in Europe and America.
In Europe, "Attack of the Mutant Camels" was a little bit like defender (with giant radioactive space camels). In America, the game released as "Attack of the Mutant Camels" was what the Europeans call "Gridrunner".
http://en.wikipedia.org/wiki/Attack_of_the_Mutant_Camels
C64 AMC: http://www.youtube.com/watch?v=xhKf3DcPk08
C64 Gridrunner: http://www.youtube.com/watch?v=bRq6e1f85KY
Jeff's "Revenge of the Mutant Camels" was completely insane...
http://en.wikipedia.org/wiki/Revenge_of_the_Mutant_Camels
http://www.youtube.com/watch?v=ymVvsPczrwk
The More You Know...
Actually, if you RTFA, he didn't develop the TCP/IP interface.
This project uses an "MMC replay" C64 expansion box with an RR-net ethernet daughterboard installed. He wrote the Twitter client to run on the Contiki OS, which comes with a built-in TCP/IP stack and a driver for the RR-card. Credit for Contiki and it's uIP TCP/IP stack go primarily to Adam Dunkels:
http://www.sics.se/~adam/
The accomplishment of the C64 Twitter client's author is really more about writing a Twitter client with one hand tied behind your back rather than really being C64 specific. He wrote it in C (CC65 6502 compiler) on Contiki, so the fact that it happens to be running on a C64 as opposed to any other environment that supports Contiki is somewhat irrelevant.
Whether it scores any points for complexity really depends on your level of experience. Given that the ./ readership has become less and less hard core over the years, I think there are many people here who should be avoiding this guy's front lawn. At least, if you've never written any networking code in your life, how about firing up Linux, or installing MinGW (maybe roughly comparable to installing Contiki and CC65 on a C64), then writing your own Twitter client... It certainly won't be a waste of time if you learn how to do socket programming as a result.
Not to mention that, as stated in the summary, this program uses an Ethernet device. I don't own one myself, so I can't be sure of the maximum practical speed, but based on my own hacking and programming on the C64 with PIO and DMA devices, I would guess data moves around at 20-30 kB/sec including TCP/IP and Twitter protocol processing overhead, on an otherwise stock machine.
Although this particular application doesn't need anything beyond an Ethernet device, solutions also exist to counter any CPU, storage, or RAM constraints that a C64 user might run up against.
1. VirtualBox is better optimized for XP (or vice verse). Linux is known to be slower there. Try real equipment.
2. Clean XP install is as useless as a snooze button on a smoke alarm. Install software, for Gods sake! And don't forget an antivirus. We aren't talking about clean lab environment, it's a harsh real virtual world outside.