He might already have a main account but intentionally doesn't want to use it. I've noticed on X that OpenAI employees tend to post a lot more regarding their employer on their main X accounts than Anthropic employees do.
And has a very vocal/opinionated owner. You know what you're getting with Sourcehut. (And I don't mean that in a bad way).
Rightly or wrongly, Codeberg had a different feel. For a while it felt like it was trying to be a refuge from Github. But then again, maybe that was projecting something on them that they didn't intend.
Once again, the stability of a BDFL is vindicated.
Democracy works ok in extremely complex systems like giant distros—Debian’s governance is slow but functional—but it seems to need guardrails around the process. (From what I can tell, an excruciating process is the best guardrail. Glacially slow decision-making means that mobs burn themselves out before they get to voting.)
I wouldn't call Drew DeVault stable, he crashed out after 4chan simultaneously exposed his creation of the RMS report alongside his huge loli porn fixation.
He may not be, but the product has been. Same goes with Theo and OpenBSD.
Hyper-productive people are often volatile. Putting up with it is a necessary tradeoff, as the systems they produce often fill a niche that nobody else will serve adequately.
Guys like Theo have a baseline to uphold and I think decades of dealing with the public on an open project with specific goals that need to be met would turn anyone sour. People respect him for his actual work though, like they used to with Torvalds before he got bought out by IBM.
Drew I think is just kind of a dick who has a history of putting his personal crusades before delivering a product people want. I remember a few years back sourcehut being reported as unstable and he went and lashed out at people who were complaining to him about it instead of fixing the issues. And he banned crypto projects cause he doesn't like them, at least Codeberg held it to a vote.
Patrick Volkerding is a pretty stable guy, I think he's the model more BDFLs should strive to be.
Patrick is an unusual exception; I’d actually put people like Drew, Theo, and pre-corporate Linus in the midpoint. The opposite extreme of Patrick would be unfortunate cases like Reiser and Ian Murdock.
I think Drew suffers a little from lack of focus. I greatly appreciate his work on Harelang, sway, and aerc for instance, but these are quite far from his Sourcehut work. (I can see how aerc and Sourcehut dovetail with the plaintext email focus, at least.)
Stability? A BDFL can make decisions at a whim that radically destabilize and change the project. Lording over and causing immense harm to the community without any sort of accountability is a recipe for disaster.
Good for everyone? A BDFL can unilaterally make decisions that prioritize their own desires over everyone else. It becomes about their personality rather than the project.
Functional? A BDFL is less functional, seeing how there is no requirement that the BDFL do anything that the community of people actually wants.
If you're saying you're opposed to democracy because you don't like the decision that codeberg reached democratically, the BDFL can do the exact same thing. Except the process is far worse, because there is literally no input from anyone else on making the decision.
You can say all these things, and yet my experience with BDFLs in reality has been the opposite. More often, they make good decisions that continue their vision for the project, rather than abruptly redirecting the project. This is because productive people are often relatively consistent in their vision and direction.
Small community “democracy” OTOH often devolves into ochlocracy, or reactive mob rule. Small communities are easily swayed, don’t often have a durable vision, and can easily be infiltrated by people who don’t have the best interest of the project (or the users) at heart.
The only thing that can offset these effects is a heavy process, like Debian has, which slows down the mob and forces everyone to consider all sides of the issue. This can actually work! And for some projects it’s a better fit than a BDFL.
I think there is a slight difference between open source and government there. With open source you can just leave and pick another one. Or start your own.
Well I suppose that's also technically true of governments...
Some cheaper devices I have (e.g. rechargeable LED light strip) _only_ charge via power-only cables. Was maddening when I realized I had thrown out all but one of the cables that can charge it.
More often than not these are usually cheap Chinese devices that are expecting a USB-C to USB-A (power-only) cable, because they're actually USB-A devices, with USB-A circuitry, modified slightly to appear as if they're USB-C.
Basically they skipped out on building power negotiation smarts that are required to support real USB-C charging, and instead just swapped out the physical connector.
Yep. The two fucking resistors. All it takes 2 x 5.1K, and yet, somehow, people keep fucking it up.
It's not expensive or complex. It's just that somehow, no one thought to look up "how to add type c to your device" online, or ask an LLM, or put literally any effort into making sure the device works as it should.
You're saving a fraction of a cent per device, while banking on customers not sending it back as defective because it didn't charge when they tried it with a random cable.
If it is a deliberate choice, it's a really, really dumb one.
Advertising is primarily about convincing is to buy things we don't need, don't want, or which are 'stupid' in some way.
Half empty plastic packaging, especially the sort where the company spent money to [re-]design it to deceive people - stupid. It should be illegal. Near ubiquitous.
One of my theories is that there is a deliberate choice happening by people who don't realize it is as simple as a couple of resistors and think they need some fancy PD negotiation chip.
Even over on r/usbchardware it is super common for people to conflate "PD" with this missing resistor issue. Part of the confusion is that the devices that people want to charge with are very likely to be PD power supplies.
> As executive chairman, Cook will assist with certain aspects of the company, including engaging with policymakers around the world.
This gives me the impression that at least for the near-term, Cook will still be the one groveling to the Trump White House. Whatever you think about that, that's probably helpful for Ternus' dealings with the next administration.
> With background computer use, Codex can now use all of the apps on your computer by seeing, clicking, and typing with its own cursor. Multiple agents can work on your Mac in parallel, without interfering with your own work in other apps.
How does that even work technically? macOS doesn't support multiple cursors. On native Cocoa apps you can pass input to a window without raising via command+click so possibly they synthesized those events, but fewer and fewer apps support that these days. And AppleScript is basically dead, so they can't be using that either.
I also read they acquired the Sky team (who I think were former Apple employees). No wonder they were able to pull of something so slick.
I remember looking trying to build something like this 6 years ago[0]. There are some interesting APIs for injecting click/keystroke events directly into Cocoa, and other APIs for reading framebuffers for apps that aren't in the foreground.
In particular there was some prior art that I found for doing it from the OpenQwaQ project, which was a GPLv2 3D virtual world project in Squeak/Smalltalk started by Alan Kay[1] back in 2011.
If I recall correctly, it worked well for native apps, but didn't work well for Chromium/Electron apps because they would use an API for grabbing the global mouse position rather than reading coordinates from events.
Which specific ones though allow you to send input to a window without raising it? People have been trying to do "focus follows mouse [without auto raise]" for a long time on mac, and the synthetic event equivalent to command+click is the only discovered method I'm aware of, e.g. used in https://github.com/sbmpost/AutoRaise
There is also this old blog post by Yegge [1] which mentions `AXUIElementPostKeyboardEvent` but there were plenty of bugs with that, and I haven't seen anyone else build on it. I guess the modern equivalent is `CGEventPostToPSN`/`CGEventPostToPid`. I guess it's a good candidate though, perhaps the Sky team they acquired knows the right private APIs to use to get this working.
Edit: The thread at [2] also has some interesting tidbits, such as Automator.app having "Watch Me Do" which can also do this, and a CLI tool that claims to use the CGEventPostToPid API [3]. Maybe there's more ways to do it than I realized.
Could you elaborate on what you mean? My understanding of the Cocoa event loop was that ultimately everything is received as an NSEvent at the application layer (maybe that's wrong though).
Do you mean that you can just AXUIElementPerformAction once you have a reference to it and the OS will internally synthesize the right type of event, even if it's not in the foreground?
yes you can do a lot background UI interaction using the AX APIs. Displaying a second cursor is also simple, just a borderless, transparent window that moves around.
For the few things you cannot achieve with the Accessibility API's there are ways to post events directly to an app - even though CGEventPostToPid is mostly broken when used on its own. These require a combination of CGEventPostToPid and CGEventTapCreateForPid. (I have done a lot of this stuff in my BetterTouchTool app)
Neat, good to know! And it does seem my mental model of event loop was broken. Accessibility related interactions don't have any related NSEvent.
They are handled as part of the "conceptual" run loop, but they seem to be dispatched internally by AXRuntime library from a callback off some mach port. And because of this, the call to nextEventMatchingEventMask in the main -[NSApplication run] loop never even sees any such NSEvent.
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] (in AppKit)
_DPSNextEvent (in AppKit)
_BlockUntilNextEventMatchingListInModeWithFilter (in HIToolbox)
ReceiveNextEventCommon (in HIToolbox)
RunCurrentEventLoopInMode (in HIToolbox)
CFRunLoopRunSpecific (in CoreFoundation)
__CFRunLoopRun (in CoreFoundation)
__CFRunLoopDoSource1 (in CoreFoundation)
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ (in CoreFoundation)
mshMIGPerform (in HIServices)
_XPerformAction (in HIServices)
_AXXMIGPerformAction (in HIServices)
In some sense this is sort of similar to apple events, which are also "hidden" from the caller of nextEventMatchingEventMask. From what I can see those are handled by DPSNextEvent, which sorts based on the raw carbon EventRef. aevt types have `AEProcessAppleEvent` called on them, then the event is just consumed silently. Others get converted to a CGEvent and returned back to caller for it to handle. But of course accessibility events didn't exist in Classic mac, so they can't be handled at this layer so they were pushed further down. You can almost see the historical legacy here..
Maybe they used Claude to come up with a good method to do this. /s
But I was also wondering, how this even works. The AI agent can have its own cursors and none of its actions interrupt my own workflow at all? Maybe I need to try this.
Also, this sounds like it would be very expensive since from my understanding each app frame needs to be analysed as an image first, which is pretty token intensive.
They aquired Vercep, and their older agent Vy did have background agent. IIRC the recent computer-use agent in Claude is based on Vy, so i'm kinda surprised that feature didn't carry over to Claude desktop app.
This is slightly different from what OpenCode was banned from doing; they were a separate harness grabbing a user’s Claude Code session and pretending to be Claude Code.
OpenClaw was still using Claude Code as the harness (via claude -p)[0]. I understand why Anthropic is doing this (and they’ve made it clear that building products around claude -p is disallowed) but I fear Conductor will be next.
and they’ve made it clear that building products around claude -p is disallowed
Imagine not being able to connect services together or compose building-blocks to do what you want. This is absolute insanity that runs counter to decades of computing progress and interoperability (including Unix philosophy); and I'm saying this as someone who doesn't even care for using AI.
Even better, running something like 'claude -p' at the command line is exactly the kind of thing a model would do. Mine loves to run python, node, and a dozen other applications.
Except it's not counter to history for SaaS services. Many will ban unauthentic usage from non-human clients. Getting banned from a SaaS service for boting is nothing new
It is confusing for a company to sell you the subscription service, say "Claude Code is covered", ship Claude Code with `claude -p`, and then say "oh right, actually, not _all of Claude Code_, don't try and use it as a executable ... sorry, right, the subscription only works as long as you're looking at that juicy little Claude Code logo in the TUI"
The disrespect Anthropic has for their user base is constant and palpable.
Subscriptions are going to leave you open to changes in the subscription terms at any time. This is especially true of AYCE subscriptions for something with a substantial marginal cost of additional usage.
If you want unrestricted and unlimited usage, it's available through the API. Complaining about the subscription like this is basically saying, I want what you're offering, but I demand it for cheaper than what you charge for it. That doesn't make any more sense here than it does at the grocery store.
This strikes me the same way the people in college who would print 497 empty pages at the end of the semester for the quota "they'd paid for" or that one guy who made lemonade at restaurants with the free lemon wedges and sugar packets. "Contempt for users" is silly. Adjusting terms to handle users who use things as not intended isn't contempt.
Contempt for users is not silly when the CEO of said company has repeatedly claimed they will replace SWEs "end-to-end" by next year.
I'm not sure what to say. You're either listening to the actions of these companies, or you're not in a place where you feel the need to be concerned be their actions.
I'm in a place where I'm concerned by their actions, and the impact that their claims and behavior have on the working environment around me.
At no point in the last 10,000 years of human civilization has there not been a developing technology that threatened to forever reshape and displace a class of labor.
Or are you also upset about the modern plight of the telephone operator, farrier, or coal miner?
And? Hyperbolic fear of change always exists and there's always been more work.
Marx' whole idea of Communism was predicted on the fact that he assumed industrialization would lead to a post-scarcity society requiring virtually no work and a overhaul of how everything was owned and produced. Boy was he wrong.
Oh nooo, labor might be automated and we might see advancement that makes the Industrial Revolution look small! Oh, the humanity! Please someone, stop progressing humanity, I need to cling to my sticks!
All AI prices will rise soon - probably shortly after the IPOs. The new prices will be eyewatering compared with today’s. This bulling change is lengthening the time until Anthropic have to raise the subscription prices, so those of us who’re not doing 24hr claw stuff can continue to use the tools the way we’ve gotten used to.
But OpenClaw is not a product. It's just a pile of open source code that the user happens to choose to run. It's the user electing to use the functionality provided to them in the manner they want to. There's nothing fundamental to distinguish the user from running claude -p inside OpenClaw from them running it inside their own script.
I've mostly defended Anthropic's position on people using the session ids or hidden OAuth tokens etc. But this is directly externally exposed functionality and they are telling the user certain types of uses are banned arbitrarily because they interfere with Anthropic's business.
This really harms the concept of it as a platform - how can I build anything on Claude if Anthropic can turn around and say they don't like it and ban me arbitrarily.
Claude Code is not a platform and you’re not meant to be building on it. Netflix is also not a platform and you shouldn’t be running code (open source or not) to mass download Netflix movies either.
It's a reasonable comment, and I should be clear, I don't expect it to be a platform. But I do expect to be able to use its advertised features for any reasonable purpose they can support.
Where it leaves me is is sort of like the DoD - nobody should use Claude for anything. Because Anthropic has set as principle here that if they don't like what you do, they will interfere with your usage. There is no principle to guide you on what they might not like and therefore ban next. So you can't do anything you want to be able to rely on. If you need to rely on it, don't use Claude Code.
And to be clear, I'm not arguing at all against using their API per-token billed services.
That rather hinges on exactly what "can support" means. Can they support use cases which work individually but would exceed their capacity to provide if done by a large number of their subscribers?
Ah thank you, this is very helpful distinction to know.
When they shut down open code, I thought it was a lame move and was critical of them, but I could understand at least where they're coming from. With this though, it's ridiculous. Claude core tools are still being used in this case. Shelling out to it to use it there's no different than a normal user would do themselves.
If this continues, I'll be taking my $200 subscription over to open AI.
If OpenAI does it too, well then I guess my principles will be challenged. Gemini CLI is unfortunately too eager to use Flash despite my setting it to use Pro, and it generates ass code that doesn't work, so that's out. I might have to invest in some GPUs then and run local. We'll cross that bridge when we get there though.
When this happens I will have to look at other providers and downgrade my subscription. Conductor is just too powerful to give up. It’s the whole reason why I’m on a max plan.
Has there been an actual change to their ToS? As of the last change which I saw reach HN, a week or so ago, `claude -p` was still in compliance with the Claude Code ToS. Has that language changed?
Came here to say the same. I remember the discussion on HN back then where we discovered that an official from Anthropic made clear that claude -p was still okay.
That's my understanding too, though i haven't checked it. running claude -p would be horribly inefficient.
I would not be surprised if openclaw added some compatibility layer to brute force prompts through claude -p as a workaround. This isn't the first time that openclaw was "banned" from claude subscriptions.
Why are they doing that? Opus is the only good way to run Claw. Do they regret making it cheaper or what?
Also what's the point of Claude -p if not integration with 3rd party code? (They have a whole agents SDK which does the same thing.. but I think that one requires per token pricing.) I guess they regret supporting subscription auth on the -p flag
FWIW I am sympathetic to Anthropic here, but OpenClaw _is_ using the Claude Code harness (via claude -p). But yes, Anthropic has made it clear they don’t like this.
I have had to do this, well over a decade ago now, when working at a place that was a pretty big deal in the node world, and node was still pretty new. They helped us.
I would imagine GH would do the same if its a high enough profile issue.
Yep, we had to do this recently with Renovate, where we had too many releases, and new publishing hit a size limit on the registry, so we needed support to help us unpublish a load of old releases