Features being considered for future releases of TightURL:

XML-RPC & SOAP APIs
-------------------
One or both of these may be added to the TightURL API.

Persuade Shorlify Maintainer to Support TightURL
------------------------------------------------
This would be dependent on getting TightURL support into the
CPAN makeashorterlink package first.

Non-deterministic IDs
---------------------

Right now a feature of TightURL is that its URLs are as short as 
possible, and no space is wasted in the database with duplicates.

This results in deterministic (predictable) Tight URLs, and the ability
to query to determine if a given destination URL has already been entered
into the system.

Future versions of TightURL may contain a configuration setting in 
tighturl.config.inc.php that allows you to have non-deterministic
(random) TightURL URLs and duplicate destination URLs in the database,
at the expense of possibly generating a slightly larger URL than
necessary.

Use PEAR Net_DNS
----------------

checkdnsrr() only provides knowledge that DNS records exist of the
type being asked for.  It does not provide the records themselves,
thus we cannot decode the address, which might be useful at some
point.

Positive: PEAR's Net_DNS routines return the actual DNS records.
Negative: Would be a new dependency on PEAR Net_DNS being installed.

checkdnsrr() does not work in PHP for Windows.  Switching to PEAR
Net_DNS would also make TightURL Windows-compatible.