this post was submitted on 30 Jul 2025
705 points (95.6% liked)
Technology
73534 readers
3496 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Stenzek's feeling got hurt when DuckStation was still proper open source software and people used the software fully in accordance with its license, i.e. they distributed modifications and not all permitted modifications were the most polished ones, so he felt that they give his name a bad reputation. Again: Stenzek released DuckStation under a license that explicitly allows this.
So he rage quit open source and released new DuckStation versions under a very restrictive "source available to look but not touch" license that's so insanely restrictive, Linux distributions are not allowed to make their own packages. So they ship the old version that works just fine because PlayStation 1 emulation was figured out very long ago. Stenzek feels that they should not ship the old version (which they are fully entitled to) and instead make a special exception for his software alone to point their users to DuckStation's website where instead of acquiring the emulator from their package manager (or "app store" in case you're not familiar with that term), Linux users should take extra steps to manually download and install DuckStation.
And since users may not know about this rift, they may post bug reports and feature ideas to Stenzek, even though these bugs may have been long fixed by non-open source DuckStation.
Basically: Stenzek did not read the license he picked for his software and then got mad when people made use of provisions explicitly allowed by the license.
This should be top comment if true.
This is a great case for a “reader added context” feature for Lemmy, if it could be implemented in a decent way.
Could be a good feature to add to PieFed, which is built on Python specifically to allow more developers to have access to building extensions and plugins.
Programming language isn’t a problem as much as the mechanics of the implementation.
I mean, how does it work on Twitter? Do they have oldschool language models parse upvoted comments and automatically generate it? Basically the options are:
Involve some kind of ML model for partial automation, which is not going to go over well with Lemmy users.
Leave the UAC completely to mods, which is going to both overburden them and make power-tripping issues far worse
On old Twitter, community notes was simply a function of raising a flag for tweets that got ratio'd. This would open those tweets up for Community Notes users to submit a fact check. Then, the fact check with the highest upvotes gets displayed as the default one.
Now? Not sure. Elon is a sneaky fucker. But I do think it could be implemented as a simple comment queue that admins and moderators could set user roles to help with.
Getting ratioed isn’t an reliable indicator though (see this post).
I guess there could be a “misleading” button that triggers a Community Notes section, but complicating the UI like that could push away many participants…
Maybe there should be a button to “mark” a comment as a correction during the posts, and if it gets enough upvotes it becomes visible under the title? That could work. Some useful comments might not get properly marked, but I think many would.
One issue is Lemmy comments are typically too long to fit under a title, so the “correction” comment would need its own structure: a short correction that fits under a post title, and context that lives in the comment section.