D-side (talk | contribs)
D-side (talk | contribs)
XKCD #129: new section
 
(One intermediate revision by the same user not shown)
Line 2: Line 2:


I haven't done the proper research on this, but don't most OSes come with DRM baked in? That's how Apple's iOS system prevents you from installing 3rd party apps even if you have the files for what you want to download. I feel like I heard that the other OSes also use that too. We would need to have a source, but I feel like this should be a major element of the article if so. It can then be tied in to the app store restrictions and other limitations that are put in place by software products. A large reason these companies can get away with murder when it comes to enshittification is because they own a monopoly on interoperable software, since all their services are locked down with DRM. I feel the article should be written to reflect that. [[User:Riverpunk|Riverpunk]] ([[User talk:Riverpunk|talk]]) 05:58, 17 August 2025 (UTC)
I haven't done the proper research on this, but don't most OSes come with DRM baked in? That's how Apple's iOS system prevents you from installing 3rd party apps even if you have the files for what you want to download. I feel like I heard that the other OSes also use that too. We would need to have a source, but I feel like this should be a major element of the article if so. It can then be tied in to the app store restrictions and other limitations that are put in place by software products. A large reason these companies can get away with murder when it comes to enshittification is because they own a monopoly on interoperable software, since all their services are locked down with DRM. I feel the article should be written to reflect that. [[User:Riverpunk|Riverpunk]] ([[User talk:Riverpunk|talk]]) 05:58, 17 August 2025 (UTC)
:Engineering-wise an effective DRM has to span not just the software, but hardware as well. Because if you can install DRM-compatible software on hardware with sufficiently open interfaces that circumvent the restrictions, that defeats the purpose of the DRM..
:I don't believe this is the case on more open platforms such as PC and Android. More specifically, I've heard stories of mixed effectiveness of Google's Widevine DRM on Android, but I'd need further research to say anything more definitive.
:I like the monopoly angle though. I've thought before about describing the manufacturers of DRM-infested devices as ''cartels'' in function: a DRM that is sufficiently widespread in content distribution necessitates that new device manufacturers in the same space need to enter into a partnership with the vendor of the respective DRM. And this does not smell like market competition. [[User:D-side|D-side]] ([[User talk:D-side|talk]]) 17:40, 8 March 2026 (UTC)


==Louis Rossmann and different names for DRM==
==Louis Rossmann and different names for DRM==
Line 15: Line 19:


:I think if one can find good citations for these alternative names for DRM, that'll also provide an angle for how they might be incorporated into the article. E. g. access controls and technological [protection] measures are mentioned in DMCA Section 1201 — suggesting a good place for those would be in a section about the legal framework around it. [[User:D-side|D-side]] ([[User talk:D-side|talk]]) 17:23, 8 March 2026 (UTC)
:I think if one can find good citations for these alternative names for DRM, that'll also provide an angle for how they might be incorporated into the article. E. g. access controls and technological [protection] measures are mentioned in DMCA Section 1201 — suggesting a good place for those would be in a section about the legal framework around it. [[User:D-side|D-side]] ([[User talk:D-side|talk]]) 17:23, 8 March 2026 (UTC)
== XKCD #129 ==
The [https://xkcd.com/129/ "Content Protection" xkcd #129] just begs for a reference to concisely showcase the absurdity of the extent to which DRMs permeate the consumer media playback landscape, but I'm honestly not sure how to do this properly [[User:D-side|D-side]] ([[User talk:D-side|talk]]) 02:54, 9 March 2026 (UTC)