News for hackers. Stuff that matters.

detaro

Re:Georgia police officers fired after Flock camera misuse on Sunday August 09, 2026 @09:51PM (#49238359)
even if you purely want to frame it is that: is helping to convince large parts of the public that cops are above the law and can't be trusted by covering for the bad apples "looking out for their members"?
> (which slipped through testing)

In another comment you say you caught it in testing and didn't think it needed fixing, which is it?

and 87k is quite a bit below 125k.
Re:CDC Pauses Testing for Rabies and Pox Viruses on Thursday April 02, 2026 @11:10PM (#47622819)
https://archive.is/3oQn9

> But widespread layoffs, hiring freezes and resignations have shrunk the number of qualified scientists who can assist state labs. The C.D.C.’s rabies and pox virus teams have lost many of their members. By July, the rabies team will be down to just one person with the clinical expertise to advise state and local officials, and the pox virus team will have none.

That the "good enough" SoCs will be arriving "over the next 2 years" is what the RISC-V advocates have told us for quite a few years now.
Again, how should the UK use the Navy here?
deploy and do what exactly? Get involved and potentially sacrifice a few UK soldiers to stroke Trumps ego? Sit around and look pretty? Having a carrier there doesn't magically make problems go away.
Re:Malus – Clean Room as a Service on Thursday March 12, 2026 @02:21PM (#47355058)
whoosh
Re:Zed new terms required to be 18 years old on Thursday March 05, 2026 @02:24AM (#47258649)
where?
Re:/e/OS is a complete "deGoogled", mobile ecosystem on Monday March 02, 2026 @06:19AM (#47216514)
How is it "bizarre" when it even tells you why it needs a Chromium-based browser?
It's a very common abbreviation for that
Re:Helldivers 2 devs slash install size from 154GB to 23GB on Wednesday December 03, 2025 @10:56AM (#46135964)
The CDN/content provider ships servers to the ISP which puts them into their network. The provider is just providing connectivity and not involved on a content-level, so no MITM etc needed.
Re:AI slop security engineering: Okta's NextJS-0auth troubles on Thursday November 20, 2025 @02:23PM (#45996555)
Why is it confusing to you to expect attribution?
I don't know the exact threshold the software uses, but my impression is that the mods use something in the ballpark of <20 points and <5 comments?
6 upvotes and no comments isn't enough attention to trigger dupe direction.
Re:Zig is so cool, C is cooler on Saturday November 08, 2025 @01:40PM (#45858879)
It clearly wasn't "refined" using LLMs when it contained commands that plainly don't work. Don't lie.
Not wrong, but that comes with promoting yourself on ideology grounds. If you want support because you are the plucky underdog community project that cares about people and are running ad campaigns how you are not evil big tech, then don't be surprised if people hold you to it. Mozilla is in this weird space where it wants to be both the good little guys and a proper Silicon Valley tech company, and those don't necessarily mix well.
How did you read the post and miss the complaint?
It's a community matter posted in a public place, a non-statement with an immediate attempt to direct it to private conversation reads like trying to avoid attention to your mistakes (e.g. hypothetically you don't have to public admit you didn't do anything to check for guidelines to follow). More vibe-y, it all sounds very corporate, like any PR statement in response to criticism ever, not "humans working together in a community".

Also while it's phrased as a question, it doesn't offer any alternative next step. So a better approach would be writing down the initial questions you have and then offer that you'd be open for a call if the OP prefers that. If they don't, they can immediately engage with your questions, and they are open to everybody else in the community. Whereas right now if they say "no, I don't want to call you" that's all you've given them.

Or answer being clear about that if you feel like you need to respond now. Acknowledge there is a problem, say you'll have to look into the details before you can say more, come back with specific questions if you need answers.
If the post gave any acknowledgement to the already stated complaints I'd agree with you, but it does not, and that does stand out and leads to my reading.
Then say so if someone complains about it? "Shoot, we accidentally ran it in the wrong mode, sorry about that, I'll look into someone fixing it ASAP" is a lot better than "We're sorry for how you feel".
Then at least try to sound like a genuine human that cares and not a PR response when reaching out. Offer a "you can call me if you want" vs making the call the expectation (it's phrased as a question but there is no other path offered).
a) don't apologize for the other persons feelings, but for your actions that lead to it

b) don't look like you are trying to take the conversation out of the community space it's happening in and/or hiding details by going to a private call (you can offer a call, but it shouldn't be the expectation)

c) Acknowledge the concrete complaints made. Are you truly "struggling to understand" what someone means when they complain that it didn't happen in a staging environment first?

d) a-c also lead to "don't sound like any cookie-cutter PR response to a complaint ever, people have learned those are not genuine". Especially if you are a project that makes a big deal out of its community interacting with said community.

e) ideally announce some concrete first step, e.g. pausing the bot

Older »