Hacker Newsnew | past | comments | ask | show | jobs | submit | isomorphic's commentslogin

The "We" is short for Westinghouse, or at least it was: Westinghouse Steered Stabilized Camera Mount, thus WESSCAM. Then they dropped an "S".

Granted pronouncing the name is ambiguous, Wes-cam or We-scam. But they're known well enough in the industry at this point that it's not a problem for them.


It's the we-scam part that's kinda funny. But of course they don't target consumers at all so that connotation doesn't matter I guess. Professionals just go by the product specs and not brand feeling.


What? You don't want travel tips from an itinerant swinger? Or for itinerant swingers?



Colima is great. However, in the upcoming macOS 26 Tahoe, and mostly in macOS 15 Sequoia, Apple is beginning to provide a first-party solution:

https://github.com/apple/container

I've been experimenting with it in macOS 15, and I was able to replace Colima entirely for my purposes. Running container images right off of Docker Hub, without Docker / Podman / etc.

(And yes, it is using a small Linux VM run under Apple's HyperKit.)


I ran into various issues I think, but my main objective was running a full k3s cluster this way, reckon this is achievable with full networking support now? Also if I already had colima setup, does new apple container provide any benefits beyond just being made by apple?


Try Orb docker. It is fast. It ha a Kubernetes cluster feature.


This thread is amazing - thank you all.

I’m surprised I didn’t stumble into any of these options, I searched and didn’t find.


Right. Define "safe."

Personally I consider Chrome to be one of the least-safe browsers available, because it sends my data to Google. Also it perpetuates a monoculture. However, others may define "safe" differently, excluding such considerations.


https://x.com/thdxr/status/1933561254481666466

ETA: The above link is at the bottom of the original submission's README. (https://github.com/sst/opencode) I posted it without context, and I have no opinion on the matter. Please read theli0nheart's comment below for an X rebuttal.


https://x.com/meowgorithm/status/1933593074820891062

--

I’m the founder and CEO of Charm. There are claims circulating about OpenCode which are untrue, and I want to clarify what actually happened.

In April, Kujtim Hoxha built a project called TermAI—an agentic coding tool built on top of Charm’s open-source stack: Bubble Tea, Lip Gloss, Bubbles, and Glamour.

Two developers approached him offering UX help and promotion, and suggested renaming the project to OpenCode. One of them bought a domain and pointed it at the repo.

At the time, they explicitly assured Kujtim that the project and repo belonged entirely to him, and that he was free to walk away at any point.

We loved what Kujtim built and offered him a full-time role at Charm so he could continue developing the project with funding, infrastructure, and support. The others were informed and declined to match the offer.

I also mentioned that if the project moved to Charm, a rename might follow. No agreement was made.

Shortly after, they forked the repo, moved it into their company’s GitHub org, retained the OpenCode name, took over the AUR package, and redirected the domain they owned.

To clarify specific claims being circulated:

- No commit history was altered

- We re-registered AUR packages for continuity

- Comments were only removed if misleading or promotional

- The project is maintained transparently by its original creator

The original project, created by Kujtim, remains open source and active—with the full support of the team at Charm.

That’s the story. We’ll have more to share soon.


> an agentic coding tool built on top of Charm’s open-source stack: Bubble Tea, Lip Gloss, Bubbles, and Glamour.

Okay I feel old now.


It's pretty funny to refer to your libraries for building a TUI as an "open-source stack". From the commonly accepted vision of a "stack" it's a pretty thin slice. It's like saying "my over-engineered component library is a stack because it involves 15 layers of abstraction!".

Neither of these companies are focused on LLMs or AI, they're both just using this as AI dust to sprinkle on top of their products.


Come on man, the BLBG stack is where it's at! What are you using, Github Copilot?!

Seriously, though: Charm creates CLI tools, not coding agents: https://charm.sh/ https://github.com/orgs/charmbracelet/repositories

Also, https://github.com/kujtimiihoxha 's recent commits are in https://github.com/opencode-ai/opencode .

But what does https://sst.dev/ (org behind https://github.com/sst/opencode) have to do with either charm or opencode?? Like Charm, it has nothing to do with coding agents.

Not for me.


You’re implying the door has now closed for people to get into coding agents. It’s a bit early for that don’t you think? These guys might one day be considered part of the founders of coding agents for all we know.


No I'm just saying I'm not touching a project with these red flags.


So which project is which here? Is Kujtim sst on github and is sst/opencode his project? Is opencode-ai/opencode the one that the two developers that went rogue made (if I understood the tweet correctly)? Or did I get it backwards?


> The original project, created by Kujtim, remains open source and active—with the full support of the team at Charm.

Anybody know where exactly this is hosted?



From the repo:

This is the original OpenCode repository, now continuing at Charm with its original creator, Kujtim Hoxha.

Development is continuing under a new name as we prepare for a public relaunch.

Follow @charmcli or join our Discord for updates.


This line in the article is horrifying:

> The researchers were surprised that when they activated VTA dopaminergic inputs into the aBLA they could reinstate fear even without any new foot shocks, impairing fear extinction.

That... seems like the first step in being able to literally induce fear without having to bother with pesky things like finding the subject's triggers. Although I suppose if one has direct access to the subject's amygdala, the point is somewhat moot.

Still, it's sort of like a reverse wirehead.

https://en.wikipedia.org/wiki/Wirehead_(science_fiction)


I feel like this would deprive the FSB/ICE/law-enforcement officials of their entire motivation for taking pride in their jobs. Automate the paperwork, yes, but let the psychopaths have their fun!


Torture is ineffective for information recovery.

Those organizations do it because they want to, not because it works.


Portability. I use YubiKeys with desktop Macs, MacBooks, iPads, and iPhones. The alternative would be to create (Secure Enclave) keys in each of those devices and register each of those keys with each thing requiring authentication... which could take a while.

I guess the alternative is something like Passkeys synchronized via iCloud Keychain. Hopefully Apple is encrypting the Passkey key material within the Secure Enclave using each other Secure Enclave's public key. Otherwise it kind of defeats the whole purpose of having a Secure Enclave. (If I remove a YubiKey from a computer, I have some assurance that computer can't authenticate with YK-controlled accounts.)


> Hopefully Apple is encrypting the Passkey key material

iCloud Keychain has always been e2e encrypted. If you lost and recovered your Apple password, you'd lose all your stored passwords.


"We have no moat. But we are well-capitalized, so in classic early-mover monopolist fashion we'll try to pull the ladder up, then use funds to bri--er, lobby--the government into smacking down climbers."


The last time I checked (this may have changed), Firefox also tags the default search engines with URL query parameters indicating that the search came from Firefox. When I tried to change this it would not let me edit the default URLs. I had to add entirely-new versions of Google and DuckDuckGo, with custom names and stripped-down URLs in order to avoid the tagging.

No doubt it is revenue-related, but it's also a privacy problem.


> it's also a privacy problem.

Can you describe how? What information is that query parameter providing to an attacker that is not being provided in 50 other ways?


Your question is assuming they're not already locking down as many of the 50 other ways as possible. Yes there are other bad things but that doesn't mean we should add #51 to that list.


OK, so it's not actually a privacy problem. Thanks.


I suppose it tells them you searched with the address/search bar instead of navigating to the search website. But I'm not sure why you would care about that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: