TwIP - An IP Stack In a Tweet
Adam Dunkels writes "Inspired by the Twitter-sized program that crashes Mac OS X, I just wrote a really, really rudimentary IP stack called twIP, small enough to fit in a Twitter tweet. Although
twIP is very far away from a real IP stack,
it can do the first task of any IP stack: respond to
pings. The entire source code can be found in this 128-character-long tweet. For those who are interested in low-level network programming, a code walkthrough with instructions on how to run the code under FreeBSD is available here. The FAQ: Q: why? A: for fun."
The underlying system must provide a way for user programs to receive and send IP packets.
This is where I stopped reading. Just... no. This is just a program that echoes every single thing back to the originator.
Now if you could figure out a way to encode a full 1500 byte packet into 160 characters you'd make some big money.
Shit doesn't smell like roses when it is made to fits into a tweet or is in any other way related to Twitter.
--- Eat my sig.
That's no stack. A stack has a queue, and a set of operations that can be done on items entering and leaving that queue. Description fail!
#fuckbeta #iamslashdot #dicemustdie
I knew I picked the right man when I cited this guy's PhD thesis in my dissertation. Folk who write things like this know their shit, and are probably safe citations, despite the use of Twitter.
I'd have thought that someone that spent his time studying and implementing minimal-waste embedded network stacks and coming up with something like Contiki would be annoyed by the huge waste of bytes that is Twitter.
... in low level system programming, I recommend reading a good book, like this, and not spending any more time reading this.
Seriously.
Here comes the lameness filter:
unsigned short s[70];*l=s+6;t;main(){for(;;){read(0,s,140);s[10]&=65280;s[11]+=8;t=l[1];l[1]=*l;*l=t;write(1,s,140);}}
And with those 9 chars perhaps you could make it better.
How we know is more important than what we know.
Just today on /. one "C" tweet that can crash a Mac, now the second one that creates an IP stack out of one liner. Can your prefered language be so badass?
I tried this particular piece of code out and it works! Of course, the ping buffer and the IP swap is just so obviously simple ... WOW!
The "everything is a file" unix philosophy really does kick in and pull its weight in this example. Sockets, network devices, hardware block devices ... You can write an app to do pretty much anything with any of these, with just file streams. Oh, yeah ... dd'ing entire flash drives, netcating sockets, rsync'ing root partitions over. I often am completely amazed by the complexity that simple pieces can produce.
Now everyone - stop talking bad about twitter ... it's awesome, it's simple and it's given random people the idea that I'm interesting & intelligent ;)
Quidquid latine dictum sit, altum videtur
Haha! This article is rated purple (2 levels above the lowest -- black) already. Wow.
Anyhow. The fact that the TwIP program requires an IP stack to work is the prime indication that it doesn't really do all that much. Since it can work with raw socket access, and switches the addresses around, well, props, but TFA's "header" code comment says this:
updating the ICMP checksum
which is then contradicted by the code comment before the address swap:
Since we only swap bytes in the IP header, we do not need to update the IP header checksum.
using ICMP and IP interchangeably..?
timothy, take this down. Now. It's your only chance to save face with this article.
I hope this isn't a new trend of 7337 |-|@(|0%$ to try to brag of their mad skill by seeing what code can fit in a Tweet.
The less the code doesn't mean better performance.
The less code can mean less functionality and error checking.
The less code does mean less documentation
The less code could mean harder readability.
We need less people taking their time and effort making unreadable small code and more effort in making good and useful applications and libraries. Granted such exercises may be useful to allow you to think of problems differently but you can get the same effect by changing languages say from C to LISP. Also these examples seem to take in include headers which accounts for thousands of lines of code, which are often limited to either the OS or even just the Programming language.
It is like me saying I can make a Web Browser using a shell script with 2 lines.
#!/bin/bash
apachectl start
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Very cool program! Taught me some things about IP. The program could be made one byte shorter by using for(;;) instead of while(1) and it is not strictly necessary to use "unsigned short" instead of "short" afaict. I wonder what other interesting programs that can be written in only 140 bytes.
Football Odds
Is this a implementation of RFC5514? I know that it needs to be IPoSN ( IPv6 over Social Networks) and is probably not, but I wonder how hard it would be to have this do IPv6.
Or is it enough, to boot a normal JavaScript based virtual machine on a normal browser, to use this?
Any sufficiently advanced intelligence is indistinguishable from stupidity.
that program just echoes stdin to stdout (maybe some char manipulations) and YOU have to connect this crap to some prog, which provides the network abilities (netcat might be suitable, i guess)
The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
It's not an IP stack at all (and requires one to function). It replies to a packet that is assumed to be a ping without any error checking. In other words, it's a very short, clever, but minimally functional ping function. The fact that it's short is nice, but that's about it.
impressive, huh?
The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
Well, straight from the IO::All man page but still. It supports CGI! (easily ownable of course)
...is big in the demoscene.
Check out this 4KB realtime demo called 'Receptor'. (Download / Video)
Except for the part where the "stack" requires an underlying sockets implementation.
Mine looks like: http://img340.imageshack.us/img340/8872/slashdot.png
Which is damn annoying since my browser window is already set to use half the screen horizontally (the other half is two xterms one above the other) so it's already not very wide...
comment.c:1: error: âover-exaggerationâ(TM) undeclared (first use in this function)
Win a signed Stephen Carpenter ESP Guitar from the Deftones: http://def-tag.com/?r=0008781
I admire you for this -- not a NOOP sled, not a trojan, not a game, you built a freaking IP stack in 128 chars. I officially declare you my hero, at least until lunch.
I propose TwERP -- an Enterprise Resource Planning app coded in a tweet.
'He who has to break a thing to find out what it is, has left the path of wisdom.' -- Gandalf to Saruman
"Unix is simple. It just takes a genius to understand its simplicity." â" Dennis Ritchie