If I don’t call out bad behaviour it will continue. As it stands doing nothing is only harmful for PyLova who has it’s unique features copied at each step.
He exported the code as a patch, while not knowing it would make her (correctly) the author. His intention very clearly looks to be as if to use her code without bringing over the authorship. And he did do exactly that later on with copying the themes and renaming it.
So yes I believe that warrants calling out at the time he did steal the code.
I am not saying he stole the code here, I am simply saying he is jacking the new features being introduced in an effort to harm PyLova by making it not be able to stand out with unique features. These are really the only big new user facing features he is adding and it’s conveniently shortly after we do.
It is?
https://quokk.au/c/fediverse@lemmy.world/p/1237518/pylova-v0-4-1-customisation-performance-qol-bugs
https://quokk.au/c/fediverse@lemmy.world/p/1105596/pylova-v0-3-1-released-multi-image-post-support
https://quokk.au/c/fediverse@lemmy.world/p/1092867/pylova-v0-3-0-released
https://quokk.au/c/fediverse@lemmy.world/p/1077126/pylova-v0-2-2-released
Rimu is welcome to bring over PyLova code, he only needs to attribute it instead of deliberately removing the author from the work as he did last time and has been well documented in his conversation with others admitting trying to do.
I don’t want to get too off-topic here, so I’ll message you.
These are only being added straight after PyLova does it. And considering Rimu’s hostile history it’s clearly an attempt to try to ensure PyLova cannot gain traction with its own unique feature sets.
And the way they are being added is not compatible with PyLova’s methods. Which breaks Fediverse compatibility. If any software such as Lemmy were to implement it in the future they would most likely ensure compatibility with the larger userbase PieFed model.
This is the similar to Microsoft’s “Embrace, extend, and extinguish” philosophy to kill off the competition.
The fork split off 7 months ago, PyLova independently added these features weeks and months before PieFed ever did.
And it has now been confirmed that Rimu has made it non-compatible.
PyLova already had this feature, does PieFeds work with it or is it breaking Fediverse compatibility?
Funny how PieFed gets multiple images in posts, and now in-line comment editing/shared blocklists after PyLova introduces it. Does PieFed have any original ideas?
The corruption surely affects people in Ukraine by having incompetent nepo babies on the board taking up their taxes.
Some of the 11 Democrats who missedTuesday’s vote to advance the impeachment of Defense Secretary Pete Hegseth were reportedly attending an event hosted by a “front group” for the American Israel Public Affairs Committee, commonly known as AIPAC.
Not only that, they were attending an AIPAC event instead of being there to vote.
PieFed only adds those checkboxes (multiple times now) after huge complaints from users.
The dev is an authoritarian liberal who thinks the best way to run the Fediverse is their way and everyone must accept that.
If anyone wants, I’ve created a tankie blocklist.
https://quokk.au/blocklist/triad-b-gone
Msg me if you have any ideas for what else to add.
4 points on PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP in !fediverse@lemmy.world ·
You can clearly see where the project forked and any upstream contributions from Rimu basically stopped existing except for some bug fixes being bought over, of which PyLova has also contributed to PieFed with bug fixes.
image
It does not seem a silly argument to call out a larger project from copying every idea introduced into a rival fork weeks after they introduce it. Why isn’t PieFed coming up with original ideas for what to offer its users? Is the project that devoid of trajectory that it has no idea what it wants to do next.
image