hehe theoretically one could undo a supersort, but on 17000 rows it's not as easy to keep in the session -- especially since w/ a search they may have had disparate original values. The other issue would be looking up 17000 rows to get the original values before deleting them (which is what undo does).

17000 snapshots to revert wouldn't be very fun or fast. it's easy to code, but could lead to PHP memory probs on default 8MB

Possibly we could move the undo functionality out of the session and simply serialize it in the ticket table or an intermediary table -- then there's not really an upper limit, just an extra cost to the first action (spam/delete) and some junk hanging around in the DB.