HN user

obpe

234 karma
Posts0
Comments59
View on HN
No posts found.

It seems the entire premise is that Social Media is what is actually bad for us but going to office would help people be more tolerant... I don't think so. The vast majority of people do not work from home remotely. And the intolerance in our society was well established before remote work was common during the pandemic.

I personally really dislike when someone proclaims how society should be from the own personal anecdote.

I think the real problem is rich people thinking that their lives are "amazing" and can not understand, because their livelihood depends on it, why some one could possibly have a different opinion about their own life. What do you mean you can't afford rent, planes have Wifi now! You haven't got a meaningful raise in 5 years, but ChatGPT 5 was released, it's a step improvement in functionality! Not a single thing that is amazing impacts me nor has improved my life. But I guess rich people flying around can stream Netflix, we truly are living in a Utopia.

I don't think that is the case. According to pre-election polling more than 50% of voters said the economy was their biggest concern and only 25% said immigration. And the Democrats were largely touting the status quo which cleary people do not want.

I think China would fit this description the best. It seems like they DGAF about what you say as long as you don't criticize the leader and government or create "social unrest" which practically means telling other people to criticize the leader or government.

I think every country has some forms of censorship. In many countries it is illegal to speak negatively or make jokes at the expense of the Crown or government. In many countries it is illegal to speak against the state religion. In the EU it is now illegal to NOT moderate your platform in the way the government demands. The US probably has the highest legal protection for free speech but companies in the US are far more likely to bend to public opinion.

Pick your poison.

The key isn't fetched and never leaves the enclave. The enclave does the crypto functions.

Passkeys are meant to replace passwords for the average user. And they definitely succeed at that.

It would really depend on where you are trying to incorporate. My understanding is this is possible but you will need to pay a lawyer to do all the legal work for you and sign their name on the documents. I doubt this would interfere with most governments finding out who you are unless you are using multiple companies registered in different countries.

If the goal of a project was to, "use a type safe language" then it can only be successful if you use a type safe language.

If the goal of a project is to, "create a crud app for your 5 coworkers" then it really doesn't matter whether you use SQL or not.

If the goal of a project is to, "server 100 billion requests per second" then maybe you should consider microservices in a monorepo (those things are not mutually exclusive).

Success, or not, only matters in the context in which you have defined success.

Htmx Is the Future 3 years ago

I see, I have never implemented those types of validations. We do religiously deploy the same validation on client and server to explicitly avoid the mismatch of client/server validation. Having the client submit "valid" input only to have server reject it is something we have run into. Having only client side validation is something I have never run into.

Also, in my opinion things like you suggest you shouldn't do. A password strength metre is only going to give attackers hints at the passwords you have in your system. And I have not see a caps lock on warning in forever. The only password validation we do is the length which is pretty easy to validate on client and server.

Htmx Is the Future 3 years ago

I have never heard this before. Can you elaborate on the differences? What do you validate on the client side that you don't on the server and vice versa?

Htmx Is the Future 3 years ago

Node does not absolve from this. Any important verification still needs to be done on the server side, since any JS on the client side cannot be trusted to not be manipulated. JS on the client side was of course possible before NodeJS. NodeJS did not add anything there regarding where one must verify inputs. Relying on things being checked in the frontend/client-side is just writing insecure websites/apps.

Yeah, that was my point. With Node you can write JS to validate on both the client and server. In the article, they suggest you can just do a server request whenever you need to validate user input.

Basically most of any progress in bandwidth or ressources is eaten by more bloat.

In my experience, the bloat comes from Analytics and binary data (image/video) not functional code for the SPA. Unfortunately, the business keeps claiming it's "important" to them to have analytics... I don't see it but they pay my salary.