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

Engagement-bait.

With a dash of humble-brag.


"Engagement-bait"

That's a new term to me. I like it!

It's a good word for the vacuous "Windows is rubbish" article that got submitted a couple of times yesterday.


Phoenix is a desert oven. It will never grow like Paris.


They mention something about not wasting space for unnecessary memory.


A bit difficult given that incandescent lights stopped being sold 10 years ago.


You can use halogen bulbs if old school incandescent is not sold where you live.


They're still available and popular in many countries, often significantly cheaper than LED bulbs.


They are still sold, but now often as 'heaters' or specialty bulbs, when in fact normal, to skirt regulations.


Freedom also means being free to use DRM if you want to.

Nobody is holding a gun to your head to open a Netflix account.


You are right, it's not a gun, it's Widevine they hold against your head. Of course everyone is free to use DRM if they want to, however, no one should be free to expose others to the risks/consequences of DRM.

It's basically Popper on tolerance all over again. Herefore it should not be a surprise to notice that Mozilla's strategic failures already are costing us freedom.

See: https://en.wikipedia.org/wiki/Paradox_of_tolerance for details.


Yes, being a browser used by small minority surely gives them major bargaining powers to rid the web of DRM.

Or it would simply make Spotify, Netflix and other similar sites not function on Firefox and reduce their market share even more.

Who knows...


The article itself [0] asnwers to this argument.

> How did it get into the spec? Oh, it got into the spec because when the Content Mafia pressured W3C to include it, Mozilla caved. At the end of the day they said, "We approve of this and will implement it". Their mission -- their DUTY -- was to pound their shoe on the god damned table and say: "We do not approve, and will not implement if approved."

[0] https://www.jwz.org/blog/2024/06/mozillas-original-sin/


It is not an argument and it doesn't "answer" anything. It simply suggests that they should have said no, without going in to details what that would entail.

At the end of the day, does it really matter? DRM extension is external and disabled by default on fresh install, and it asks to be enabled only once you encounter the DRM content. You can always say no if you deeply care about it.


Its /not/ (only) external, as your "disabled" in the same sentence already implies. Fundamental changes have been made that transfer power from the end user to elsewhere without end user consent nor them understanding the scope and meaning of the problem at hand. This transfer was ( partially ) forced by third parties not acting in the end user or Mozillas interest; in fact the opposite is true. Not only damages technical in nature where dealt, but also in terms of good name & reputation since the adversary made Mozilla squander their responsibilities and by extension betray their relationship with the end users. This is a textbook example of howto drive any organization into the ground.


In my understanding, they could at least have fought for this not to get into the W3C spec, but they did not object, according to the blog. This is one the kind of stuff that endanger free internet, which mozilla is supposed to fight for.


The blog is wrong, I think they did object afaik, the blog (and others) just think they should have objected more strongly or not implemented it.


Ok, if that is the case I stand corrected.


Sometimes you do get arbitrary code execution, but you are in a Chrome sandbox.

One use of mseal is for defense in depth, where you try making it as hard as possible to un-sandbox the sandbox.


mseal is not designed to protect against sandbox escapes


Despite what many programmers think, code is not law.

Just like a bug in a smart lock does not allow you to enter a house because "you were allowed in".


People keep saying that, but not even one case is documented.

These chains are created by startups with VC money, they are not going to hire hitmans.


https://www.cbc.ca/news/canada/toronto/crypto-king-pleterski...

It's not so much the projects themselves who are a threat, but the thousands (?) of random individuals whose value is stolen.


North Korea might. Silk Road went under due to attempting to hire one.

The more likely concern is that someone will sell you out to any of the numerous governments who feel you wronged them. Leading to decades of life in prison.


I wouldn't expect there to be documented cases yet. The hypothetical case in question is a hacker taking hundreds of millions of dollars, not being caught initially, but then being caught years later. Crypto as a whole is just 15 years old, and it's only really been hot for under a decade. There have only been a handful of cases with such large dollar amounts, and most occurred in the last 5 years. And I expect most of the people who pull this off will be properly paranoid.


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

Search: