Unable to mass install packages

[AlexWayfer]

Hello.

I tried Pulsar. Works good, thank you.

I tried to sync my Atom settings (including customization and packages) via sync-settings (I'd attach a link, but I got the "Too many requests error") and got a lot of packages non-installed:

I thought they were missing in your packages repo. https://web.pulsar-edit.dev/packages does not have search. But checking by name-in-URL shows they exist.

While I tried to search sync-settings package to link it here, I've got the error:

So, I believe it's the reason.

Can you please relax your restrictions, rate limits, or do you have advises how should I do?

It's not a common case for newcomers or who wants to start over, but it can be a common case for migration from Atom.

[Daeraxa]

I thought they were missing in your packages repo. web.pulsar-edit.dev/packages does not have search. But checking by name-in-URL shows they exist.

There is a search but it is on the main screen and not the package list - https://web.pulsar-edit.dev/

The rate limit is still something being tweaked, the main concern is being hit by a bot or something else that would cause the hosting costs to skyrocket for no reason. It should relax after I think 15 mins?

[AlexWayfer]

There is a search but it is on the main screen and not the package list - https://web.pulsar-edit.dev/

OK, thanks. It'd be nice to be placed also somewhere there:

The rate limit is still something being tweaked, the main concern is being hit by a bot or something else that would cause the hosting costs to skyrocket for no reason. It should relax after I think 15 mins?

Sad, but I got it. Thanks.

Maybe later we can use something like Cloudflare or Fastly.

[AlexWayfer]

Also, discussing packages search, they're not indexed by Google. 😔

[confused-Techie]

To echo like previously said, we are trying to find a balance for our current RateLimits, but thanks for reporting that your limit has been hit, I'll look into the request log and bump as may be needed.

Otherwise for the packages search page it may be a good idea to just include the search bar onto every single page if it's causing some confusion.

Then for your last point, are you referring to the packages themselves not being indexed by Google? Or the URL web.pulsar-edit.dev since it should be, I've got the Google Admin Dashboard setup for every subdomain for Pulsar so it may just be showing you a generic web result on that first option.

[AlexWayfer]

Then for your last point, are you referring to the packages themselves not being indexed by Google?

Yep, it could help, like "pulsar linter package" query, you know.

[confused-Techie]

So for the last point I could look into getting it index, thing is we don't block it at all, so hard to say why Google hasn't just done this automatically. But something I had previously looked at was getting the search bar to appear in the search results, like you might see for other websites, that allows you to search the website directly from your Google Search Results.

But we can see what can be done

[AlexWayfer]

The limits are weird.

I've just launched Pulsar today, I think after 24 hours, and already unable to search for packages:

[AlexWayfer]

I'm not entirely sure what you mean with seems the same above.

I mean, the numbers ("300 requests within 15 minutes"), so I see no meaning in their differentiation, but it's your business.

But while we don't maintain the version on AUR the version listed there does match with the beta that has some changes to decrease the amount of hits to the API as well as caches the information received longer, so that's good.

OK, I'll try to contact the AUR package maintainer.

But yeah with 100 packages it can hit that limit rather quickly.

Got it. Sadly. For me it's pretty common usage.

And yeah I'm not placing any blame on you for hitting it, just seems we need to bump it again then since that is very normal usage, and what we would expect.

No offenses for me, thank you for detailed quick answers. I'm trying to do my best in describing issues what I faced.

[AlexWayfer]

But while we don't maintain the version on AUR the version listed there does match with the beta that has some changes to decrease the amount of hits to the API as well as caches the information received longer, so that's good.

OK, I'll try to contact the AUR package maintainer.

v1.101.0-beta is the latest official tag as I see, so I'll not disturb AUR package maintainer until there will be a new version tag.

[confused-Techie]

Ah I see what you mean, well that is to say that any endpoints that require authentication are under different RateLimits.

Such as when you publish, delete, or update a package, or log into your account. That is still rate Limited to 300 requests per 15 minutes.

Meanwhile the generic API RateLimit, such as searching for packages, getting packages, or everything else really is now Rate Limited at 600 requests per 15 minutes.

But I do see how it can be a bit confusing.

But yeah for now the tag you have seems to match our latest so no need to contact them yet. Hope things work out better from here on out for you, feel free to contact us or me again if common usage still gets you RateLimited

[AlexWayfer]

But yeah for now the tag you have seems to match our latest so no need to contact them yet. Hope things work out better from here on out for you, feel free to contact us or me again if common usage still gets you RateLimited

You're great, thanks. I will in any (serious) case. Thank you for your work. I'll try to help as well as I can.

A little off-topic: I'm surprised about how Pulsar faster than the latest Atom (I think any engine update, like Electron, can affect this) and how it's compatible with existing packages. Very impressing, thank you all.

[Daeraxa]

The electron update did actually bump the performance a little and when we clear the path to Electron 19 it promises to actually be quite a bit faster in theory.