Image hosting on appspot, few questions.

[Rohan Chandiramani]

Greetings gentlemen,

I'm close to starting my app and it's main function will be hosting images.

1. I'm thinking about keeping the images for only a day, Master/slave would be a cheaper and faster solution, could anyone give an opinion on that?(also considering the recent instability on appspot regarding M/S.)

2. I'm scared about what people will be uploading, child pornography and such. how does this affect me as owner of the app and how am i legally eligible for that?

Thanks, i'm hoping for a reply.

Regards,

Rohan

[Ikai Lan (Google)]

Yes, you are legally responsible for policing the content per the terms of service. 

I would almost never advice anyone starts an app on Master/Slave. Actually ... I just don't advise it at all, period. 

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com | twitter.com/ikai

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/BThpw2n7T0EJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Rohan Chandiramani]

Thanks for the quick response,

HR it is then.

If would like to follow up on your answer.

What is google's view on policing?

Let's say i put a report button and mark it for deletion after *a few* reports and ban the ip after *a few* deleted images , would that be sufficient?

Thanks,

Rohan

[Ikai Lan (Google)]

I'm not very good at playing the "what if" game, but you're usually okay as long as you make a conscious effort to fight bad content. If it gets reported to us and we ask you to take it down (and you do), that's usually enough. If it gets to to the point where it's overwhelming, we may ask you to require moderation before users are allowed to post, but again, that's playing the speculation game.

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com | twitter.com/ikai

Rohan

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Jc3t58-eLi8J.

[Rohan Chandiramani]

Alright that sounds very reasonable.

Sorry for the delayed response, it was getting late in europe-land.

Thanks a lot!

[Kenneth]

Note also that the cost for blobstore in hr is cheaper and I believe the hr cost is coming down when app engine exists beta.

Regarding storing images, caching is your friend.

[Rohan Chandiramani]

Could you elaborate that a little further?

Right now i'm saving the image to the blobstore and serve the images with ImageService.getServiceUrl().

So with caching, do you mean:

The user upload his image and the image itself is cached locally?

or

The image get's memcached, but what good would that do, does the blobstore use memcache?

Sorry, i'm a still a newbie at AppEngine.

Thanks, looking forward to your reply.