I guess if done via unofficial plugin it would be up to the end user to weigh the benefits vs the risk of getting sued.
If not, how do we get Canon’s attention? I’ve sent emails, tweeted at them, asked the questions during their Q&A livestreams. So far I’ve only been ignored.
Would a Change.org campaign get their attention? Should we create a dedicated “protest” website for this issue and promote it on social media?
I can create the website but I’d need devs with in depth technical understanding of the issue to write up a demand, be willing and available for communication with Canon in case some of their engineers contact us.
We should present ourselves as a “large” collective of open source projects, developers and Canon customers and users.
We could probably push this “action” and promote it on Softpedia, Forbes, Ars Technica, ZDNet, Phoronix, EOSHD and maybe a few others if somebody has any contacts?
I’d assume that the “FOSS” youtubers would pick this up the same day.
We could also push it on social media platforms: Canon subreddit, Hacker News, Twitter, Facebook, Instagram etc.
If we create enough of an outrage it could be picked up by fstoppers, photonews, froknowsphoto, tony… (i know, i know… but we really need it in this case and it’s for a good cause).
If we could have the whole thing translated to Japanese even, it would show that we mean business.
Thoughts?
I mean, I am currently on 5Dmk4 and 77D readying to invest into R5 if the next firmware pulls this camera from the trash.
I think in light of the recent bad press (terrible actually), Canon might use some good press and this would be them directly listening to their “technical” users and also developers. And they are really lacking here right now with the release of R5.
It would be a kind of quid pro quo.