talkin

no profile record

·21 日前·議論

It costs tokens, so it helps the business model, so it’s not a bug but a feature.

·先月·議論

It’s also a weird argument. You can only spend your money once, and the affected employees also chose to work for a bell-end like Altman (or Zuck, or Musk)

talkin

·2 か月前·議論

Fixing easy cases makes the list shorter, so enables more focus on harder cases.

And it also signals that you actually do want to improve, just a little bit of boy scout rule goes a long way.

talkin

·4 か月前·議論

> for some reason the industry stubbornly refuses to solve the "cron job as a service" problem for end-users, whether on the web or in the OS.

Such a service will always be destroyed by the bell-ends who want to run spam or worse activities.

talkin

·4 か月前·議論

> cd -: The classic channel-flipper. Perfect for toggling back and forth.

And not only cd. Gotta love 'git checkout -'

talkin

·4 か月前·議論

There will always be early adopters.

And maybe more importantly: security tools and researchers.

talkin

·4 か月前·議論

Or even an autoincrement int primary key internally. Depending on your scale and env etc, but still fits enough use cases.

talkin

·5 か月前·議論

Most regex usage actually doesnt require near infinite backtracking, so limited unless opted in wouldn’t be that weird.

talkin

·6 か月前·議論

“Intuitive!”

talkin

·7 か月前·議論

NO. Please don’t spread wrong solutions.

Your attempt has similarities to the idea behind Checking Sec-Fetch-Site. Implementing that header is the same amount of work. But this header is exactly meant for this purpose, and referer is haunted with problems.

So for officially intended protections, implementing this header and samesite cookies gets you a very long way without any complexity, assumptions, or tricks of old lore.

コメント