Independent of that: how dangerous is ML dev to the cameras themselves (in terms of brick potential)? Permanently bricking a camera in the price range of the 1DX is not exactly my idea of a good time. :-)

Similarly, How is challenging DMCA 1201 going?

In relation to the rent-seeking behavior of Canon they allegedly nudged a certain open-source camera firmware project not to support some of their most high-end cameras. But with Canon losing interest in DSLRs I hope the situation changes.

> There is some speculation Nintendo was involved with the death of the Nintendo 64 emulator UltraHLE a long time back, but this was never confirmed.

iirc it got c&d but a case was never filed in court, the source code turned up eventually anyways.

    Updated Date: 2024-06-02T11:17:09Z

Someone know more to this story? (i.e what was exactly on the disc, and what were the legal basis of said police action)

With the debatable demise of organic community platforms and the rise of curated social-media recommendation by algorithms it is always nice to facilitate interaction between two vaguely-human entities. :-)

Take care!

In addition just because code is available publicly on GitHub does not necessarily mean it is permissively licensed to use elsewhere, even with attribution. Copyright holders not happy with their copyrighted works publicly accessible can use the DMCA to issue take-downs that GitHub does comply with but how that interacts with Copilot and any of its training data is a different question.

As much as the DMCA is bad law rather funny seeing Microsoft be charged in this lawsuit with the less known provision against 'removal of copyright management information'. Microsoft does have more resources to mount at defence so it will probably end up different compared to a smaller player facing this action.

It is a paid product (eg $x/hr cloud billing). Supposedly easier to obtain than the security research device.

[1] https://corellium.com

If this was ten years ago myself might have agreed with others on the full-disclosure approach. However considering the irresponsibility of 'lowest common denominator' of people in modern times do you really want to enable script-kiddies to violate the privacy of many unwitting victims with a metaphorical loaded gun?

Perhaps an amicable middle-ground could be demonstrating the existence of these vulnerabilities in public (such as with a video) and withholding the exact exploit code from publication at least initially. Assuming you are at minimal risk of retaliation from the vendor and a diplomatic resolution fails to achieve results you could carefully measure the pros and cons of full publication and wash your hands of it.

However. Does anyone else feel uneasy about Matrix end-to-end encryption and how some people justify its provenance by asserting it is the same encryption as Signal despite the homebrew implementation by Matrix having obvious differences to attempt to accommodate multi-device support among other features?

Worth noting that certain people probably have means to dump streaming HD Netflix content but keep these methods private because presumably Netflix can change things around to break them. So the cat and mouse game continues.