@Alexander: Textastic also obviously tells te system photos are plain text files, then, because all plain text editors in the system suddenly claim to be able to open those too: http://cl.ly/FjMM – issues goes away with Textastic uninstalled. Seems the boundary between binary and plain text is muddled by it, or, to paraphrase Hamlet: something is rotten in the kingdom of UTImark :).

The problem is even worse than Textastic taking over *one* spot in the “Open In” menu (which one can be on the fence about re. upload ability): Textastic introduces a bug in the whole “Open In” system for PDFs – when it is installed, *all* text editors on the iPad suddenly pop up there: Pages, Byword and WritingKit all claim to be able to open PDFs with Textastic installed, which they are not able to, and do not pretend to do otherwise!

Screenshot without Textastic installed: http://cl.ly/FjTF
… and with Textastic installed: http://cl.ly/Fjc3

As far as I can tell, Textastic is messing up the whole Launch Services system by claiming to be able to open *any* file – Pages and co. have also randomly turned up in the “Open In” menu for photos and basically every other binary file along Textastic (not reproducibly so, though, unlike for PDFs).