Gerhard Lazu

But it means that bad actors, again, I shouldn't be using that.

Unhappy people.

I can see for this specific episode being a very simple fix, right?

Because we can just serve basically a location header and we just do redirect and that's it.

We're done with it.

So it'd be like another synthetic response.

Exactly, exactly.

And we have other clients, which are, for example, we've seen that PaaS,

where they're basically busting the cash and purposefully going to R2 directly and just varnishes like a, almost like acts like a proxy in this case.

So we have that as well.

We have every now and then we have like this, this random client that comes and downloads all the episodes and that's not the problem.

So I think that some sort of a throttle would make sense, which would keep the system fair to everybody, but the throttle needs to be high enough so that it doesn't impact anyone else.

Now, if for example, our requests or like if our audience grows or we become more popular and we get more requests, obviously we would need to be aware of where the limit is and start increasing the limits, right?

Once we are throttling too much, maybe.

That seems to be more like long-term and it seems more, I don't know, like a well-engineered approach in a way.

But certainly the simplest thing would be just like take this one URL.

I mean, that could be done in minutes, roll it out.

And then we would stop this abuse for this specific MP3.

That would be the easiest thing for sure.

So yeah, I can see the, how pragmatic that approach is.