4,197 karma · joined April 14, 2016
> Denuvo DRM Outage Leads to Major Games Being Unplayable
[0] https://gamerant.com/denuvo-drm-outage-major-games-unplayabl...
> The cracked version of Resident Evil Village runs better, testing confirms
[1] https://www.pcgamer.com/resident-evil-village-drm-denuvo-stu...
> Shadow of the Tomb Raider Reportedly Runs Better Now That Denuvo Has Been Removed
[2] https://gamerant.com/shadow-of-the-tomb-raider-reportedly-ru...
As a result, for many companies obsessed with KPIs, the only KPI for customer support is "price". In that lens, they are optimizing.
Obviously this situation is awful for customers.
[1] https://www.propublica.org/article/meet-the-customer-service...
> HN is not a site for discussing legal matters per se, but only the ones that gratify intellectual curiosity, and only to the extent that they do. That is what we're optimizing for here.
Taken at face value, it is unclear if this particular discussion "gratifies intellectual curiosity"
> Thanks for contacting us. To get help with this issue, please reach out to Curl: https://curl.se/gethelp.html
The original tweet was deleted. If this were a bug report related to the system distribution of curl on M1 macOS (apple's proprietary platform), it seems somewhat entitled that Apple would pass the support burden to the curl author without providing resources to debug on their proprietary platform
As an example of an "impure language" with security in the form you envision, Deno allows you to specify access controls on a per-script or per-dependency basis. You can specify imports that prevent dependencies from opening sockets or writing files or reading files.
Many years ago npm inc treated download and package counts as KPI. They pushed back against sensible measures like code signing, instead centralizing the ecosystem and encouraging cross-dependencies within their registry. A more security-oriented package manager would have focused on code signing and vendoring strategies.
You can't be coerced to make business decisions like selling out to a competitor or aggressively raising prices if you own the company.
SVGO https://github.com/svg/svgo is used by many graphics software but hasn't seen donations commensurate with usage https://opencollective.com/svgo
> One thing that we have learned is that piracy is not a pricing issue. It’s a service issue ... The easiest way to stop piracy is not by putting antipiracy technology to work. It’s by giving those people a service that’s better than what they’re receiving from the pirates.
~10 years ago Netflix was superior. With the shifting catalog and the pricing tiers for high-quality streaming, the value proposition is not as clear today.
> Your Switch keys and either your dumped firmware or recent game cartridge untrimmed XCI
> Your dumped Nintendo Switch games or homebrew
You don't need a hacked switch if you can find the homebrew apps / games / firmware on the internet and if you can find a donor set of keys. But that enters questionable territory
4.5MB XLSX https://techcommunity.microsoft.com/t5/excel/wordle-with-exc...
It uses the full information when generating possibilities, including letters that are not in the solution/
> Not mentioned is that the full test sqlite test suite is proprietary and you need a super expensive sqlite foundation membership to get access to it.
According to Dr Hipp [2], no one bought the test suite. So there are definitely deficiencies in the test suite which may have been better addressed if the full test suite was open.
[1] https://news.ycombinator.com/item?id=33346661
[2] https://corecursive.com/066-sqlite-with-richard-hipp/#billio...
For example, setting.dev is $180/yr https://domains.google.com/registrar/search?searchTerm=setti...
It is likely that there was no premium pricing in the beginning. It was established after the initial lease
nonws:
<tab>echo nonws
ws:
<tab>echo wsRelicensing is an increasingly popular choice for OSS devs to to try to monetize usage, and it works since it is oftentimes cheaper to just pay than to rewrite software.
> If you follow the above, you’ll see the supposed “free rider” problem is simply a natural consequence of open source being free as in beer: it’s not a problem to be solved, it’s a consequence to be embraced and exploited.
"to be embraced and exploiting" is referring to the consequence, not to the open source developers.
What the author is trying to say is that a large segment of the users of open source software are using it because it is free as in beer. That sounds like a problem, and it is if you are narrow-mindedly thinking about how to monetize the open source software directly. But there are other ways for open source developers to take advantage of the opportunity.