Gemini version available ♊︎

Microsoft GitHub, DRM Enforcer, Bans Free Software

Posted in DRM, Free/Libre Software, Microsoft at 7:08 am by Dr. Roy Schestowitz

Reproduced from Mobileread, as can be seen here:

Initially, I didn’t want create an account on this site and keep all discussion on GitHub (the fewer accounts one has, the easier it is to stay anonymous …), but I guess with the GitHub being gone, it’s about time to answer some of the questions here …

Maybe GitHub hasn’t been the best choice for a platform, but I didn’t expect there to be DMCA claims when there have been none over the recent years in Apprentice Harper’s repository. I guess, in the long term, I should move to another platform.

I received the first message from Github about the DMCA claim on January 4th in the late evening, with a time line of 24h to remove the “offending” content. Of course that deadline is rather short – I am obviously not using my “main” mail address for stuff like this, so I didn’t check this account every single day, and only found out the repository was blocked (some time on January 6th) when I checked this forum thread and saw the discussion on January 7th.

The GitHub FAQ states that when one misses the 1-day window to make requested changes, one can request an additional time of 1 day to perform the changes. I requested that by mail on January 7th, but so far the GitHub support hasn’t gotten back to me yet. Right now, I see the same page that you all see – repo unavailable due to DMCA. They could have at least given the repo owner access to update the code, but they didn’t.

Rather disturbing that they are allowed to block a repo after just one day of no response (they could have given me a notification on the Github page itself, in addition to the mail, then I would have seen it before the deadline was over …), and then don’t respond to the topic for multiple days, but maybe their support doesn’t work on weekends and they don’t consider stuff like this urgent now that the repo’s down and they did what they legally have to do …

The goal is to hopefully get Github to restore the repository once they finally read my mail, then remove the offending code from the repository, and have the plugin no longer contain the offending LCP code on Github to comply with the DMCA request.

The DMCA request mentions nothing about the difference between library books and bought books. The request states that the original repositories (apprentice harper and so on) are not part of the takedown – not because they have blocks for library books, but because they don’t support LCP at all. So I doubt adding a block for library books would have prevented this takedown (or, would be an acceptable solution to get the repository back). The guys behind LCP know how easy it is to edit Python code to remove such blocks, and I think with this plugin being the first public solution for LCP DRM removal, I guess they are more concerned with people knowing the algorithm, and they think that with a DMCA request for this repo they can remove that from the entire internet.

I don’t want to piss off GitHub (and Readium?) even more by now creating a new account or repository. Even though it’s probably fine as far as the DMCA goes (if there’s no LCP code in the new repo), it certainly violates Github TOS to just make a new repo when there’s a pending takedown. So I’m going to wait for the support to respond, which they are supposed to according to their own FAQ. If they don’t, I guess the plugin moves to another platform.

As for the other topics being discussed here in the last couple days:

- Someone mentioned that based on the description of LCP in the takedown notice, this DRM doesn’t sound so bad – maybe it doesn’t, but there’s one thing they are purposefully omitting in that description, and one they either deliberately or accidentally explained wrong. They are claiming that LCP is oh-so-open and doesn’t lock the user into a proprietary environment.
Yeah, LCP is not as proprietary as Adobe or Amazon, but it’s still proprietary. Yes, they have the source code available on their GitHub, but still require you to pay huge amounts for licenses if you want to use the code. A critical piece of source code for the project is missing on their Github, and you only get this code (with a very restrictive license) if you pay them. So, the code on the GitHub is useless, as if you forked it and built the code yourself, it wouldn’t work.
And the other thing they omitted is the fact that there’s (almost) no reader support. They claim the DRM doesn’t hurt content accessibility, it lets users share content with friends, and so on. But that’s only true if you’re reading on a phone or computer, or if you have a very new eReader from particular vendors.
If the codebase would have *really* been open-source (meaning, I take the source code, built it, and get a 1:1 100% identical binary to the one they give to users, without paying for a license), AND Readium had support on all eReaders, I doubt I would have deemed it necessary to add LCP support. The main reason I added this support was not to “crack” books and share them with the world, it was getting them to work on MY readers …

- The latest release of the plugin (10.0.2) does not yet support QT 6 / Calibre 6, but the latest commit on master already does. I doubt there’s many people that have that downloaded, with the repo now gone. Though, even if GitHub decides to block the repo permanently and I don’t find any other useful hosting, the plugin only required very small changes in two or three places that became apparent when reading the error messages, so it should be easy for others to fix that, if needed.

As noted in Mastodon: “RIAA showed that it was acceptable to use GitHub’s (legally mandated) DMCA process for DMCA section 1201… Any tool like this should probably self-host their code repository at this point… Can we please kill these anticircumvention laws? Maybe then we won’t need tools like DeDRM?”


Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New

  1. IRC Proceedings: Sunday, June 04, 2023

    IRC logs for Sunday, June 04, 2023

  2. Links 04/06/2023: Unifont 15.0.05 and PCLinuxOS Stuff

    Links for the day

  3. Gemini Links 04/06/2023: Wayland and the Old Computer Challenge

    Links for the day

  4. StatCounter: GNU/Linux (Including ChromeOS) Grows to 8% Market Share Worldwide

    This month’s numbers from StatCounter are good for GNU/Linux (including ChromeOS, which technically has both GNU and Linux); the firm assesses logs from 3 million sites and shows Windows down to 66% in desktops/laptops (a decade ago it was above 90%) with modest growth for GNU/Linux, which is at an all-time high, even if one does not count ChromeOS that isn’t freedom- or privacy-respecting

  5. Journalism Cannot and Quite Likely Won't Survive on the World Wide Web

    We’re reaching the point where the overwhelming majority of new pages on the Web (the World Wide Web) are basically junk, sometimes crafted not by humans; how to cope with this rapid deterioration is still an unknown — an enigma that demands hard answers or technical workarounds

  6. Do Not Assume Pensions Are Safe, Especially When Managed by Mr. EPOTIF Benoît Battistelli and António Campinos

    With the "hoax" that is the financial assessment by António Campinos (who is deliriously celebrating the inauguration of illegal and unconstitutional kangaroo courts) we urge EPO workers to check carefully the integrity of their pensions, seeing that pension promises have been broken for years already

  7. Links 04/06/2023: Why Flatpak and Wealth of Devices With GNU/Linux

    Links for the day

  8. Gemini Links 04/06/2023: Rosy Crow 1.1.3 and NearlyFreeSpeech.NET

    Links for the day

  9. IRC Proceedings: Saturday, June 03, 2023

    IRC logs for Saturday, June 03, 2023

  10. Links 04/06/2023: Azure Outage Again (So Many!) and Tiananmen Massacre Censored

    Links for the day

  11. Links 03/06/2023: Qubes OS 4.2.0 RC1 and elementaryOS Updates for May

    Links for the day

  12. Gemini Links 03/06/2023: Hidden Communities and Exam Prep is Not Education

    Links for the day

  13. Links 03/06/2023: IBM Betraying LibreOffice Some More (After Laying off LibreOffice Developers)

    Links for the day

  14. Gemini Links 03/06/2023: Bubble Woes and Zond Updates

    Links for the day

  15. Links 03/06/2023: Apache NetBeans 18 and ArcaOS 5.0.8

    Links for the day

  16. IRC Proceedings: Friday, June 02, 2023

    IRC logs for Friday, June 02, 2023

  17. The Developing World Abandons Microsoft Windows, GNU/Linux at All-Time Highs on Desktops/Laptops

    Microsoft, with 80 billion dollars in longterm debt and endless layoffs, is losing the monopolies; the media doesn’t mention this, but some publicly-accessible data helps demonstrate that

  18. Links 02/06/2023: Elive ‘Retrowave’ Stable and Microsoft's Half a Billion Dollar Fine for LinkeIn Surveillance in Europe

    Links for the day

  19. Linux Foundation 'Research' Has a New Report and Of Course It Uses Only Proprietary Software

    The Linux Foundation has a new report, promoted by Clickfraud Spamnil and others; of course they’re rejecting Free software, they’re just riding the “Linux” brand and speak of “Open Source” (which they reject themselves)

  20. Links 02/06/2023: Arti 1.1.5 and SQL:2023

    Links for the day

  21. Gemini Links 02/06/2023: Vimwiki Revisited, SGGS Revisited

    Links for the day

  22. Geminispace/GemText/Gemini Protocol Turn 4 on June 20th

    Gemini is turning 4 this month (on the 20th, according to the founder) and I thought I’d do a spontaneous video about how I use Gemini, why it's so good, and why it’s still growing (Stéphane Bortzmeyer fixed the broken cron job — or equivalent of it — a day or two after I had mentioned the issue)

  23. HMRC Does Not Care About Tax Fraud Committed by UK Government Contractor, Sirius 'Open Source'

    The tax crimes of Sirius ‘Open Source’ were reported to HMRC two weeks ago; HMRC did not bother getting back to the reporters (victims of the crime) and it’s worth noting that the reporters worked on UK government systems for many years, so maybe there’s a hidden incentive to bury this under the rug

  24. Our IRC at 15th Anniversary

    So our IRC community turns 15 today (sort of) and I’ve decided to do a video reflecting on the fact that some of the same people are still there after 15 years

  25. IRC Proceedings: Thursday, June 01, 2023

    IRC logs for Thursday, June 01, 2023

  26. Links 02/06/2023: NixOS 23.05 and Rust 1.70.0

    Links for the day

  27. Gemini Links 02/06/2023: Flying High With Gemini and Gogios Released

    Links for the day

  28. Links 01/06/2023: KStars 3.6.5 and VEGA ET1031 RISC-V Microprocessor in Use

    Links for the day

  29. Gemini Links 01/06/2023: Scam Call and Flying High With Gemini

    Links for the day

  30. Links 01/06/2023: Spleen 2.0.0 Released and Team UPC Celebrates Its Own Corruption

    Links for the day

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts