glitch.me is clearly intended for small experiments, not for dealing with 10s of thousands of hits in just a few minutes.

I'm getting the author to move it.

Stand by ...

OK, here:

https://somethingorotherwhatever.com/wobble-clock/

Very cool, can imagine that on my Apple Watch

it's back!

worth noting that anyone can remix the project :) https://glitch.com/edit/#!/wobble-clock

As mentioned elsewhere, not my project.

Even when I've got a front page article in the past on HN at like 150 votes I only got about 6000 views in a day. This one has like 10 likes so I doubt it's getting 10s of thousands in a minute. Can only imagine it's some severe rate limiting to push glitch.me users for some paid alternative.

When some of my submissions have hit the front page I got a lot more that 6K views in a day, although probably 10K in some minutes is an overestimate, possibly by a lot.

Agreed that it's probably glitch.me pushing people to a paid option, but there's no real problem with that ... they are a business providing a service.

We love to see these sorts of projects running on Glitch with OR without a paid account!

We do have some default protections in place to prevent (even accidentally) problematic projects from taking too many shared resources.

We've temporarily removed those barriers for this project since it was getting such a big hug. It should stay up and be Remixable now.

disclaimer: I'm on the engineering team at Glitch.

okay but this was maybe a few hundred thousand requests over about an hour for 536 bytes of html and two js files of respectively 2232 bytes and 2667 bytes

like, an old netbook could serve up all those requests in 100 milliseconds with apache

on a 9600 baud modem (5 kilobytes 300_000 times an hour is under 4 kilobits per second)

are you hosting glitch.me on an amiga 500 on dialup in zimbabwe or something

I won't go into a ton of specifics, but we talk about the general limitations for projects here: https://help.glitch.com/kb/article/17-technical-restrictions...

it sounds like you accidentally set your request rate limit about four orders of magnitude lower than the other limits, because you set them to 4000 requests per hour, which is about a ten-millionth of a laptop

by contrast the 512 megabytes of ram is about a 64th of a laptop and the 712 megabytes of disk is about a thousandth of a laptop

this results in absurd situations like this one, where a purely static web app collapsed under a load you could literally handle on a commodore 64 on dialup

well, i guess with tls you might need a 25-MHz 386 on dialup

To be clear, we’ve got Glitch projects doing a lot more volume than that, especially for static apps. This one was hitting our rate-limiting but that was a bit of an outlier and should be fixed now.

Perhaps they serve requests in bursts, just like how this clock works.

Some sort of "wobble server" technology?