ipswbot is special. He tells you about stuff that goes on as it happens (first, actually). You should want him in your channel. If you do, contact me!
More about this:
When any event happens in terms of the fwlinks updaters (i.e. firmware, iTunes, redsn0w, PwnageTool, iFaith, sn0wbreeze, etc release or SHSH signing changes), ipswbot actually posts by default to the IRC channels that he's in, in a format similar to this:
[10:55] <+ipswbot> [Update] Something awesome has happened! (but kinda more detailed :P)
And yes, he's a "he".
So, onto the commands.
Commands are as follows:
!firmware- for firmware releases following the format:
!fw <identifier> (buildid/version) (request)
!itunes- for iTunes releases following the format:
!it <Operating System> (version) (request)
!redsn0w- for redsn0w releases following the format:
!rs <Operating System> (version) (request)
!pwnagetool- for pwnagetool releases (got the idea yet? :P) following the format:
!pt (version) (request)
!tss- for TSS (SHSH signing!) requests - powered by Neal's API. following the format:
!shsh- for finding out SHSH blobs found on Cydia's SHSH cache server. following the format:
<item> indicates a required field. If the items in brackets are not found, they will default to the following:
<identifier>is the identifier of the device you want, or the boardconfig. e.g. iPhone4,1 or n94ap
<buildid>is the BuildIdentifier of the firmware file, found in the BuildManifest.plist or Restore.plist of the IPSW file. Also the filename of the IPSW (see diagram below)
<version>is the version of the IPSW/tool (see diagram below)
<request>is the data you wish to request - see the Firmware Links API documentation for all possibilities.
e.g. iPhone3,1_4.1_8B117_Restore.ipsw |_______| |_| |___| | | | | | \----- BuildID: 8B117 | \---------- Version: 4.1 \----------------- Identifier/device: iPhone3,1
!rs Windows 0.9.15b3 url
!fw iPhone2,1 latest version
!fw n81ap latest datefound
!iTunes Windows 11.0.5 url
This documentation and the ipswbot will most likely receive updates in the near future.
IPSW Downloads and the IPSW Downloads API would not have been possible without the help of Neal and his hard work.