For now PyLova still 'identifies' as PieFed, as PieFed is coded to only accept certain features from other 'PieFed' listed instances. So if I change it over to PyLova, it would lose all compatibility with other PF instances for things like polls or events. In the future as the project grows and diverges more, I'll look into making the fork harder.
As for the CoC it's hosted on dbzer0, I can't help you with that but if you ask in their Matrix chat they may be able to diagnose why you're hitting the honeypot.
As for quokk.au's stance on copyright, it's anti-copyright but I also do not want to be hosting or directly linking to pirated/illegal content (i.e. torrents) so as to not invite potential issues.
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.
Understandable. It's not super high priority, but I'll look at adding in the next update some sort of selector in the user profile for showing say current view, up/downvotes, or percentage views?
I’m not sure if I would want to publicly show who downvoted what, although I could certainly consider making this an optional toggle for admins as I know mbin instances already show this data.
Or are you referring to this?
I haven’t had any issues with this being janky, but I could certainly look into it further if that’s what’s causing issues?
None, they put them into a carton.