@arcinternet Uhmmmm. You are taking away the first and last working browser on my mac? (I have Intel mac today)
I beg you add Intel Mac support to Dia and i move! 🙏🙏🙏
@BetaProfiles I think this compartment was very necessary, especially for the Plus and Max series of phones, since they have a huge screen and sometimes it is not convenient to reach some elements with your hands, especially if the user has small hands.
@phillymike223@maltsakas@FFmpeg@IloveRockchip From that perspective, the harm looks exactly like ‘FFmpeg/OSS dropped support for my hardware’, even if on paper it is Rockchip’s fault.
@phillymike223@maltsakas@FFmpeg@IloveRockchip For them this used to be something that ‘just installed’ via their distro or a simple guide, and now it suddenly breaks or disappears.
@phillymike223@maltsakas@FFmpeg@IloveRockchip That’s exactly the problem: if the only “move” you see is a takedown that degrades UX and codecs for users while the vendor quietly adapts, the enforcement toolbox is way too narrow. Rockchip’s silence is bad, but it doesn’t automatically make every reaction good for OSS users
@phillymike223@maltsakas@FFmpeg@IloveRockchip Most people just see “things stopped working / got worse after some legal drama around FFmpeg”, not a clean chain of warnings and takedowns. If what they experience is degraded codecs and UX while Rockchip mostly moves on, it’s hard to call that a clear win for OSS users.
@phillymike223@maltsakas@FFmpeg@IloveRockchip Yes, that was my point: Rockchip’s behavior is obviously bad for OSS users. But you’re oversimplifying how the “user perspective” actually looks.
@phillymike223@maltsakas@FFmpeg@IloveRockchip Maybe. But from a user’s perspective, “FFmpeg broke my codecs after a DMCA fight” doesn’t exactly look like a win either. If the outcome is worse UX and broken codecs while Rockchip quietly moves on, that’s not protecting OSS users, that’s just sharing the blame.