Bonum Certa Men Certa

Microsoft GitHub, DRM Enforcer, Bans Free Software

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?"

Related:



Recent Techrights' Posts

Microsoft Problems in Europe Even Before the Cheeto Tariffs
The case of Romania, Europe's notorious Microsoft fan
Oman in 2025: GNU/Linux Growing to 5%
what can Microsoft do about it except sabotage the PCs?
Microsoft Shares Collapse Again (Down $101), Fifth Round of Microsoft Mass Layoffs in Less Than 100 Days in 2025
disaster
 
Microsoft Windows in Jordan: From 99% Down to 10%
This is becoming more "normal"
Open Source Initiative (OSI) Privacy Fiasco in Detail: A "Deep Dive" Into the Complaint at the California Privacy Protection Agency
There are many facets to it and it may be the first complaint of several
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, April 07, 2025
IRC logs for Monday, April 07, 2025
Gemini Links 07/04/2025: Stock Market, Galène, and DMT Entities
Links for the day
During the Weekend We Said Fedora DEI Requires Proprietary Software, Now the Chat About It Is No Longer Accessible Over the Open Web
is this just a coincidence and an habitual change in Element?
Links 07/04/2025: US Measles Fatalities and China Launches HDMI and DisplayPort Alternative
Links for the day
Links 07/04/2025: More Cuts to Science Funding, Snail-speed Internet in Germany
Links for the day
Gemini Links 07/04/2025: Leasehold and Safe Gifts
Links for the day
In Some Countries, Laptops and Desktops Become a Dying Breed (Even Before Tariffs), Windows Has Nowhere to Go
expect more GNU/Linux on new and existing laptops
When the Credibility or 'Quality' of Clients Ceases to Matter, It's About Helping Rich Companies Like Microsoft Censor Critics (No Matter the Risks)
Bad ideas typically result in undesirable outcomes
UAE: GNU/Linux and Android at Record Levels, Windows at New Lows and Falling Below Apple
Even iOS is measured as bigger than Windows this month
Links 07/04/2025: Reddit Occupied (Social Control Media Controlled by Oligarchy), Demise of Globalisation Ongoing
Links for the day
Windows Has Fallen to All-Time Lows in Switzerland Since GNU Celebrated 40th Anniversary (GNU’s 40th Birthday in Biel, Switzerland)
GNU/Linux has been doing well in Switzerland
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, April 06, 2025
IRC logs for Sunday, April 06, 2025
Links 07/04/2025: Leaving Gemini/smolweb and Mastodon Migrations
Links for the day
In Iraq, Windows 3.1 (Percent)
There's also zero
One Person's Take on Jef Spaleta, the New Fedora Project Leader
"With a little searching, I wonder what else may be found regarding Microsoft."
Links 06/04/2025: Flood, Cool Gemini Capsule, and Long Form
Links for the day
Links 06/04/2025: Science, Politics, and Pricier Goods
Links for the day
LLM Slop Has Virtually Killed unixmen.com and Many Other Sites
There's no longer any incentive to write real articles in there
Sharp Declines for Microsoft Windows in Bangladesh (Pop. ~175,000,000), Big Gains for GNU/Linux
Microsoft Windows has been having a really hard time in poor countries
Links 06/04/2025: Fake Reviews, Privatisation Heists, and "AI" as Smokescreen for Impoverishing Humans
Links for the day
Taking a Moral Stand Against Strategic Lawsuits Against Public Participation (SLAPPs) and the Worst Offenders/Facilitators
Any other stance would sidle with moral depravity or moral hazard
Links 06/04/2025: Many New Acts of Repression and Elements of Financial Depression
Links for the day
In Qatar GNU/Linux Rose From Under 1% to Over 4% in Two Years (or Over 5% If Counting ChromeOS)
It's a big improvement compared to what we saw last year
LLM Scrapers Are a Nuisance, But They're Also a Reminder It's Time to Make Your Site Static
Perhaps the best protection is the ability to endure surges
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, April 05, 2025
IRC logs for Saturday, April 05, 2025
Links 06/04/2025: Attacks on Education, Fake Patents, and Fake (Illegal) Patent Courts
Links for the day
France: Apple and Microsoft Down, GNU/Linux Up to New Record Levels
How will tariffs against France impact things in the coming months?