this post was submitted on 27 Dec 2025
135 points (98.6% liked)

Technology

78002 readers
2694 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
top 13 comments
sorted by: hot top controversial new old
[–] CaptainBasculin@lemmy.bascul.in 55 points 23 hours ago* (last edited 23 hours ago) (4 children)

How do you even manage to break LGPL lmao all it asks for is attribution

[–] otter@lemmy.ca 86 points 22 hours ago (1 children)

Relevant bit

The DMCA filing states that several files in the Rockchip MPP repository are derived from FFmpeg’s libavcodec sources. It lists AV1, H.265, and VP9 decoder files, and claims the copied code is clear because of matching structure, comments, and commented-out calls to FFmpeg functions with their original names.

Much of FFmpeg, including libavcodec, uses the GNU Lesser General Public License version 2.1. This license allows reuse, but only if certain rules are followed. These rules include keeping copyright notices, giving proper credit, and ensuring any shared code remains under an LGPL-compatible license.

The DMCA notice says Rockchip broke these rules by removing the original copyright and author details, claiming the copied code as their own, and sharing it under the Apache license, which does not meet LGPL requirements here.

[–] avidamoeba@lemmy.ca 12 points 15 hours ago* (last edited 15 hours ago) (1 children)

Sounds like something they should easily be able to comply with. If the relevant ticket in their internal issue tracker is given priority. 😅

[–] michaelmrose@lemmy.world 6 points 12 hours ago

Maybe. They cut and pasted the other guys stuff who knows what other stuff is there

[–] Goodlucksil@lemmy.dbzer0.com 21 points 22 hours ago

They're Chinese, they ain't bothering to read and change the License (especially if they don't have many english-speaking devs)

[–] michaelmrose@lemmy.world 6 points 13 hours ago

Cut and paste source code into your repo, which you can do, then offer the whole thing under apache which you cannot do.

[–] markz@suppo.fi 2 points 23 hours ago* (last edited 23 hours ago)

I didn't look into how the code is used, but LGPL can still easily get an entire project.

[–] punrca@piefed.world 32 points 20 hours ago (1 children)
[–] frongt@lemmy.zip 13 points 19 hours ago

And all those licenses rely on copyright and IP law.

[–] zurohki@aussie.zone 22 points 21 hours ago (1 children)

I just wish each video decoder manufacturer didn't feel the need to create their own API that isn't supported by anything.

[–] whaleross@lemmy.world 2 points 2 hours ago

It feels counter productive when everyone relies on ffmpeg and there are no proprietary secrets left to protect. Just agree on an open standard that saves time and effort for all companies using it while getting tons of goodwill and positive cosmic vibes and maybe even revenue.