talkin

8 ms·

1.
by talkin 17d ago
> Criminals don't just rob random houses False, opportunity theft is the most common form. Better doors/windows/locks help the most, and help against both opportunistic and targeted.
2.
by talkin 2mo ago
I didn’t see it for decades, only realized waaay too long into a Dutch movie: https://www.imdb.com/title/tt3765078/ (Publieke Werken). I cannot imagine how I was ever able to not see it immediately..
3.
by talkin 3mo ago
It costs tokens, so it helps the business model, so it’s not a bug but a feature.
4.
by talkin 4mo ago
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)
5.
by talkin 4mo ago
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.
6.
by talkin 6mo ago
> 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 wor
7.
by talkin 6mo ago
> cd -: The classic channel-flipper. Perfect for toggling back and forth. And not only cd. Gotta love 'git checkout -'
8.
by talkin 6mo ago
There will always be early adopters. And maybe more importantly: security tools and researchers.
9.
by talkin 6mo ago
Or even an autoincrement int primary key internally. Depending on your scale and env etc, but still fits enough use cases.
10.
by talkin 7mo ago
Most regex usage actually doesnt require near infinite backtracking, so limited unless opted in wouldn’t be that weird.
11.
by talkin 8mo ago
“Intuitive!”
12.
by talkin 9mo ago
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 haunte
13.
by talkin 1y ago
No. The Regex DoS class of bugs is about infinite backtracking or looping inside the regex engine. Completely isolated component, just hogging CPU inside the regex engine. It may also have ‘DoS’ in its name, but there’s no relation to netwo
14.
by talkin 1y ago
Backup/restore tends too look less important until it isn’t. ;)
15.
by talkin 1y ago
Interferes with the business model. ;)
16.
by talkin 2y ago
> Well, I don't think most folks could name a CEO of another car company. Yup, and I don’t care. I liked the brand better without the drama queen.
17.
by talkin 2y ago
Spreading the message inside FB helps the mission. The people who already stopped don’t need to be convinced anymore. ;) But sure, ironic and counterintuitive.
18.
by talkin 2y ago
Nobody said you shouldn’t do any due diligence. But 1 sprint vs 2 months of review really smells like ‘processes over people’. ;)
19.
by talkin 2y ago
All true, but lets be honest: For the technical users searching a library, nothing beats having The Keyword being part of the name.
20.
by talkin 2y ago
Yes. Just like the Log4j issue root cause. Too powerful and abstract features to wield securely. Or maybe if we keep intent out of it; features were added in a time when we all worried less about security and internet implications. I would
21.
by talkin 2y ago
This comment and all siblings fight over PHP vs Pyhton etc, but that just isn’t the bottleneck in most apps. By far, for most apps, the biggest bottleneck is the database.
22.
by talkin 2y ago
To be specific about static analysis: Lots of tools catch this. Sure, making some checks native would be nice, but for instance PHPStan always catches this, and more. Regardless of the ‘improve the language angle’: Is somebody isn’t running
23.
by talkin 2y ago
You’re technically right but that doesn’t matter. That you’re correctly using html forms won’t quickly lead to browser improvements.. so the result is that users will hate your forms. Users/your customer might possibly even think that
24.
by talkin 2y ago
> I think it's the autocomplete in particular that leaks a lot of private data. That’s the beauty. The whole unified input can be presented as a UX simplicity gain, while this quote points at the actual business value. ;)
25.
by talkin 2y ago
And 2 problems jn the fix: - It’s a specific symptom fix: The same problem could occur with $_COOKIE or $_REQUEST always being available - The cleanup is not done in a finally{}, so random missing vars when an exception occurs. Exec summary
26.
by talkin 2y ago
Thanks for the clear words. :) But that still means both can go hand in hand! If user targeted ads and tracking is forbidden and a thing from the past, there’ll be less problems with having some proper statistical attribution. Hint: I’m fro
27.
by talkin 2y ago
All posts like these, and all comments here up till now just don’t mention the Real Solution: Allow ads, forbid user targeted ads. If a site can not exist based on that instead of the current ads ‘needing 1337 partners’, tough luck. Also: m
28.
by talkin 2y ago
Well, or it is important, and then you add the countermeasures. These countermeasures are quite easy to mess up, so doing the validation (on an ongoing basis!) MUST be part of the deal. Or if you think it’s not important enough to do those
29.
by talkin 2y ago
With such a small group, chances are they all figured out that a race to the bottom won’t reach the desired long term outcome.
30.
by talkin 2y ago
Legal: “it’s forbidden to target ads at specific users” Done.

More ›