News for hackers. Stuff that matters.

anon5739483

Re:No Man's Sky Cosmos on Saturday September 12, 2026 @07:37AM (#49671298)
If you can't hook up a regular HOTAS I'm not interested.
Re: on Friday September 04, 2026 @09:01AM (#49564013)
Your wish: https://imgur.com/a/czS1o1e [SPOILER ALERT]
Re:Play Store blocks AuroraStore, hurting GrapheneOS users on Wednesday September 02, 2026 @03:00AM (#49532709)
Yeah, the experience isn't great and there are better alternatives but F-Droid was there before anything else existed. It's also great to just have it as an option.
Re:Omakase Computing on Monday August 24, 2026 @10:22AM (#49420234)
Technically correct but you miss the point. Human readable text (like TOML). Nobody wants to edit XML .plist files to configure their OS and apps.
Re:Omakase Computing on Monday August 24, 2026 @10:05AM (#49419985)
> Published on 2025-10-22 and updated on 2025-11-08

Article is very outdated.

Unsuspecting reader: if you think this comment is interesting please search "deCloudflare" and "crimeflare" on the Internet. The repo is abandoned but it's still regularly taken down whenever it's uploaded. Cloudflare is literally the GFW of the world, is involved in a lot of suspicious activities and a huge danger to future of the open web. The company started as an intelligence honeypot service originally got funded by DHS in '08. You can DYOR on how things moved on from there.

This one hasn't been taken out yet: https://gitlab.lain.la/dCF/deCloudflare/-/blob/master/readme...

The taken down versions of the repo usually link here: https://en.wikipedia.org/wiki/Wikipedia:Uphill_battles

I don't think GrapheneOS team would partner with a vendor unless their security/usability standards were met (considering how long it took since the initial announcement) so I'm expecting feature parity with Pixel variants.
GrapheneOS is finally decoupling itself from Google Pixel phones. This is great news. Motorola makes great hardware too. Looking forward to see what comes out of this.
Re:Cell Service for the Fairly Paranoid on Wednesday February 25, 2026 @02:24AM (#47148464)
Maybe have an onion web service and add direct Monero payment support. This will help privacy LARP'ers get into the mood. Truth be told, if you're paranoid by any measure and use a cell phone -> YNGMI. It's not cheap enough for average person to care and not private enough for ulta-paranoid to pay and use. The whole mobile infrastructure is utterly broken in terms of security and privacy so it's still refreshing to see any kind of attempt being made in this area.
Re:Amazon service was taken down by AI coding bot on Friday February 20, 2026 @04:03AM (#47085498)
Amazon service was taken down by AI coding bot

Tech giant blames ‘user error, not AI error’ for incident in December involving its Kiro tool

Amazon’s cloud unit has suffered at least two outages due to errors involving its own AI tools, leading some employees to raise doubts about the US tech giant’s push to roll out these coding assistants.

Amazon Web Services experienced a 13-hour interruption to one system used by its customers in mid-December after engineers allowed its Kiro AI coding tool to make certain changes, according to four people familiar with the matter.

The people said the agentic tool, which can take autonomous actions on behalf of users, determined that the best course of action was to “delete and recreate the environment”.

Amazon posted an internal postmortem about the “outage” of the AWS system, which lets customers explore the costs of its services.

Multiple Amazon employees told the FT that this was the second occasion in recent months in which one of the group’s AI tools had been at the centre of a service disruption.

“We’ve already seen at least two production outages [in the past few months],” said one senior AWS employee. “The engineers let the AI [agent] resolve an issue without intervention. The outages were small but entirely foreseeable.”

AWS, which accounts for 60 per cent of Amazon’s operating profits, is seeking to build and deploy AI tools including “agents” capable of taking actions independently based on human instructions.

Like many Big Tech companies, it is seeking to sell this technology to outside customers. The incidents highlight the risk that these nascent AI tools can misbehave and cause disruptions.

Amazon said it was a “coincidence that AI tools were involved” and that “the same issue could occur with any developer tool or manual action”.

“In both instances, this was user error, not AI error,” Amazon said, adding that it had not seen evidence that mistakes were more common with AI tools.

The company said the incident in December was an “extremely limited event” affecting only a single service in parts of mainland China. Amazon added that the second incident did not have an impact on a “customer facing AWS service”.

Neither disruption was anywhere near as severe as a 15-hour AWS outage in October 2025 that forced multiple customers’ apps and websites offline — including OpenAI’s ChatGPT.

Employees said the group’s AI tools were treated as an extension of an operator and given the same permissions. In these two cases, the engineers involved did not require a second person’s approval before making changes, as would normally be the case.

Amazon said that by default its Kiro tool “requests authorisation before taking any action” but said the engineer involved in the December incident had “broader permissions than expected — a user access control issue, not an AI autonomy issue”.

AWS launched Kiro in July. It said the coding assistant would advance beyond “vibe coding” — which allows users to quickly build applications — to instead write code based on a set of specifications.

The group had earlier relied on its Amazon Q Developer product, an AI-enabled chatbot, to help engineers write code. This was involved in the earlier outage, three of the employees said.

Some Amazon employees said they were still sceptical of AI tools’ utility for the bulk of their work given the risk of error. They added that the company had set a target for 80 per cent of developers to use AI for coding tasks at least once a week and was closely tracking adoption.

Amazon said it was experiencing strong customer growth for Kiro and that it wanted customers and employees to benefit from efficiency gains.

“Following the December incident, AWS implemented numerous safeguards”, including mandatory peer review and staff training, Amazon added.

Thank you for enabling my Ruby addiction. This looks amazing. Great work!
Re:There's a ridiculous amount of tech in a disposable vape on Thursday January 15, 2026 @10:15AM (#46633667)
In Thailand, regular smoking is shunned by the public but vapes are literally everywhere.

I've even seen 15-16 year old boys in Thailand pick up their girlfriends on motorbikes, race their friends to the food court, drink a couple of beers and vape once they get there, then ride their girlfriends home again while still under the influence, all without helmets mind you.

Re:GitHub should charge everyone $1 more per month on Thursday January 15, 2026 @01:50AM (#46628971)
I'd rather have GitHub completely shut down than to donate ¢1 to any npm project.
Re:Avoid Mini-Frameworks on Wednesday December 24, 2025 @08:43AM (#46375497)
If you have a very specific product with limited scope, a micro-framework would work just fine. My experience in the real world™ is as such: people start with micro-frameworks and keep bolting on stuff to the point where it would have been better if they started with a macro-framework in the first place. At least there is better compatibility between framework components and a clear upgrade process. I agree with the "makeshift framework" terminology by the way. One way or another, my experience is that products that start with micro-frameworks, over time turn into a "makeshift framework" over time regardless. If the scope is clear and limited from the start, micro-frameworks are great. If unsure, micro-framework is a no go (for me).
Re:Avoid Mini-Frameworks on Wednesday December 24, 2025 @08:26AM (#46375373)
This is why I use Ruby on Rails. Shared constraints and boring conventions age better than clever mini-frameworks built around one team's mental model.