Rhonir(Common Patron)
33 days{"ops":[{"insert":"Good day,\n\nI've been using archidekt for about 2 years now and am really satisfied with a lot of features it offers. I'm even a (small tier) Patreon member. But the request throttle when you open more than 5 decks at a time or when you do things too fast is really bothersome. I would be half-okay with it if it woudln't also happen when doing basic things inside a deck as of late. Just now I just wanted to put a couple dozen of cards into the sideboard by repeatedly pressing \"s\", as it leaves the before affixed categories intact. I've been doing this just fine for as long as I've been using this website but now it throttles my request after pressing \"s\" about 8-10 times. Come on, this can't be real. If this continues I'm literally forced to switch just because I can legit not use the website properly...\n\nKind regards from Germany\n"}]}
0
michael(Alpha User)
32 days{"ops":[{"insert":"If you're hitting the request limit while editing decks regularly, I'm impressed. The limit is something like 80 requests per any 60 second period, so you must be absolutely zipping through actions. Some actions require 2 or more requests, these types of actions are usually uncommon, particularly for more than 2 requests per action. The specifics aren't worth going into, but in general that leaves users with 40-60 APM. \n\nThe reason that throttle exists is to prevent users from spamming our API, which we've had issues with in the past. People will intentionally and continuously send requests maliciously to attempt to cause issues with our api. \n\nWe tend to be pretty firm with that request limit, since lowering it means a more vulnerable site in general. There's only so many connections that can be open to our database at once, so if we're getting bombarded with requests, this causes everyone else on the site to have a worse experience. \n\nI'll do some testing and see if we can reasonably increase that limit a bit. But the limit we currently have is rather high, how are you interacting with the site to cause throttling with regularity? You mentioned using the S keybind, which 100% could potentially cause a thottled response if clicked 20-30 times in quick succession. I can't imagine that kind of deck editing behavior is common to your workflow though, so how else are you interacting with the site to cause the throttle? \n"}]}
0
Rhonir(Common Patron)
30 days{"ops":[{"insert":"Many thanks for the quick and in-depth response! I am indeed a fast worker but there are a lot of scenarios where I don't think I hit those limits. For instance the beforementioned sideboard-switching. In that case I get a throttle when pressing \"s\" about 10 times in quick succession. This is also a new problem, until a couple weeks ago (last time I used the website) I could spam \"s\" as many times as I wanted. \n\nAnother time I get throttled is when I go through my folders and open around 7+ decks in new tabs at once. I do this sometimes because I know there's card xyz that would fit perfectly in my new deck but I can't remember in which deck I've put it before. Or when I want to see what other people on this website built and I open 7+ decks at the same time. Every further deck opened then becomes a throttle message\n\nOne suggestion would be to change it so that multi-select > right-click > \"add Sideboard as a category\" leaves the categories already in place intact. Currently it just overrides them so when you click \"a\" on a card in the sideboard it's just getting moved to the maindeck by its type and that's it. Reason for this suggestion is that when I build a deck I collect everything I can think of and find fitting for the strategy I'm building around and when I'm finished (usually around 200 cards) I sort them all into categories, clone the deck, move all cards in the original deck into the sideboard and use the cloned deck as reference to add cards from the SB into the main deck by pressing \"a\". (This method makes it a lot easier to build a deck since you don't cut, you just add until hitting 100 cards).\n"}]}
0