Freesound Forums

As a user, I tried out Freesound on the new hosting provider yesterday and this morning. Everything seems to be working fine.

Thank you all for another great update.

Things all seem smooth to me too
Cheers!

Everything became very fast. Very good. It's just a song. If only you could fix the latest interface issues with displaying its elements...

Hi everyone,

Thanks for your messages. We've been working hard on this, but now we have many things set up. Still many more details to be adjusted and some missing services (no tag recommendaition, no similarity for newly uploaded sounds), but overall the system seems to work quite nicely, much faster than before. We'll keep you posted!

I get a few "429 too many requests" errors, after a few refresh it goes though tho

In regards to moderation, I can see the website is faster as it's harder to select a few "assign to me". Now , after selecting one or two it takes me to my queue faster without having completed my "assign to me" x')
If possible to disable the auto move to moderation queue, and just stay on the "assign sounds" page that would help!
Or having 3-5seconds of waiting time after the last "assign to me" click, would also work.
Many thanks!

I’ve just uploaded a 10-minute file of 123 MB. The file was processed and published in no time at all.
I think the improvements made last week are brilliant.

Thank you very much.

Hi,

Thanks for your nice words. The truth is that Freesound is running super fast now, and we still have many things to tweak. We should hava made this move ages ago

@Sadiquecat: we'll look into this, I don't remember quite well now but maybe the assign process is happening asyncronnously and the next page loads so fast that the initial process is not finished yet. About the 429s, can you elaborate more? We put some limits in place as we found out that we were being abused by more bots than we thought, but we might still be able to adjust some things.

Hi Frederic and friends !
Personally, I can’t say anything about the moderation process, but as a regular user, looks like everything is faster and smoother.
Great job !

Wishing you all the best !

Kevin

I don't know if I am on the new hosting provider, but I get 429 errors way to fast, I can not even look at 3 pages of results without being blocked.

Hi Frederic,
To clarify for the Assign thing. It does work where sounds do get assigned without issues.
The difference being before I could use the loading time to assign a dozen users before it moved on. Here I can assign a first user maybe two and it loads the page.
It's less practical do select a couple users but it does work for A user or assigning all tickets.
But the assign feature does work.
It's just I haven't finished doing my selection at a human level, but technically once I selected a "assign to me" it does go though as it should. I just wish to assign more before moving pages.

For the 429 error I'm not sure what I can say more about it. When loading a page it sometimes shows that error, both on computer, laptop (ios) and phone (android) using chrome, mentioning "429 too many requests - nginx/1.27.5". After refreshing the page a few times it does load.
For example I just had it for this link https://freesound.org/search/?f=username:%22Sadiquecat%22&s=Date+added+(newest+first)&g=0
I also had it searching for a user's packs.
This happens very frequently. I can get it multiple times in a minute.

Cheers!

Sadiquecat wrote:
For the 429 error I'm not sure what I can say more about it. When loading a page it sometimes shows that error, both on computer, laptop (ios) and phone (android) using chrome, mentioning "429 too many requests - nginx/1.27.5". After refreshing the page a few times it does load.
This happens very frequently. I can get it multiple times in a minute.

Cheers!

Hi Sadiquecat. We noticed that we had some botnets attacking freesound and so we introduced some rate limits to the tags, browse, and search pages of 5 requests per second. If you're encountering this error then the limit is probably too aggressive. I'll reduce it to allow a bit more access. We're also looking into some other tools to help us with this and we might roll them out over the next weeks. Of course, we don't want to say exactly what the limits are in case people use this knowledge to bypass the limits But if you find that you still get the limits with what you think is a "reasonable" usage then please let us know and we'll continue to tweak it!

Hi,
I think you could have the same average rate, but with a bigger buffer.
Like if it was 150 requests over 30s, that would still be 5 requests per second average but way more human friendly.

Like I assume a typical use case could be opening 30 sounds across 5 pages, and then monitor them over a few minutes to find the right one.

So a human user may have high activity at one time but not consistently.

I'll report back if I get the issue
But with a quick stress test opening a few sounds and moving across a few pages, I didn't encounter it so far
Thanks!