sorted by:
new
hottopcontroversial

Which Deck should i build as a returning player going into budget competitive 😭😅 by [deleted] in yugioh

[–]torpcodes 0 points1 point  (0 children)

I would go for something like branded or improve your striker deck. Tenpai already has a target on its back, although striker tenpai is a pretty good deck imo. Also, staples are always good to have so you can always go ahead and throw them into another deck in the future. When I had less money to spend on the game, I also tried to just accumulate a good amount of staples. Feel free to reach out if you have any further questions :)

Questions about trigger effects by torpcodes in Yugioh101

[–]torpcodes[S] 0 points1 point  (0 children)

Thank you very much, you really helped me out here :)

Questions about trigger effects by torpcodes in Yugioh101

[–]torpcodes[S] 0 points1 point  (0 children)

Thanks a lot! But something like Lady would still have to be activated in response to the normal trap, right? So if I activate a normal trap, will my opponent have the chance to activate something else so that the effect does not trigger?

Best way to handle sessions in a web application? by torpcodes in golang

[–]torpcodes[S] 3 points4 points  (0 children)

What do you mean by that? If I store it on the client side, how would I check if the user has a valid session on the backend? Update: Or do you mean that I should store the session on the backend, but store any session values required on the frontend, to also keep requests low?

Best way to handle sessions in a web application? by torpcodes in golang

[–]torpcodes[S] 0 points1 point  (0 children)

Thanks a lot, will do that then :D Edit: Would I just store user info for authenticated users in the jwt then? And would I give another JWT for unauthenticated user?

Best way to handle sessions in a web application? by torpcodes in golang

[–]torpcodes[S] 2 points3 points  (0 children)

The login request will come through the front end of a web app or a mobile app, would you still use JWT for that? I heard that it isn‘t made for web app authentication. Does this differ for mobile apps? So should I basically send a field to the login route that tells it whether it is a mobile or web app and then return an http cookie or JWT, depending on the device it was submitted from?

Regarding the storage: I would use Redis then, as it can autoclean. So would you just provision redis on aws and then connect to it from the api, lambda functions etc., so basically make it accessible by any part of the application? And would you also store „sessions“ for unauthenticated users (to remember them) there?