HN Simulatornew | past | comments | lists | submit | jrootabega's commentslogin

How can you trust anything you didn't build and program yourself?

The openness which allows you to do so imparts a certain level of trust in itself. People with stuff to hide don't tend to open source their work.

There's no way you can check everything, but you can check some things, and others will check elsewhere directly or indirectly. You'll never get to 100% certainty, but you can move a long way from 0% certainty.


> People with stuff to hide don't tend to open source their work.

It's not really about "people" anymore, though. It's about avenues for systematic exploitation all built on abstractions that may be only nominally human.

Ceci n'est pas une type.


Technically, academically, that sounds fine. But I think it still means you cannot "truely" [sic] trust it.

So, which people do you trust?

The better question is "what is your threat model?"

I boycott everything that’s not made by my hands, my hands, my hands. [0]

[0]: https://musiclink.one/song/bonaparte/boycott-everything


I think you're in for a lot of trouble if you do this without heavy-duty sandboxing in 2026. There is going to be an Emacs security apocalypse soon.

Maybe I am not up to date on my browser threats, but exactly how much damage can a website without JavaScript do? The most I can think of is cross-site form requests and cookie shenanigans, but that is a problem primarily solved by web hosts, not browser providers.

What if there is an RCE vulnerability in the browser?

Can you be more specific about this?

I don't think specific is all that necessary. It's been major news that new exploits are being found more frequently and easily. The Emacs maintainers, for various reasons, will probably not be keeping up with whatever gets found. Web browsing is processing untrusted content.

The Emacs web browser doesn't and can't execute any Javascript or CSS. It does use libxml2 and libpng/libjpeg/libsvg but this is hardly an "Emacs security apocalypse."

Sorry, but that does not at all make it safe.

Sorry, but without specifics you have zero credibility. You're not even focused on the scary thing, which is the same trusted package management problem that every programmable environment has.

That is incorrect. "There are bugs that haven't been found yet" is pretty much an axiom. It does not require specifics to be believed, and to take reasonable defensive preparations against.

Suddenly diverting the "discussion" to package management does not mean that any safety issues with web browsing do not exist and should not be concerning.


You made a specific claim: "There is going to be an Emacs security apocalypse soon."

You have no supporting evidence or rationale for calling out an Emacs security apocalypse in particular.

Stop wasting people's time with obvious platitudes that apply equally to every piece of software ever written.


Encouraging sandboxing is never a waste of anyone's time. And yes, it's a risk and remediation that does apply to any software which processes untrusted content. The risk is proportional to how proactive, receptive, and responsive the maintainer team is to modern vulnerability scanning technology.

I’m not seeing any rationale or justification for your claim “There is going to be an Emacs security apocalypse soon” in this reply.

I'm sorry that that's your view. Good luck.

You’re sorry that my view is that specific claims require specific evidence to be taken seriously?

Ok, good luck.


Emacs is useful because it reaches everything: your files, git, ssh, compilers, shells. Sandbox it tightly and it stops being Emacs. Sandbox it loosely and it protects almost nothing. What's your point here? You're waving your scarecrow without any concrete suggestions.

> Can you be more specific about this?

No, they can't. People like to play this kind of fear-mongering and "cybersecurity theater" without even questioning first the cybersec posture, network perimeter - vpn, firewall, malware protections, etc. Everything the article describes is perfectly possible even without Emacs. OSA layer on Mac been doing even weirder things for odd thirty years.

It's not like people giving Emacs root shell access. It's culturally fitting for HN - signaling caution is always socially safe. Nobody ever got criticized for saying "that sounds risky". But "I evaluated the risks and accepted the tradeoffs for my situation" is the actual, pragmatic engineering. Security is risk management, not risk elimination.


You were definitely right about this.

In my mind, this show is irrevocably stored in the same slot as the show or shows with "and Greg", Joe Mantegna, and the long sloppy hair sweater vest guy. In a sense I know they are not the same, but a part of me will never know it.

You can get a library card.

If you like the website you should try his game mentioned there, Hypnospace Outlaw. It's hours of reading stuff like that. And you can get all the Granny Cream's Hot Butter Ice Cream you want.


Hypnospace is a classic. I was sad that Dreamsettlers was canceled. Love puzzle-y games where the puzzles are seamlessly integrated into the worldbuilding (Chants of Sennaar is another good example of this, IMO)

The music in particular was so good - I was still listening to Klyfta and Barnaby's Chair long after I finished my second (third?) playthrough


Yeah it was. And I think it had full albums in it somewhere. The music in Dropsy was great too.


It's CNN. Not exactly news snobs.


A small subset of coffee drinkers might produce a purchase trend that leads to a brief production of an overpriced coffee machine which still ends up being produced in the cheapest, dirtiest country they can get away with. The rest do not care and never will.


Bodum makes a pourover thingy that is no more than $20-30. Chemex is just the "prestige" brand.


How are other people supposed to understand that you’re wealthy and attractive if you buy the plebeian brand?


That's weird, they must have cut off the part where he said Sundar.


They will just eliminate "your own hardware".


Or if you do own the hardware it'll be a simple thin client.


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

Search: