How about some NSFW warnings on those links you have there? I couldn't care less that you are running porn but please put a warning on the links for us that have watchers watching us.
On Nov 22, 3:04 am, "Brandon Wirtz" <drak...@digerat.com> wrote: > I'm not real worried. As I said I wanted to know if I could start offering > services to adult sites, and what the limitations would be. It'd be nice to > have my "suckingon.com" url working, but I'm not planning on quitting my day > job to be in the adult business. Or in the whole sale Lollipop and Sucker > business either. Sucker Fish for your exotic fish aquarium. I could go in > to, but I'm not hosting that on GAE. The uptime isn't there for such a high > demand 24/7 business :-) > > Getting the hold taken off of my login was a fun conversation. Tech support > didn't seem real amused at "hairypubicarea.com" which seems to be > permanently in state of limbo now, despite putting the DNS in place to claim > it. > > Aren't you glad I didn't pop for the $500 a month yet? We could have been > talking about this on the phone. with the "monitored for quality assurance" > recordings going the whole way :-) > > In the meantime enjoy thehttp://suckingon.appspot.combut to get the Apps > For Domains people moving a little faster you might consider pointing out > that you can't currently require that adult content not be presented on the > AppSpot.com domain. ( I was really tempted to use the "powered by google" > on the page and decided I didn't have enough lawyer on retainer this month) > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Gregory D'alesandre > Sent: Monday, November 21, 2011 11:24 PM > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Fine GAE Team LIES! Porn on GAE Not So Much > > Thanks for highlighting the issue with associating "racy" domain names with > Google Apps, I'll see what we can do to resolve, it might take some time... > > Greg > > On Mon, Nov 21, 2011 at 10:33 PM, Brandon Wirtz <drak...@digerat.com> wrote: > > Link is NSFW: > > Since I couldn't get appsfordomains to take any of my domains. and I suspect > that even if I did, that they would turn me off later. I'm using the > "Naked" Appspot.com urls > > http://suckingon.appspot.com runshttp://www.cdninabox.comon Python 2.7 > with Thread Safe enabled. There are a few bugs, but poof! Adult site > running On GAE. > > This is mostly there to prove Google is aware that there are adult sites, > are ok with it, and to work through the issues relating to setting one up > with the related products. > > I haven't yet enabled billing. I am not sure Google Wallet allows for me to > pay for adult services :-) > > I am not sure I can make any money at the cost of hosting. Adult Free sites > are not highly monetizable. But GAE is probably cheap compared to most > adult hosing solutions. > > Where this is bad for "The Rest of us" is that my adult site occupies a GAE > IP range, so schools and places that filter adult content using IP may start > blocking all of GAE to prevent kids from watching content on > Suckingon.appspot.com > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer > Sent: Monday, November 21, 2011 8:02 AM > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Fine GAE Team LIES! Porn on GAE Not So Much > > This is hilarious. I would love to be a fly on the wall in one of Google's > conference rooms while this gets hashed out between the Google Apps team and > the GAE team. > > Back in my pr0n days our conference room shared a wall with one of the film > sets. I would routinely have interviews in the middle of the afternoon > while there were all sorts of... noises... coming from next door. If the > candidate couldn't block out the distraction and solve programming problems, > I knew it wasn't a good fit. I'm not sure HR would have approved :-) > > Jeff > > On Mon, Nov 21, 2011 at 10:37 AM, Brandon Wirtz <drak...@digerat.com> wrote: > > And in case anyone missed it the "lies" was meant sarcastically, I know that > the issues aren't GAE's team and they didn't mean to say you could do it, > just that the rest of Google hasn't caught up. > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz > Sent: Sunday, November 20, 2011 9:12 PM > To: google-appengine@googlegroups.com > Subject: RE: [google-appengine] Fine GAE Team LIES! Porn on GAE Not So Much > > Note to self: Don't Try things on your primary account. > > Now when I login I am greeted with Your account has been disabled. > Apparently Even without getting the porn in place the domain was enough to > cause problems. > > I would say Google isn't quite ready for adult hosting. > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz > Sent: Sunday, November 20, 2011 8:20 PM > To: google-appengine@googlegroups.com > Subject: [google-appengine] Fine GAE Team LIES! Porn on GAE Not So Much > > So you are all excited that you can host Porn on GAE. You go to the trouble > to set up the code for a porn site to try it out. (I can't sell a product if > I haven't tested it). You are just about ready to deploy it, and.. You find > out Apps for Domains (My constant nemesis) won't let you have any "Good" > porn names. > > SuckingOn.com seemed like a great Porn Site name. Good for SEO, Short, Easy > To Spell, Only trouble. Apps For Domains says you can't have any domain > with suck in it. You can't even have something like WholeSaleSuckerfish.com > or LollipopsAndSuckers.com (I own one of those two domains) > > Turns out you can't have anything with the word SEX, Fuck, or several body > parts. > > So Fine.www.hairypubicarea.comit is. (yes I wanted the most offensive name > I could come up with that would pass the Word screening) Only when I go to > deploy the app. I get mysterious errors. (ScreenShot Below) > > So can you build an app that is "adult" in nature. Sure (nothing other than > the TOS prevented this before) Can you deploy the app. Well only if you > stay off the offensive word list. And the word list isn't the same > everywhere. If someone from GAE wants to assist in deploying my porn site, > I'm sure it would be an excellent exercise in working through the HR issues > associated with working in the adult space. I'm sure when I call to talk to > tech support about my Hairy Pubic Area they will be very happy to help. And > all those nudie pics when we test to see that it is finally working will be > great for the people in the call center. But seriously. I'm blocked by > Apps For Domains (Again) and that group is making Liars out of the GAE > group. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com > <mailto:google-appengine%2bunsubscr...@googlegroups.com> . > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > > I am the 20% > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com > <mailto:google-appengine%2bunsubscr...@googlegroups.com> . > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. > > image001.jpg > 39KViewDownload > > image002.jpg > 26KViewDownload -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
