
PyLova (Python+Pavlova) is a soft fork of PieFed, aimed at improving the user experience through UI overhauls, empowering users and admins with agency, improved administration and moderation functions, and general bug fixing.
New in V0.3.0
For Users
- New ‘Look & Feel’ tab in settings, for customising your user experience.
- In comment video uploading and posting (counts towards files quota).
- Updated ‘Files’ page, allowing mass deletion of uploaded media.
For Moderators
- Can set default tags for communities, that auto-fill into new posts on community. Enabling greater discover-ability across the Fediverse.
For Admins
- New ‘Look & Feel’ tab in settings, to help with managing the visual style of your instance.
- Ability to view a users deleted posts and downvotes alongside their upvotes.
- New ‘Rules’ sidebar panel to display instance rules.
And More
- Themes can support sub-colour schemes.
- New User setup page is condensed into one, offering options for setting pronouns and bio.
- Alt text (aria label) for video uploads.
- Consistent markdown editor.
- Musk/Trump filter reworked to a ‘low politics’ filter.
- Hard-coded musk/trump filter removed for users who are not signed in.
- Thanks to @Dialectical_Specialist@quokk.au, Lichess boards are supported to display.
- Updated documentation by @quill7513@anarchist.nexus.
- Updated docker example by @tenchiken@anarchist.nexus.
- Visual changes to posts, tags displayed under title and titles now serve as hyperlink.
- Fix with API, images posts no longer upload against image quota and send as image type posts enabling to display correctly on Lemmy.
- Collapse-able sidebar cards.
- Sorting (hot/new/local/all) is managed by drop-downs to maintain consistency.
- Removal of ‘Rational Discourse’ sidebar.
- Minor fixes & changes.


The Lemmy method sounds pretty simple to add. I’ve put it on my to-do list for the next release, so I’ll probably do it over the weekend.
On the second half, it’s a complex issue. From what I’ve seen the majority of Threadiverse users are extremely against seeing this information and feel like it can lead to I guess … revenge against users who downvote. But like your example shows, there can be harm in those sort of mass-downvoters. I originally started with Kbin myself, so I don’t mind the option myself but I am also wanting this to cater to a broader userbase, and the general consensus I’ve seen is ‘don’t make it public’. I’ll have to give this some greater thought before I touch it sorry.
The Lemmy way: yay!
The second half: yes I understand and agree - it’s a rather complicated issue, which can go both ways. Perhaps it can be something left to the admin to decide whether to enable vs. not? They can see all votes themselves in any case. In general I am not a fan of restricting people’s abilities “for their own good”, which seems in line with the spirit of PyLova, but in any case I definitely understand that it needs thinking about first bc it does run against the grain of what PieFed has done so far.
Thanks for talking about it with me.:-)