Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
haskellshill
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
haskellshill
11mo ago
Right, they probably already mitigated this bug in their own usage. Which is exactly why reporting the bug is a FAVOR to ffmpeg. Would you rather they just quietly fix it on their own and not report it to the maintainers?
2.
▲
by
haskellshill
11mo ago
> you have 90 days to fix it Or else what? They release the report? That's standard and ffmpeg is open source anyway, anybody can find the bug on their own. There's no threat here. If you're mad about companies using your
3.
▲
by
haskellshill
11mo ago
What does it matter if it's AI generated if it's a real bug? The problem with AI reports is usually that they're invalid; in this case it was an actual bug. > currently have zero real-world impact So better we not talk abo
4.
▲
by
haskellshill
11mo ago
There's no law that you have to fix all bug reports. Isn't it better for users and developers alike that they can see the problems of the project. If they don't have resources that's fine, it's not like they are cha
5.
▲
by
haskellshill
11mo ago
Google found a vulnerability and reported it for free. Why do they need to do anything more? Give and inch and ffmpeg's twitter guy requests a mile. If you don't want people to use your software to make money, release it with a li
6.
▲
by
haskellshill
11mo ago
>rarely anyone ever uses It's enabled by default so all that's required to exploit it would be to construct a payload file and name it movie.mp4
7.
▲
by
haskellshill
11mo ago
Yeah, it's actually a great bug report. Reproducible and guaranteed to be an actual problem (regardless of how small the problem is considered by the devs). Just seems irresponsible to encourage people not to file bug reports if it
8.
▲
by
haskellshill
11mo ago
VLC is pretty popular on windows, but ffmpeg? Is there any commonly used windows app that relies on it? I doubt it'd be worth one's time to write exploits for desktop linux
9.
▲
by
haskellshill
11mo ago
Yeah, I mean if it's an actual vulnerability what are they complaining for?
10.
▲
by
haskellshill
11mo ago
No :)
11.
▲
by
haskellshill
11mo ago
Again, you're focusing on a pointless detail. Sure, I made a mistake in offhandedly using li as an example. Why do you choose to ignore the actually valid p example though? Seems like you're more interested in demonstrating your k
12.
▲
by
haskellshill
11mo ago
That's exactly my point, people are clueless about the basics of nuclear power. Why would they know it? I mean, why would the average person know what a linear equation is or what year the first world war started?
13.
▲
by
haskellshill
11mo ago
> If there's a bit of water in your lungs, a surprisingly small amount , it causes massive inflammation and your lungs start to fill with fluid. It's called "secondary drowning" , and it happens a couple of hours
14.
▲
by
haskellshill
11mo ago
Well, just because something is allowed by the syntax does not mean it's a good idea, that's why pretty much every language has linters. And I do think there's an evenly applied rule, namely: always explicitly close all non-v
15.
▲
by
haskellshill
11mo ago
Are you misunderstanding on purpose? I am aware they are optional. I am arguing that there is no reason to omit them from your HTML. Whitespace is (mostly) optional in C, does that mean it's a good idea to omit it from your programs? O
16.
▲
by
haskellshill
11mo ago
The merits and drawbacks of XHTML has already been discussed elsewhere in the thread and I am well aware of it. > And at a time when there was legitimate browser competition, the one that made a "best effort" to render invalid
17.
▲
by
haskellshill
11mo ago
As the saying goes, "a little bit of knowledge is a dangerous thing". Your "water rescue course" taught you something that's clearly wrong, as we see with the sibling comment, while my common sense and just everyday
18.
▲
by
haskellshill
11mo ago
It's an analogy, there's no need to analyze it literally. And no, I've worked with some devs who don't understand git (thankfully I don't anymore) and it was quite a bit more than "five times" they got stu
19.
▲
by
haskellshill
11mo ago
"Intimately understand the VM" is not the same as knowing what data structure you're using. It'd be comparable to not knowing the difference between an array and a linked list. Sure you may call it gatekeeping but likewi
20.
▲
by
haskellshill
11mo ago
I didn't expect this level of unfounded ignorant hysteria here. Have you really never gone swimming and inhaled some water? Did you go to the hospital? > In the past, these terms were used to try to explain that some fatal drowning
21.
▲
by
haskellshill
11mo ago
It had too much unnecessary metadata yes, but case insensitivity is always the wrong way to do stuff in programming (e.g. case insensitive file system paths). The only reason you'd want it is for real-world stuff like person names and
22.
▲
by
haskellshill
11mo ago
> They introduce zero ambiguity to the language Well, to parsing it for machines yes, but for humans writing and reading it they are helpful. For example, if you have <p> foo <p> bar and change it to <di
23.
▲
by
haskellshill
11mo ago
Reall? Libreoffice at least has a File > Open menu that allows you to specify the separator and other CSV stuff, like the quote character
24.
▲
by
haskellshill
11mo ago
> People can drown on dry land from about a tablespoon of water getting into their lungs. Well, I don't think there's such a big risk of that. Falling into a pool is something most of us have probably done. Being pushed by a fr
25.
▲
by
haskellshill
11mo ago
I mean, if you actually think there's a pool of "lava" that's dangerously radioactive at the surface, while people are walking right next to it, you might be a bit "stoopid". The whole reason water is used is t
26.
▲
by
haskellshill
11mo ago
"Expert level knowledge" implies something more to me than simply few people knowing about it. It's ridiculous to say that knowing how to change gears makes you an expert driver, even if a minority know how to do it (such as
27.
▲
by
haskellshill
11mo ago
> all the experts you know use it in slightly different ways What? Knowing that a git repo is just a folder is nowhere near "expert" level. That's basic knowledge, just like knowing that the commits are nodes of a DAG. Sad
28.
▲
by
haskellshill
11mo ago
Wow, people are really clueless about how nuclear power plants really work. It's really not that dangerous to fall into the water.
29.
▲
by
haskellshill
11mo ago
You're arguing in circles. They don't "try to figure out reasons" because there is no concept of "trying", "figuring out" or "reasons". > If that's not thinking, then I don't kn
30.
▲
by
haskellshill
11mo ago
This is a silly definition of learning, and any way, LLMs can't even do what you describe.
More ›