Happily Sad, Sadly Happy


She stood firm - a blaze in her eye,
‘That’s as far as you go, or else you die!

‘Your words sting like a thousand spears,
When worse words the Wixen hears!

‘You stand here by my mercy,
For I could throw you deep under sea.’

‘Undoubtedly, I am truly in your debt,
Though I still do wish that we’d never met.

‘For you were to me an elixir of life -
A blessed curse paid for with much strife.

‘We shall part ways as the winds blow,
Fair weathers to you, wherever you go.’

Continue reading

RFC 1149



   This memo describes an experimental method for the encapsulation of
   IP datagrams in avian carriers.  This specification is primarily
   useful in Metropolitan Area Networks.  This is an experimental, not
   recommended standard.  Distribution of this memo is unlimited.

Overview and Rational

   Avian carriers can provide high delay, low throughput, and low
   altitude service.  The connection topology is limited to a single
   point-to-point path for each carrier, used with standard carriers,
   but many carriers can be used without significant interference with
   each other, outside of early spring.  This is because of the 3D ether 
   space available to the carriers, in contrast to the 1D ether used by IEE   E802.3.  The carriers have an intrinsic collision avoidance
   system, which increases availability.  Unlike some network
   technologies, such as packet radio, communication is not limited to
   line-of-sight distance.  Connection oriented service is available in
   some cities, usually based upon a central hub topology.

Frame Format

   The IP datagram is printed, on a small scroll of paper, in
   hexadecimal, with each octet separated by whitestuff and blackstuff.
   The scroll of paper is wrapped around one leg of the avian carrier.
   A band of duct tape is used to secure the datagram's edges.  The
   bandwidth is limited to the leg length.  The MTU is variable, and
   paradoxically, generally increases with increased carrier age.  A
   typical MTU is 256 milligrams.  Some datagram padding may be needed.

   Upon receipt, the duct tape is removed and the paper copy of the
   datagram is optically scanned into a electronically transmittable


   Multiple types of service can be provided with a prioritized pecking
   order.  An additional property is built-in worm detection and
   eradication.  Because IP only guarantees best effort delivery, loss
   of a carrier can be tolerated.  With time, the carriers are self-      regenerating.  While broadcasting is not specified, storms can cause
   data loss.  There is persistent delivery retry, until the carrier
   drops.  Audit trails are automatically generated, and can often be
   found on logs and cable trays.

Security Considerations

   Security is not generally a problem in normal operation, but special
   measures must be taken (such as data encryption) when avian carriers
   are used in a tactical environment.

Source: IETF



Whew, I’ve finally finished it! I’m sure this could be optimised further. I haven’t done extensive tests on it either. Overall, a lot of fun with this. Honestly I don’t think I’ve ever written a program before whose input was more difficult than writing the program itself! (Which is why I didn’t test it. :P)

GitHub repo has the source.



Oh, Stack Overflow


Stack Overflow's 404

Came across this 404 on Stack Overflow today. My favourite would be the Befunge code. I think esoteric languages are fun (though hardly practical) and subtle things like this make it even more fun. I’m working on a Brainf*ck interpreter and good golly! Writing tests for it is a PAIN. D:

If you’re looking for more information about the polyglot, there’s a SO question on it.