when I open scratch wiki
wait until <it is fixed>
happy

jvvg wrote:

GratefulGamer9398233 wrote:

jvvg wrote:

Can I have a database dump? No. The database dump contains emails, deleted revisions, and a lot of other information we cannot give out.

What if I said I wanted a database dump without that information?

That's a lot easier said than done.

jvvg wrote:

Hi everyone,

A quick update about the server situation. We have been continuing to experience server and traffic issues, but we have basically maxed out the mitigations we're able to do with our current server stack. Anything else we can do at this point would basically just be a band-aid and have minimal impact on the actual problem. I have reached out to the people in charge of our hosting about this and requested some changes to the server stack that would actually be a sustainable solution, but I can't make any guarantees here.

Some FAQs:

• Why have you not been more responsive? There really isn't much more for us to say beyond “we're aware of the issue and looking into it”. That's been the status for weeks.
  
• Can I set up my own alternative? No. The Scratch Team has placed a level of trust in us to maintain the Wiki to their standards, a level of trust they very rarely give to third-party sites, and I strongly doubt they are interested in passing that on to someone else. In addition, for the levels of traffic we get you will likely find you are going to be dealing with the same problems we are.
  
• Can I have a database dump? No. The database dump contains emails, deleted revisions, and a lot of other information we cannot give out.
  
• So is this the end of the Scratch Wiki? We don't know. It depends on the response I get from the folks in charge of our hosting.
  
• Can I join on the engineering side? No. We appreciate the offer, but we have really maxed out what we can do with our current server stack, and you need a much higher skill level for this than a lot of you probably think you do.
  
• Can you just implement (whatever solution I just thought of)? Probably not. We have done pretty much everything we can on our current server stack. Short of the changes I have requested, anything else would be mostly ineffective, and for why we can't just magically change our server stack, see the next FAQ.
  
• Why can't you just get better servers? Servers cost money, and we are also stuck with what we have for legal and administrative reasons that are out of our control.
  

jvvg wrote:

jvvg wrote:

Hi everyone,

A quick update about the server situation. We have been continuing to experience server and traffic issues, but we have basically maxed out the mitigations we're able to do with our current server stack. Anything else we can do at this point would basically just be a band-aid and have minimal impact on the actual problem. I have reached out to the people in charge of our hosting about this and requested some changes to the server stack that would actually be a sustainable solution, but I can't make any guarantees here.

Some FAQs:

• Why have you not been more responsive? There really isn't much more for us to say beyond “we're aware of the issue and looking into it”. That's been the status for weeks.
  
• Can I set up my own alternative? No. The Scratch Team has placed a level of trust in us to maintain the Wiki to their standards, a level of trust they very rarely give to third-party sites, and I strongly doubt they are interested in passing that on to someone else. In addition, for the levels of traffic we get you will likely find you are going to be dealing with the same problems we are.
  
• Can I have a database dump? No. The database dump contains emails, deleted revisions, and a lot of other information we cannot give out.
  
• So is this the end of the Scratch Wiki? We don't know. It depends on the response I get from the folks in charge of our hosting.
  
• Can I join on the engineering side? No. We appreciate the offer, but we have really maxed out what we can do with our current server stack, and you need a much higher skill level for this than a lot of you probably think you do.
  
• Can you just implement (whatever solution I just thought of)? Probably not. We have done pretty much everything we can on our current server stack. Short of the changes I have requested, anything else would be mostly ineffective, and for why we can't just magically change our server stack, see the next FAQ.
  
• Why can't you just get better servers? Servers cost money, and we are also stuck with what we have for legal and administrative reasons that are out of our control.
  

I'm bumping this up since we're on a new page and I have seen a bunch of questions about why we're getting 503 errors. As of right now I don't have any additional updates to provide.

when green flag clicked
forever
if <maintenance?> then
say [503 error doesn't means service unaliable it means mantinance mode]
end
end

<maintenance?>
<500?>
<404?>
<403?>
<429?>

olliegman wrote:

Scratch wiki is down…

when scratch wiki is down
display [Error 503 v]
play sound [Error! v] until done

olliegman wrote:

olliegman wrote:

Scratch wiki is down…

when scratch wiki is down
display [Error 503 v]
play sound [Error! v] until done

Hi guys! The Scratch Wiki is down. Who will fix it? is it ceebee? Maybe ericr? Idk.

olliegman wrote:

olliegman wrote:

Scratch wiki is down…

when scratch wiki is down
display [Error 503 v]
play sound [Error! v] until done

Hi guys! The Scratch Wiki is down. Who will fix it? is it ceebee? Maybe ericr? Idk.

olliegman wrote:

olliegman wrote:

Scratch wiki is down…

when scratch wiki is down
display [Error 503 v]
play sound [Error! v] until done

Hi guys! The Scratch Wiki is down. Who will fix it? is it ceebee? Maybe ericr? Idk.