4 ms·

If it was server storage related, then we don't mind helping them out =)

by moolave 16y ago

tszming 16y ago
They use Amazon S3 for storage in the past, not sure if it is still valid for now.
- moolave 16y ago
  Then I hope we can help them if given the opportunity. The site is working so far. Thanks for the feedback, folks. http://moolave.tk/ http://moolave.tk/
bl4k 16y ago
I have been in this situation with high profile sites before. When there is downtime that is very public like this incident, you get a flood of emails and calls from service providers offering to help. This can actually often work, a relationship I established with a particular hosting provider (who I introduced to numerous other people as well) started out during a downtime incident when an executive of the company sent an email. If you are a startup that offers services, I would recommend taking advantage of these opportunities to get new business (put on a good pitch at a time when the potential client is vulnerable).
jeff18 16y ago
Ironically, I am trying to go to your site to see what you do and am getting the following error: Error Request-URI Too Large The requested URL /... is too large to process.
- deleted 16y ago
  [deleted]
- mike-cardwell 16y ago
  And when I try to view http://moolave.tk/ http://moolave.tk/ in Firefox I just get a message saying: This content cannot be displayed in a frame. To protect your security, the publisher of this content does not allow it to be displayed in a frame.
  - m0tive 16y ago
    I also got NoScript's cross-site scripting filter kicking in which is never a good thing...
    - moolave 16y ago
      Thanks for the input. For some reason it works on Chrome and Firefox on my side. I will check and see what I find.
  - pbhjpbhj 16y ago
    It works for me but seems to be a weird structure of a regular site hooking in a google sites frame which bootstraps a wix flash page which frames the actual site content.
    - moolave 16y ago
      Yes, we designed the website from the Wix Flash platform and published it on Google Sites. We still have to make some changes as the right-hand side is taking some space on high-resolution screens.
- moolave 16y ago
  Thanks Jeff. It might have something to do with Google running slow (with Gmail and other applications having the same challenge). I will check and see what's causing it.
  - moolave 16y ago
    It could be one of many problems, but I checked a similar thread reporting the same issue; only this time the issue was addressed under Gmail (still Google) http://www.google.com/support/forum/p/gmail/thread?tid=3560202027c7d5ab&hl=en http://www.google.com/support/forum/p/gmail/thread?tid=35602...

If it was server storage related, then we don't mind helping them out =)

by moolave 16y ago

If it was server storage related, then we don't mind helping them out =)

tszming 16y ago

They use Amazon S3 for storage in the past, not sure if it is still valid for now.

moolave 16y ago
Then I hope we can help them if given the opportunity. The site is working so far. Thanks for the feedback, folks. http://moolave.tk/ http://moolave.tk/

bl4k 16y ago

I have been in this situation with high profile sites before. When there is downtime that is very public like this incident, you get a flood of emails and calls from service providers offering to help. This can actually often work, a relationship I established with a particular hosting provider (who I introduced to numerous other people as well) started out during a downtime incident when an executive of the company sent an email. If you are a startup that offers services, I would recommend taking advantage of these opportunities to get new business (put on a good pitch at a time when the potential client is vulnerable).

jeff18 16y ago

Ironically, I am trying to go to your site to see what you do and am getting the following error: Error Request-URI Too Large The requested URL /... is too large to process.

deleted 16y ago
[deleted]
mike-cardwell 16y ago
And when I try to view http://moolave.tk/ http://moolave.tk/ in Firefox I just get a message saying: This content cannot be displayed in a frame. To protect your security, the publisher of this content does not allow it to be displayed in a frame.
- m0tive 16y ago
  I also got NoScript's cross-site scripting filter kicking in which is never a good thing...
  - moolave 16y ago
    Thanks for the input. For some reason it works on Chrome and Firefox on my side. I will check and see what I find.
- pbhjpbhj 16y ago
  It works for me but seems to be a weird structure of a regular site hooking in a google sites frame which bootstraps a wix flash page which frames the actual site content.
  - moolave 16y ago
    Yes, we designed the website from the Wix Flash platform and published it on Google Sites. We still have to make some changes as the right-hand side is taking some space on high-resolution screens.
moolave 16y ago
Thanks Jeff. It might have something to do with Google running slow (with Gmail and other applications having the same challenge). I will check and see what's causing it.
- moolave 16y ago
  It could be one of many problems, but I checked a similar thread reporting the same issue; only this time the issue was addressed under Gmail (still Google) http://www.google.com/support/forum/p/gmail/thread?tid=3560202027c7d5ab&hl=en http://www.google.com/support/forum/p/gmail/thread?tid=35602...