114
cross-posted from: https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp
New features
- Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances.
- Edit comments inline, without loading a separate page - wjs018
- Fediverse statistics at https://piefed.social/statistics
- 2-factor authentication (TOTP) - can be added to your account in the 'Security' page in your settings.
For admins
- Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting 'piefed.social' in as the instance and 'spam' as the keyword filter. It'll cut down on the work involved in running your instance SO much.
- Voting pattern graph on user profiles to help spot automated voting.
- Reset the password of any user.
- Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It's a lot to take in but the video will explain it all.
API
- edit matrix user id when saving user profile data.
- scheduled post endpoints - wjs018
Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases for details.
To upgrade from 1.8.x or earlier
git pull
git checkout v1.9.x
Then,
./deploy.sh or ./deploy-docker2.sh
Donations
PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features.
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"
Source?
You won't acknowledge it but for everyone else here's rimu saying well it's just unfortunate and their fault totally nothing I did
https://lemmy.world/comment/26882650
What do you mean I "won't acknowledge it"?
Are you defending @awesomelowlander@cozyver.se 's claim?
Ty for proving the point
I mean, I definitely proved a point.
The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don't really think so, but I can accept that too.
Are you going to share your source for your claim of "deliberately breaking compatibility"? Pretty strong claim...
There are 3 possibilities:
You seem to be conflating 'deliberate' with 'malicious'. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.
I notice you have once again failed to provide any source for your strong claim. I think at this point we can assume you made it up.
Gee, who could have predicted the exact crybullies rimu was talking about who show up to tell lies about him any time PieFed is mentioned would show up and tell lies about him!
At this point I'm not sure you even read my comment... WHAT strong claim? Would you like to take a look at my previous comment and tell me which of the 3 possibilities you think was the case?
You made the strong positive claim that rimu deliberately broke compatibility with pylova.
I've asked you twice now for your source for that claim. You've instead given me other scenarios you imagine could be the case if it wasn't true that rimu deliberately broke compatibility.
That's completely non-responsive to my question... No one asked what you imagine might have happened.
So the comment that somebody else linked an hour ago, that you replied to, direct from Rimu, isn't enough? Or are you being deliberately facetious here?
https://lemmy.world/comment/26882650
Do you understand the meaning of the word deliberate?
That comment doesn't demonstrate whatsoever that rimu "deliberately broke compatibility with pylova".
Of course I do. Do you? How about the word "break"?
Edit: Do you think deliberate means "not intentional"?
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word 'break', then? Nothing else? Why didn't you say so 4 comments ago? And not after you conclusively lost the argument on deliberate?
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Better?
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".
I'm only pointing out the optics of it aren't great. I do agree Pylova doesn't have a monopoly on a feature just because it implemented it first.
Here, let me help you reframe the miscommunication:
lemmy,{k,m}bin, et al. can implement these features pylova compatible too. Piefed refuses to compatibilize.
That's what I was addressing. According to that logic, even if Piefed supports blocklists the way Pylova does it, then it's still preventing Pylova to gain traction with its own unique featue sets.
Maybe I'm missing something.
In the case of popularity, @cobracommander@quokk.au is correct in this assessment, as Piefed refuses to acknowledge 1) pylova or 2) accredit original pylova features. I don't want to partake in that discussion.
Legally, piefed has to accredit any code it copies, which piefed devs have not done so in the patch demonstrated before. These current implementations maybe legally different. I have not compared them yet.
In libre ethics, breaking compatibility with an early implementer of a feature in a shared network maybe coincidental, or in the case CC argues, anti libre. Piefed devs are aware of this thread, and read the contents. Now it's a matter of when piefed users desire to pylova compatibilze these features. Time will tell.