That said, sounds like Rimu did not verify with PyLova devs whether the third party conveyed their thoughts accurately. I don’t blame him; it is a task that takes both emotional and physical efforts. Just perhaps it could have been resolved in a more beneficial way to both parties, e.g. they might have been satisfied if attribution are added to the files themselves.

4chan is a most known imageboard and detecting posts from it to delete them will have less collateral damage.

In reality 4chan is a cesspit of the worst people on the internet and a hotbed of fascism.

I think that crown goes to Xitter now. Hopefully there's detection of Xitter screenshots too. Fuck that place.

Even if you fully attribute code, some people still don't get FOSS

You, along with Dessalines, Nutomic, Ernst of Kbin, Jgrim of Sublinks, etc. have all provided alternatives to the immensely enshittified for-profit platforms, which is something really special. So thank you.

“Hey, glad you liked the theme! Could you amend the commit to include Co-authored-by: or cherry-pick the original commit so the git history reflects the author?”

The Typical Resolution: The maintainer amends the commit, adds a note to the changelog/commit message, and both projects move on.

The immature way is to accuse the downstream developer of stealing.

Coding in public like this is quite vulnerable and does require/assume good-faith engagement from others. There's a huge array of ways to exploit that vulnerability and I've seen many examples of that in the last few months.

It's been really hard.

Thank you for the effort, marvel, art, you do...

It makes sense the person got upset, but they indeed did not follow the license, considering the header/annotation missing. You did everything right from the point of the license, and considering your time you invest into the works, it makes also sense to follow the license only.

Yet, indeed, when I work at projects at jobs, or something personal, I do tend to leave references in the code as comments (if it's in the middle; or the header, if it's a start of the entire file); in the commit messages, or least pull-requests, though the latter is weaker considering the vendor custom database outsourced. These also help to track down the origin in the history, in case of required:

> /** @see https://codeberg.org/quokkau/PyLova/src/commit/deb4cb2bb9956019dd5c847de03a28d9b9ed45b5/app/community/routes.py#L1115 */

Yet, sure it may increase the source code much... hence commit messages, CHANGELOG.md, or pull-requests to just have a reference in the history of someone's invaluably marvelous life on the miraculous road!

You sure know how it all works, and this is sure not fair to call it "stealing", and especially with no private clarification prior public judgement, I believe...

You publishing this clarification on public highlights your gratitude, respect, and acknowledgement towards other people's effort even more, of course... and is sparkling appreciated...

Meanwhile, I do wish you, and everyone here, safety, stability, and peace...

Best and kind regards