That’s right, we’ve disabled the random-images, latest-images, and upload functions to combat customer abuse, namely the uploading of pornographic images. I’ve even been able to detect (and quickly remove and ban) at least one instance of bestiality pornography, which is illegal as well as disgusting.

What are we going to do about it?

• Add enhanced admin controls to let me quickly view and moderate uploads by group, and view and moderate the old uploads which are not in the database
• Place all new photos into a moderation queue until they are rated for content by at least three people
• Add a cookie-based preference which must be set before a user can moderate content, so that users agree they are adults in their countries and warning them that they might see anything that has been uploaded
• Place all X-rated content after moderation into a nasties queue for me to action
• Consider implementing a SVM to detect pornography in the images themselves
• Create policies which define what a pornographic image is

Until we can prevent, filter, eliminate, and ban pornography, the site will be disabled. On the upside, with a clear policy in place and human reviewers, it should become easier for us to handle this kind of content.

This post is tagged with: human reviewers, customer abuse, pornographic image, pornographic images, random images, least three people, svm, new photos, moderation, queue, uploading, pornography, uploads, preference, adults

We’ve rolled out a proxy-host to buffer bandwidth on this site because it’s costing too much money!

We’re still storing your photos using Amazon S3 so they’re safe and secure for all time, but downloading them will now occur through Distributed Cache Node 1 hosted on FeiFei.us, a 2.8 TB / month server. So far (and you can go check out IMGFLYDCN1 yourself) it is caching 1,394,848,217 bytes and 14,201 files.

The reason for this is that using Amazon S3 to transfer files is prohibitively expensive. I can’t afford to be paying $300+ a month for bandwidth:

The solution is a distributed cache network I’ve rolled out, starting with Fei Fei dot US:

The technical details are quite simple: A visitor requests static.imgfly.com, which decides which cache server to forward the request to. Currently this is quite simple–all requests go to IMGFLYDCN1. In the future, as ImgFly grows, we can scale the bandwidth demands by adding additional servers in rotation.

My ultimate goal is to make this complete server-side configurable, so that I can simply add the server URL, login, and password to a form and automatically provision the machine with the proxy-client software. The server software will actively monitor the performance of client proxies, so if one goes down it can transparently fail over to the others. Additionally, the clients will make available metrics (hit / miss ratios, number of items, size, bandwidth used, bandwidth left) that the server can poll and track. It could be set up so that once a given client reaches a certain metric limit, it’s automatically pulled out of rotation.

As always, comments are appreciated!

This post is tagged with: amazon s3, bandwidth demands, proxy solution, fei fei, proxy host, proxy client, cache server, visitor requests, server url, client software, proxies, server software, metrics, server side, technical details, ratios, provision, tb, servers, photos