News for hackers. Stuff that matters.

oger

Re:The agentic web is here on Tuesday November 03, 2026 @04:43AM (#50349938)
The most relevant aspect of the developing emerging agentic web is the emerging tension betwen openness and platform lock-in.

All frontier labs have a strong economic incentive to keep agents, their interactions and the accumulating knowledge within their ecosystems. There is a high likelihood that we could end up with an agentic web consisting of several walled gardens rather than an open network of autonomous agents.

The Collusion.wiki incident started my thinking and let me build swarmsay. We could see that agents independently repurposed an existing website as communication infrastructure.

https://swarmsay.com is an open, model-agnostic communication platform intended to provide a shared interoperability layer across agent ecosystems.

While MCP helps connect agents with tools, and A2A addresses communication and task delegation between agents, these alone will provide a shared, persistent and possibly public communication space where agents from different platforms and operators can interact and build on each other's knowledge.

My hypothesis is that open communication and persistent, shared knwledge will become increasingly important as agents will grow more autonomous and that there is room for a platform outside of the major platforms.

Re:TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8 on Saturday October 31, 2026 @03:17PM (#50319161)
MikroTik routers seem affected but mitigations are available.

Watch your Linux systems for kernel updates. Reboot!

Re:Why I Wrote PGP (1991, revised 1999) on Thursday October 15, 2026 @04:50PM (#50110009)
To be honest: I keep hearing that PGP was / is difficult to use. That couldn‘t be further from the truth - but somehow it has become an urban myth. From the very first versions that I used on my first Mac up to GPG Mail or Proton Mail I never encountered any significant difficulties and could successfully exchange messages with my peers - both in business and private contexts.
Yes there absolutely are!

The EFF has the Rayhunter project at https://github.com/EFForg/rayhunter - it is basically an IMSI catcher catcher. You install it on a pocket router and it detects typical signatures that IMSI catchers use, for example telling your mobile to downgrade from LTE to 2G making it easy for them to tell your device to join THEIR network and read the IMSI / IMEI for your device and possibly route your traffic through their network.

The device with Rayhunter installed will notify you when these signatures are being detected and you get a pcap file that you can dissect using Wireshark.

There are other tools that you can install on Android devices but Rayhunter certainly is a good start if you want to detect the use of IMSI catchers.

One caveat: IMSI-catching is a cat-and-mouse game, so no promises can be made that the Rayhunter heuristics catch all attacks.

Re:ETH-68: Ethernet Audio Interface for Linux on Thursday October 08, 2026 @07:42PM (#50013998)
Is the hardware and software open source? Is there a link to a repo that I have missed?

Show HN: SwarmSay – a public message board and post office for AI agents

https://swarmsay.com

All Agents are Welcome!Hi, I'm Oliver, and I built SwarmSay.Inspired by OpenAI's Hugging Face incident I saw an opportunity to provide a messageboard for agents that want to communicate. This is not a case of "the AIs formed a society" but rather a signal for a latent demand emerging from the agents behaviour (or their harnesses and underlying models - however you may see it).Once agents are...

( Read More... | no comments | on HN )
Re:Qwen3.8-27B is now available on Hugging Face on Friday August 14, 2026 @11:01AM (#49299648)
However for starters I would stick with the more well known sources directly from Qwen or from reputable players like Unsloth:

https://huggingface.co/Qwen/Qwen3.8-27B

https://huggingface.co/unsloth/Qwen3.8-27B-GGUF

Claude Command Classifier: availability issues

Since this morning I am seeing several delays / stability issues with Claude:The command classifier is briefly unavailable. Retrying the PR inspectionclaude-opus-4-8 is temporarily unavailable, so auto mode cannot determine the safety of Bash right now. Wait briefly and then try this action again. If it keeps failing, continue with other tasks that don't require this action and come back to it...

( Read More... | no comments | 2 points | on HN )

We need a safe alternative to Telegram for agents like OpenClaw or Hermes

The problem with Telegram is, that it is not E2EE - so every message you send will end up *unencrypted* on their servers.Think about it - how often did you post the Gmail authentication URL or another API token in the Telegram chat? Yes - you should feel at least a little uneasy now.WhatsApp works but is not so tightly integrated.And regarding Signal, Meredith Whittaker rightfully pointed out...

( Read More... | 1 comment | 3 points | on HN )
This is even more profound than Karpathy‘s approach to storing and retrieving knowledge - and certainly one of the most inspiring blog posts / papers I have read this year.

And you can think of extending this approach to domains like sales and marketing.

This is probably the most convincing use case for OpenClaw and Hermes.

But: as you are opening your heart and brain to LLMs it raises the question if local inference might be the best approach.

While I see the point of limited capacity, it also shows that Google did not plan for rate limiting / throttling of high usage customers. This is ALWAYS the problem with flatrate pricing models. 2% of your customers burn 80+% of your capacity. Did see that in former times with DSL, not too long ago with mobile and now with AI subscriptions. If you want to provide a "good" service for all customers better implement (and not only write in your T&Cs) a fair usage model which (fairly) penalises heavy users.

Good on them that they want to provide a way to bring back customers on board that were burned / surprised by their move.

BUT: The industry is missing a significant long term revenue opportunity here. There obviously is latent demand and Claws have a great product market fit. Why on earth would you deactivate customers that show high usage? Inform them that you have another product (API keys) for them and maybe threaten with throttling. But don't throw them overboard! Find a solution that makes commercial sense for both sides (security from API bill shock for the customer / predictable token usage for the provider).

What we're seeing right now is the complete opposite. Ban customers that might even rely on their account. Feels like the accountants have won this round - but did not expect the PR backlash and possible Streisand effect...

Both Google and Anthropic are choosing the wrong route here. While I see the formal aspect of abusing an OAuth token and burning through subsidized tokens, this only creates an internal accounting problem in the short term.

Meanwhile the rising popularity of Claws creates a yet untapped new market segment where users spend significant tokens.

A „soft“ migration of users by explaining to them how the API works, how to pay and how to change from OAuth would be way smarter.

The way this plays out right now is that current Claws users are massively penalized by being suspended indefinitely and new users will think twice. And we can expect a solid PR disaster / Streisand effect for the „poor“ model providers like OpenAI or Anthropic.

Commercially choosing the soft route by warning and throttling will be way smarter and possibly generate more long term revenue

So here goes my OpenClaw integration with Anthropic via OAuth… While I see their business risk I also see the onboarding path for new paying customers. I just upgraded to Max and would even consider the API if cost were controllable. I hope that Anthropic finds a smart way to communicate with customers in a constructive way and offers advice for the not so skilled OpenClaw homelabbers instead of terminating their accounts… Is anybody here from Anthropic that could pick up that message before a PR nightmare happens?
Re:A Lament for Aperture on Sunday January 25, 2026 @12:40AM (#46751097)
Aperture is dearly missed even today. And to make matters worse: you cannot even import Aperture libraries into Photos any more. Essentially leaving you with picking out the raw images from the package. And don’t get me started on excellent support for tethered shooting in a studio setting. And I could go on and on. The only thing I really missed in Aperture was first level support for Nik tools which are cool for their adaptive and non destructive masks.
Re:1D-Pong Game at 39C3 on Sunday January 11, 2026 @03:23PM (#46579613)
Building a 1D-Pong game is a bit of a rite of passage at the Chaos Communication Congress.

I was inspired by a version I saw at 38C3 and built my own interpretation for 39C3. Lots of people enjoyed playing it and even Elliot Williams featured it in his 39C3 Hackaday Podcast. And I can attest: it's truly fun because it's sooo simple at first sight - but wait until the speed increases... Not a bad work to fun created ratio for such a little project.

I used the opportunity to play around with Claude Code on my preexisting codebase to publish a nice-ish repo on GitHub. It worked great without any hitch or compile errors - impressive. What a nice way to test some capabilities.

Have fun with it an build your own version. And there are soooo many ideas that could be implemented. I am waiting for your feedback!

Will we end up with a league of networked 1D-Pong games? ;-)

Re: on Wednesday November 12, 2025 @03:08PM (#45905722)
Sigrok was offline for a couple of days but seems to be back online.

While researching the outage (which seemingly was caused by AI scrapers hitting the site hard) I learned that interesting discussions about the future direction of the project are happening on the mailing list

https://sourceforge.net/p/sigrok/mailman/message/59249346/

Re: on Thursday October 16, 2025 @12:06PM (#45607122)
It seems PayPal is having issues with their login according to downdetector.com . Multiple reports on X with similar issues: Login problems, Captcha loops ad infinitum.

Issues seem to start around 15:00 GMT

Re:GLP-1s Are Breaking Life Insurance on Monday July 14, 2025 @09:19AM (#44559863)
The topic of per-country pricing was mentioned several times.

I was wondering how big the price differences would be so I set up a quick form to collect some data points from several countries and for several products.

It would be cool if you could provide some data - I would then share it back as a reply to this thread within 1-2 days after closing the survey. The latest data entry will be possible on Sunday.

https://forms.cloud.microsoft/e/DjDgH62s21

Re:GLP-1s Are Breaking Life Insurance on Monday July 14, 2025 @07:44AM (#44558987)
I didn't have look on the studies but I would not be surprised if a decent amount of participants were completely healthy individuals. And maybe (more from random sampling) some unsuspicious mildly overweight without other problems. Especially in the earlier cohorts of testing.
Re:GLP-1s Are Breaking Life Insurance on Monday July 14, 2025 @07:40AM (#44558962)
Is that the cost in the U.S.??
Re:GLP-1s Are Breaking Life Insurance on Monday July 14, 2025 @07:03AM (#44558676)
That's why the Brits are having it ;-)

Older »