InsaneJournal Announcements

Potential Move to AWS

InsaneJournal Announcements

Potential Move to AWS

Previous Entry Add to Memories Tell a Friend Next Entry
I'm reading through the AWS Acceptable Use Policy. I don't think anything there precludes hosting InsaneJournal there. I feel that our existing Terms of Service falls in line with this. I'd love to have an open discussion about this, so please comment with concerns. Please keep all conversations civil.


No Illegal, Harmful, or Offensive Use or Content

* You may not use, or encourage, promote, facilitate or instruct others to use, the Services or AWS Site for any illegal, harmful, fraudulent, infringing or offensive use, or to transmit, store, display, distribute or otherwise make available content that is illegal, harmful, fraudulent, infringing or offensive. Prohibited activities or content include:

* Illegal, Harmful or Fraudulent Activities. Any activities that are illegal, that violate the rights of others, or that may be harmful to others, our operations or reputation, including disseminating, promoting or facilitating child pornography, offering or disseminating fraudulent goods, services, schemes, or promotions, make-money-fast schemes, ponzi and pyramid schemes, phishing, or pharming.

* Infringing Content. Content that infringes or misappropriates the intellectual property or proprietary rights of others.

* Offensive Content. Content that is defamatory, obscene, abusive, invasive of privacy, or otherwise objectionable, including content that constitutes child pornography, relates to bestiality, or depicts non-consensual sex acts.

* Harmful Content. Content or other computer technology that may damage, interfere with, surreptitiously intercept, or expropriate any system, program, or data, including viruses, Trojan horses, worms, time bombs, or cancelbots.
  • re: alternate plans for a hardware fundraiser mentioned in another comment

    I know AWS provides a lot of support. If you went with this option instead, would the quality of support be on par? Or would everything fall on you?

    I understand people have concerns and appreciate that you want an open dialogue with your customer base, but your customer base has to look at you as the technical expert here. People are concerned that they will lose their writing, their journals, their paid accounts, their icons during the migration. As the technical expert, it is up to you to answer those questions and concerns and not necessarily automatically default to another solution.

    Upgrading to new servers doesn't necessarily negate the concerns either. Again, you have to tell us what to expect from that kind of migration. Is upgrading to new servers a cost effective solution if you will need a fundraiser for it? I assume some upkeep will be necessary which will also cost money.

    As for the concerns that people will have to move to Dreamwidth to escape Terms of Service, you've already established that DW is already hosted there.

    Thank you for pushing progress on IJ. Your transparency is so appreciated.
    • Re: alternate plans for a hardware fundraiser mentioned in another comment

      So I'm confident in maintaining a certain service level either way. AWS would afford us the ability to go a bit further beyond what we are doing now, which would be ideal. There is also the option of using the cloud for bursting during times of heavy use even if we stay with our own hardware, but I don't want to get ahead of myself
Powered by InsaneJournal