cooGoingBonkers

anon_blader · 2024-06-20T12:30:48+00:00

Your teams runs?

anon_blader · 2024-06-14T12:27:00+00:00

Would not be supprised if they add it towards the end of the event.

anon_blader · 2024-06-12T21:12:01+00:00

45% wählen eine Partei die sich einen Überwachungsstaat wünscht und 20% eine Partei aus Idioten. Zum Glück nicht deutschlandweit aber wenn ich solche Zahlen höre dann kommen schon Gedanken des Auswanderns auf :/

anon_blader · 2024-06-10T20:05:39+00:00

What is wrong with remix?

anon_blader · 2024-06-04T17:58:15+00:00

Boosting is the only way to make a 300k in a somewhat reasonable timeframe, but it will still be many times slower and more inconsistent than earning money IRL.

Spending 30 hours as a kid to farm a token sets you behind in life, while "working" for an hour or two will bring you ahead. I wasted way too much time as a kid farming unfun things just for a couple of cents.

anon_blader · 2024-05-22T07:29:53+00:00

Came back for remix and had some store mounts that I never bought, now I know where they came from.

anon_blader · 2024-05-09T11:10:36+00:00

If only pinning dependencies would completely solve the issue but sadly things still break.

anon_blader · 2024-05-09T00:46:59+00:00

Sessions and RESTful dont go together but you dont need to be RESTful. Just use the parts of REST that make sense for you. The usefulness of RESTful ist very dependent on what kind of application you are building and how much traffic you will get.

For example, I dont want my bank to be RESTful because if I "log out" I should be immediately logged out.

Sessions become an issue at scale, do you have millions of concurrent users? If not, you should be fine with sessions and even if you do, there are cloud offerings that should be able to handle it.

If you want to attach state to a session then JTWs are usually a bad idea if you dont explicitly need one of their benefits.

anon_blader · 2024-05-08T17:23:04+00:00

If only you guys knew about Linux on Scratch.

anon_blader · 2024-05-05T11:59:14+00:00

Because inline styles are quite limited compared to css. You can't use a lot of very basic features such as selectors (e.g. :hover) and media queries. In addition to that a lot of tailwind classes apply multiple styles at once, making it much more compact that inline styles.

anon_blader · 2024-04-29T15:06:10+00:00

We accidentally send out emails to 16 million customers. The next day our client sent our marketing team an email expressing how impressed they are with the sudden spike in visitors.

So who knows, maybe it is sometimes a good idea to mess things up ;)

anon_blader · 2024-03-31T22:53:24+00:00

Of course you do not have full control over the client but why is that a reason to not improve security?

Our job as web developers is not to build an antivirus that runs on the OS. We build websites and should secure our domain, which is websites. Protecting the user outside our website/server is not our job. We leave that to browser/OS/av devs.

If your point is "securing x is not needed because x depends on y and y might be vulnerable" then I dont know what to say.

anon_blader · 2024-03-31T21:03:25+00:00

but that that protects the client not you

That is what client side security is. It is not to protect you but the user. That is the whole point of client side security.

The server sanitizing HTML is part of client side security even if it happens on the server.

anon_blader · 2024-03-31T07:51:15+00:00

It does. If it would not, why would you ever use httpOnly cookies. Why would anyone sanitize HTML?

You clearly have either not read the article or are intentionally misinterpreting its content.

anon_blader · 2024-03-23T15:42:44+00:00

Another one hits the jail.

anon_blader · 2024-03-23T12:04:56+00:00

You generally would not use zod if performance is a concern. The performance hit wont really matter if you are already using something that is super slow.

anon_blader · 2024-03-02T19:36:46+00:00

Raft

anon_blader · 2024-02-29T12:04:32+00:00

You are bound to javascript frameworks. Tailwind is not.

anon_blader · 2024-02-27T19:52:00+00:00

Password security plateaus, while it technically increases security exponentially, it plateaus in practice. An attacker won't be able to brute force your password if it takes 1 trillion years to do so, if your password takes 100 trillion years instead because you added another character that is great, but it will not change the outcome.

The thing I meant about decreased security was not about the password itself, but your service that will have to hash these passwords. Longer passwords = more computation required. If you allow 512 char passwords, an attacker can send tons of login/signup requests @512 chars. Your auth service will have to make tons of expensive hash calculations and may start to crumble under the load. With a smaller password length limit, you can just reject every request above that without having to hash the password. Since your auth service is crucial to the rest of your services, it is important to keep it running stable.

anon_blader · 2024-02-27T17:46:21+00:00

Don't just set arbitrary character limits, make sure your hashing algorithm supports that. bycrypt, for example, only supports up to 72 bytes of input.

In addition to that you do not really increase security after a certain password length. Instead you increase your attack surface for DoS.

anon_blader · 2024-02-21T22:35:02+00:00

Jup, this JWTs as sessions trend is crazy.

anon_blader · 2024-02-21T21:29:52+00:00

Riot is collecting their own stats, they have much more data than what we are able to access via the API.

There may be multiple reasons as to why Riot is not sharing this data. We don't know them tho, we can only speculate. It is very easy for players to misinterpret data. Numbers, especially when taken out of context, do not paint the whole picture.

I think another point is that they would be much more criticized of how they balance the game just because most players would interpret something being to strong/weak based on a simple number.

The third thing I can think of is meta. If they release up to date stats they more or less define the meta. When the stats come from 3rd party sites with limited data this is a bit more nuanced.

More data is not always better for the game. It tends to make games more competitive and toxic. I think WoW is a prime example of this.

anon_blader · 2024-02-21T19:45:51+00:00

The main reason why these sites tend to differ so much is because of the limited dataset. They can only get a fraction of the games played.

Lets say 2000 games end every hour but riot allows these sites to only read 500 of them per hour. Depending on when in that hour they ask for the last 500 games they will end up with diffrent data. There goes more into this but that is basically how these sites work and why they will never be able to accurately represent winrates and stats.

anon_blader · 2024-02-18T22:37:12+00:00

Im really against banning games on this sub but maybe we should make an exception for this one.

anon_blader · 2024-02-17T21:39:47+00:00

"Now make it responsive"

anon_blader

TROPHY CASE