Sure, but the point is to have IA be the owner of an archive w/ a good, well performing UI/UX. Because: I might build an excellent interface to IA's millions o

Sure, but the point is to have IA be the owner of an archive w/ a good, well performing UI/UX. Because: I might build an excellent interface to IA's millions of images, so good that it becomes the default way of viewing them. Countless bookmarks and links from other sites are published against the material through my site. But then one day I decide it's just not working out anymore and I pack it all up. I call this imaginary system Fleckr. I'm not saying people shouldn't build what they want in this way, but IA shouldn't rely on other services to host anything that it wants to stick around. They appear to have done that with Flickr, because Flickr had a good system, but now it's all dust. Or, if not dust, it will require a complete system to be built to do something similar, migrating user contributions (if they were salvageable) to this new system. I'm saying this new system should be owned & operated by IA. Building it w/ volunteer work under a FOSS license like many other large projects seems a reasonable option.