HN user

fresh_broccoli

264 karma
Posts2
Comments30
View on HN

the reporter should not be the one responsible for reporting separately to every single downstream of the thing they found a vuln in.

Not "separately to every single downstream", there is the "linux-distros" mailing list for disclosures: https://oss-security.openwall.org/wiki/mailing-lists/distros

This random blogpost from 2022 serves as a proof that disclosing kernel vulnerabilities to the distros list is a well-known practice: https://sam4k.com/a-dummys-guide-to-disclosing-linux-kernel-...

I agree it's a shame that the process isn't more streamlined and the kernel developers aren't forwarding the reports to the distros list.

Well, if Carmack wants to give gifts to AI companies then he's free to do it, but it doesn't mean that other people want it too.

I think this debate is mainly about the value of human labor. I guess when you're a millionaire, it's much easier to be excited about human labor losing value.

So many projects now walk on eggshells so as not to disrupt sponsor flow or employment prospects.

In my experience, open-source maintainers tend to be very agreeable, conflict-avoidant people. It has nothing to do with corporate interests. Well, not all of them, of course, we all know some very notable exceptions.

Unfortunately, some people see this welcoming attitude as an invite to be abusive.

To understand why it's happening, just read the downvoted comments siding with the slanderer, here and in the previous thread.

Some people feel they're entitled to being open-source contributors, entitled to maintainers' time. They don't understand why the maintainers aren't bending over backwards to accomodate them. They feel they're being unfairly gatekept out of open-source for no reason.

This sentiment existed before AI and it wasn't uncommon even here on Hacker News. Now these people have a tool that allows them to put in even less effort to cause even more headache for the maintainters.

I hope open-source survives this somehow.

As far as I know, there's still no real RISC-V equivalent to Raspberry Pi, and I think that's what early adopters want the most.

The closest thing is probably Orange Pi RV2, but it has an outdated SoC with no RVA23 support, meaning some Linux distros won't even run on it. Its performance is also much poorer than of the RPi5.

I find it worrying that this was upvoted so much so quickly, and HN users are apparently unable to spot the glaring red flags about this article.

1. Let's start with where the post was published. Check what kind of content this blog publishes - huge volumes of random low-effort AI-boosting posts with AI-generated images. This isn't a blog about history or linguistics.

2. The author is anonymous.

3. The contents of the post itself: it's just raw AI output. There's no expert commentary. It just mentions that unnamed experts were unable to do the job.

This isn't to say that LLMs aren't useful for science; on the contrary. See for example Terence Tao's blog. Notice how different his work is from whatever this post is.

Right, the website lists the accusations with links, but the links seem unrelated to the accusations.

For example, I'd expect "criticizing expert medical and scientific consensus on healthcare for our minors" to link to some kind of article describing what Jesse Singal said about this topic and why it's incorrect, but instead it links to a general page about "healthcare providers serving gender diverse youth" that doesn't even mention anything about the accused person or their writings.

But to my eyes, this PR does look like spam. It has no description, its title and commit messages are meaningless. Changing random auxiliary files is also a common sign of PR spam. This PR really looks no different from other spam PRs that popular GH repos have to deal with all the time.

This is not the right way to contribute to a project. If I were the maintainer, I wouldn't engage with it either, just like I don't reply to spam emails.

Kagi News 10 months ago

Also, they talk about "echo chambers" and "full spectrum of global perspectives". Representing all perspectives sounds great in theory, but how far should it go?

Should all politicians' remarks be reproduced verbatim with absolutely no commentary, no fact-checking and no context? Should an article about an airplane crossing the Pacific include "some experts believe that this is impossible because Earth is flat?"

Excessive bias in media is definitely a problem, but I don't think that completely unbiased media can exist while still being useful. In my expierence, people looking for it either haven't thought about it deeply enough, or they just want information that doesn't make their side look bad.

Kagi News 10 months ago

I think this is the wrong direction. We need better journalism, not better summarizing aggregators.

Summaries are no substitute for real articles, even if they're generated by hand (and these apparently are not). Summaries are bound to strip the information of context, important details and analysis. There's also no accountability for the contents.

Sure, there are links to the actual articles, but let's not kid ourselves that most people are going to read them. Why would they need a summarizing service otherwise? Especially if there are 20 sources of varying quality.

There are no "lifehacks" to getting informed. I'll be harsh: this service strikes me as informationally illiterate person's idea of what getting informed is like.

It's very annoying that Google's websites, including this blog, are automatically translated to my browser's preferred language.

Sillicon Valley devs clearly believe that machine translation is a magical technology that completely solved internationalization, like in Star Trek. No, it's far from it. Ever since internet has been flooded with automatically translated garbage, the experience of international users, at least bilingual ones, got much worse.

The slow adoption of QUIC is the result of OpenSSL's refusal to expose the primitives needed by QUIC implementations that already existed in the wild. Instead, they decided to build their own NIH QUIC stack, which after all these years is still not complete.

Fortunately, this recently changed and OpenSSL 3.5 will finally provide an API for third party QUIC stacks.[1] It works differently than all the other existing implementations, as it's push-based instead of pull-based. It remains to be seen what it means for the ecosystem.

[1] https://github.com/openssl/openssl/pull/26683

So apparently this is one person's project, but the branding makes it seem like it's some kind of official European Union initiative.

Also, I don't see what problem a national Linux distribution would solve. It would either duplicate the effort of a "normal" Linux distribution, or more likely, it would be just a rebrand of an existing distro.

1) memory safety at compiler level

Ada isn't memory safe. It doesn't have anything resembling a borrow checker. The spec used to allow an optional garbage collector, but that was never widely used in practice and was removed in Ada 2012. The average production codebase relies on Unchecked_Free/Unchecked_Deallocation for memory management.

I find it genuinely baffling that so many people who praise Ada clearly don't know and/or don't use the language.

I had a Ryzen 1700 that didn't meet the windows 11 tpm standard.

It's not TPM, Zen1 does support TPM 2. Also, its instruction set is identical to Zen+ (Ryzen 2xxx), which is supported by Win11. After all, Zen+ was just a die shrink of Zen1 with some minor fixes.

It really seems like they blacklisted Zen1 for no real reason.

I wasn't a very active 4chan poster to begin with, but when they introduced this awful CAPTCHA, and later the 300s countdown before making the first post, I completely lost interest in using the website.

Anonymous boards were supposed to be low-friction, but now 4chan is one of the most user-hostile social media platforms around. It takes a special kind of dedication to post there, which I seriously doubt helps the quality of the site.

It's a shame that MikroTik routers' UI is completely unsuitable for non-powerusers.

Otherwise they would be perfect. Cheap and supported practically forever. Their trick seems to be that they use a single firmware image for all routers with the same CPU architecture.