this post was submitted on 17 Sep 2025
433 points (99.5% liked)

Technology

75233 readers
2964 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

Should OS makers, like Microsoft, be legally required to provide 15 years of security updates?

you are viewing a single comment's thread
view the rest of the comments
[–] JustARaccoon@lemmy.world 2 points 21 hours ago (8 children)

I think I'd prefer if there was a minimum updates guarantee that OS sellers would have to disclose, but even then I'm more in favour of other companies being able to pick up the work by making sure devices have their bootloader unlockable after they don't get any more updates for X amount of time, rather than add burden to OS makers, because forcing people to support a project for Y amount of years would really harm indie developers releasing Linux distros and the like

[–] Buffalox@lemmy.world 1 points 19 hours ago (7 children)

rather than add burden to OS makers

It's not a burden for the OS maker, except when the OS is the product, and in that case it's only fair.
With Android the phone maker adapt the OS to their phones and flavor of Android, if they can't handle maintaining it, they can use vanilla. Google is the OS maker, and I think they can handle the burden.

[–] ell1e@leminal.space 1 points 19 hours ago* (last edited 19 hours ago) (6 children)

The EU has been so far bad at making sure FOSS isn't seen as a paid product in the eyes of regulation, even in cases where it's clearly unpaid, see here. They can't be trusted to get this differentiation right.

Therefore, unlockable bootloader seems like the better idea. Get people to Linux and open Android variants if the closed-source companies won't serve them.

[–] Buffalox@lemmy.world 2 points 18 hours ago* (last edited 18 hours ago) (1 children)

I have no idea what I'm supposed to see from you link? I don't see any particular legal knowledge, or description of any particular legal consequences, and I have no idea what the point is???
Obviously software provided for free "as is", cannot be required to be maintained. And if it is owned by the public which is the case with FOSS, there is no "owner" who can be made responsible.

If however the software is part of a commercial package, the one supplying the package has responsibility for the package supplied, you can't just supply open source software as part of a commercial product, and waive all responsibility for your product in that regard.

[–] ell1e@leminal.space 1 points 16 hours ago* (last edited 16 hours ago) (1 children)

I admit it's a complex topic, but if you read the post in detail, it should answer your questions. The "owner" is typically the maintainer, if in doubt that's the person with repository write access. And the EU can apparently potentially require whatever to be maintained, not that I understand the exact details. The point was that the regulation doesn't seem to avoid FOSS fallout well.

[–] Buffalox@lemmy.world 2 points 16 hours ago (1 children)

“owner” is typically the maintainer,

Nope, AFAIK that is not legally applicable, that is very clear with licenses like MIT BSD etc, and for GPL in all versions it's very explicitly stated in the license.
You can also release as simply public domain, which very obviously means nobody owns as it is owned by everybody.
Generally if you give something away for free, you can't be claimed to be the owner.
I have no idea where that idea should come from, some typical anti EU alarmists maybe? And I bet there is zero legal precedent for that. And I seriously doubt any lawyer would support your claim.

If however you choose a license where the creator keeps ownership it may be different, but then it's not FOSS.

[–] ell1e@leminal.space 1 points 52 minutes ago* (last edited 37 minutes ago) (1 children)

As far as I understand the license doesn't matter at all for EU regulation, other than "non-free" software is treated even worse.

Generally if you give something away for free, you can’t be claimed to be the owner.

The CRA from what I can tell applies to software given away for free, sadly. I'm not a lawyer, though. But you can perhaps see why people don't trust the EU.

[–] Buffalox@lemmy.world 1 points 46 minutes ago (1 children)

If it's proprietary it doesn't, between proprietary and FOSS it absolutely does for the reasons I already stated.

[–] ell1e@leminal.space 1 points 33 minutes ago* (last edited 33 minutes ago)

https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ%3AL_202402847

Supply in the course of a commercial activity might be characterised not only by charging a price for a product with digital elements, but also by charging a price for technical support services where this does not serve only the recuperation of actual costs, by an intention to monetise, for instance by providing a software platform through which the manufacturer monetises other services, by requiring as a condition for use the processing of personal data for reasons other than exclusively for improving the security, compatibility or interoperability of the software, or by accepting donations exceeding the costs associated with the design, development and provision of a product with digital elements

TL;DR, just donations can already be a problem, apparently. But IANAL.

load more comments (4 replies)
load more comments (4 replies)
load more comments (4 replies)