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?
Sharing of ideas and code is a core tenant of FOSS. PyLova literally started as a copy of Piefed. Why shouldn’t the ideas and features flow both ways?
Multiple images in posts and in-line comment editing are basic features coppied from Reddit (and, like, every social media site), which probably coppied them from somewhere else. Let’s not pretend like PyLova is breaking new ground here, lmao.
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.
Do you have any context/source for “Rimu’s hostile history”? Because I’ve tried looking into that a few times but I’ve only ever found this Piefed devlog post which makes Piefed sound reasonable but obviously has every incentive to be biased.
Why shouldn’t the ideas and features flow both ways?
why doesn’t @rimu@piefed.social admit that he got the ideas from Mia then? why copy changes from PyLova, and strip attribution, then admit to MrKaplan that he did it so that she wouldn’t be attributed? moth supposes that perhaps he does not want to admit Piefed is inferior to PyLova.
Let’s not pretend like PyLova is breaking new ground here, lmao.
no, but PyLova IS doing most of the dev work for Piefed.
according to the PyLova devs, it was forked to remove the hard-coded (at that time) censorship in Piefed, especially the anti-memes censor and upvote punishment. memes are a valued and culturally important form of self-expression, and even if the Piefed author is from an older generation, it doesn’t mean those memes should have to swim upriver just to get the same engagement on Piefed as they do on Lemmy.
that’s a good idea, thank you! moth thinks marriage is an outdated concept, but moth might find it agreeable if it’s to the best threadiverse software currently available!
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.
Is Mia supposed to patent Pylova features, and prevent any other Fediverse software to use them, be it Lemmy or Mbin? Serious question, as otherwise I don’t see how this can be solved.
Features have always been replicated between software, even beyond the Fediverse.
This is a different question. The comment above is advocating for “Piefed to stop copying Pylova features”, you are speaking about compatibility, which I guess would also be criticized for “copying the feature”.
Because it’s your opinion and I haven’t seen Rimu do anything in this community that breaks the rules.
My parents gave me some advice early on in life, maybe you should hear it too.
If you can’t say something nice, don’t say anything at all.
There are numerous places on Lemmy that will happily let you say far meaner or disrespectful things about whoever you’d like (myself included). That’s not how I run this community though.
Then im seeing piefed code pulled into pylova as soon as Nov 5th. Last week.
It looks more like pylova is pulling from piefed rather than the other way around. I mean this is what open source is for. But it sure looks like rimu did most of the work when you look at: https://codeberg.org/quokkau/PyLova/activity/contributors
By a HUGE factor.
It also looks like piefed has much more active development. So this seems like a silly argument to have by a long shot.
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.
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.
Maybe it’s because the PyLova maintainers refuse to let their code be contributed back, loosing their shit and accusing Rimu of stealing instead of contributing their code back.
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.
Did he really though? For the main code including the patch file should have preserved the author for the commit, right? As is shown in the blog post. Honestly that is enough to meet the license requirements. I guess you could argue that he skipped it for the themes, but really? Do you still think that warrants the narrative that they’re stealing code? (Which is a fucking rich statement for a fork to accuse the source project of anyway)
It would also have been nice to shoutout in the release notes as well, but we never got to see that because of the drama.
the PyLova maintainers refuse to let their code be contributed back
as soon as the fork was made, were the PyLova devs not banned from all Piefed channels? was the first security patch authored by the PyLova devs not ignored by @rimu@piefed.social, despite attempts to reach out so that Piefed could take advantage? tell moth, how long should the PyLova devs continue reaching out, only to have Rimu push them away? why do you have this double-standard?
all attempts to reach out to Rimu are shot down by Rimu and the persons blocked or banned from Piefed channels, so moth isn’t sure how things will get “figured out”.
Yeah that means PyLova copied a lot of features from PieFed lol, that’s how forking works.
Yes and forks give attribution. They essentially say, “this is a fork of this other program. It is made with a lot of the other program’s code. We wouldn’t exist in our current state without using the original codebase as a starting point.”
Whereas Rimu has a history of behavior which shows his thoughts are more along the lines of: “This is mine. Someone else came up with the idea and wrote it, but their contributions aren’t contributions because I don’t like them and so they don’t deserve credit.”
It wouldn’t be so bad if Rimu had actually copied the code, which would then be compatible. Or even implement his own code in a compatible way, if attributing PyLova’s devs is such a taboo for him. But he chose to implement a non compatible feature, fomenting fragmentation and a worse user experience. And for what?
Comments
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?
Sharing of ideas and code is a core tenant of FOSS. PyLova literally started as a copy of Piefed. Why shouldn’t the ideas and features flow both ways?
Multiple images in posts and in-line comment editing are basic features coppied from Reddit (and, like, every social media site), which probably coppied them from somewhere else. Let’s not pretend like PyLova is breaking new ground here, lmao.
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.
Do you have any context/source for “Rimu’s hostile history”? Because I’ve tried looking into that a few times but I’ve only ever found this Piefed devlog post which makes Piefed sound reasonable but obviously has every incentive to be biased.
I don’t want to get too off-topic here, so I’ll message you.
May as well start with rimu flat out attacking everyone associated with it again
Hey, I’m not familiar with either implementation - how does PyLova do it? And how does PieFed do it?
why doesn’t @rimu@piefed.social admit that he got the ideas from Mia then? why copy changes from PyLova, and strip attribution, then admit to MrKaplan that he did it so that she wouldn’t be attributed? moth supposes that perhaps he does not want to admit Piefed is inferior to PyLova.
no, but PyLova IS doing most of the dev work for Piefed.
How come pylova isn’t publishing these updates here too?
It is?
https://quokk.au/c/fediverse@lemmy.world/p/1281812/pylova-v0-5-0-shareable-blocklists-roles-ui-changes
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/1214229/pylova-v0-4-0-moderation-community-management-tools-galore
https://quokk.au/c/fediverse@lemmy.world/p/1135278/pylova-v0-3-2-released-muffles-reels-flags-bookmarks-and-more
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
Interesting. Either I scrolled past it or didn’t know what it was and ignored it.
Is there any history on why it was forked? Could be useful to add to the repo.
according to the PyLova devs, it was forked to remove the hard-coded (at that time) censorship in Piefed, especially the anti-memes censor and upvote punishment. memes are a valued and culturally important form of self-expression, and even if the Piefed author is from an older generation, it doesn’t mean those memes should have to swim upriver just to get the same engagement on Piefed as they do on Lemmy.
If you love pylova so much why don’t you just marry it?
that’s a good idea, thank you! moth thinks marriage is an outdated concept, but moth might find it agreeable if it’s to the best threadiverse software currently available!
I use both, starting another flamewar doesn’t seem positive for either project.
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.
Is Mia supposed to patent Pylova features, and prevent any other Fediverse software to use them, be it Lemmy or Mbin? Serious question, as otherwise I don’t see how this can be solved.
Features have always been replicated between software, even beyond the Fediverse.
You have to admit, deliberately breaking compatibility with Pylova’s identical blocklist feature isn’t the best look though.
lol nothing Rimu does is “a good look”
This is a different question. The comment above is advocating for “Piefed to stop copying Pylova features”, you are speaking about compatibility, which I guess would also be criticized for “copying the feature”.
Source?
Rimu is here making it worse fyi
Please be respectful. Personal attacks aren’t appropriate for this community.
How is describing what they are doing in the thread an attack?
Because it’s your opinion and I haven’t seen Rimu do anything in this community that breaks the rules.
My parents gave me some advice early on in life, maybe you should hear it too.
If you can’t say something nice, don’t say anything at all.
There are numerous places on Lemmy that will happily let you say far meaner or disrespectful things about whoever you’d like (myself included). That’s not how I run this community though.
We are so small haha. Its so silly.
Definitely x)
Its a fork isn’t it? So like 95℅ of the codes the same.
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.
I’ll take a look later. It should have a tiny bit my code in there.
EDIT: So I took a look. If this is the repo:
https://codeberg.org/quokkau/PyLova
Then im seeing piefed code pulled into pylova as soon as Nov 5th. Last week.
It looks more like pylova is pulling from piefed rather than the other way around. I mean this is what open source is for. But it sure looks like rimu did most of the work when you look at: https://codeberg.org/quokkau/PyLova/activity/contributors
By a HUGE factor.
It also looks like piefed has much more active development. So this seems like a silly argument to have by a long shot.
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
Thank you for having a look
Pylova is built 50% on piefed, 50% on a complete misunderstanding of what open source software is.
Maybe it’s because the PyLova maintainers refuse to let their code be contributed back, loosing their shit and accusing Rimu of stealing instead of contributing their code back.
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.
Did he really though? For the main code including the patch file should have preserved the author for the commit, right? As is shown in the blog post. Honestly that is enough to meet the license requirements. I guess you could argue that he skipped it for the themes, but really? Do you still think that warrants the narrative that they’re stealing code? (Which is a fucking rich statement for a fork to accuse the source project of anyway)
It would also have been nice to shoutout in the release notes as well, but we never got to see that because of the drama.
as soon as the fork was made, were the PyLova devs not banned from all Piefed channels? was the first security patch authored by the PyLova devs not ignored by @rimu@piefed.social, despite attempts to reach out so that Piefed could take advantage? tell moth, how long should the PyLova devs continue reaching out, only to have Rimu push them away? why do you have this double-standard?
Yeah that means PyLova copied a lot of features from PieFed lol, that’s how forking works.
It does suck if it’s not all compatible though, I hope that gets figured out
all attempts to reach out to Rimu are shot down by Rimu and the persons blocked or banned from Piefed channels, so moth isn’t sure how things will get “figured out”.
Becareful this will get called a attack
Yes and forks give attribution. They essentially say, “this is a fork of this other program. It is made with a lot of the other program’s code. We wouldn’t exist in our current state without using the original codebase as a starting point.”
Whereas Rimu has a history of behavior which shows his thoughts are more along the lines of: “This is mine. Someone else came up with the idea and wrote it, but their contributions aren’t contributions because I don’t like them and so they don’t deserve credit.”
It wouldn’t be so bad if Rimu had actually copied the code, which would then be compatible. Or even implement his own code in a compatible way, if attributing PyLova’s devs is such a taboo for him. But he chose to implement a non compatible feature, fomenting fragmentation and a worse user experience. And for what?
Sign in to comment. Sign in