And PieFed also supports blurring photos using spoiler flair instead of just relying on NSFW tags as Lemmy does.

This and || inline spoilers || were some of my early contributions to Piefed because I was so frustrated that they weren't in lemmy.

They're different and have relative strengths and weaknesses. Despite being a contributor to piefed, I moderate a handful of communities on a lemmy instance and don't really have intentions of moving them. Overall, piefed is a lot less "mature" than lemmy, which makes sense because it is a lot newer of a project. It is getting better now about being more stable, but there are plenty of things that are still changing quite rapidly, especially on the api front.

As for python/pip/typing, I just don't see this as the major issue that some people seem to think it is. We aren't adding dependencies willy-nilly and the framework in which we are working (flask) is a very mature one that has stood the test of time. The fact that python is used for the project has tremendously helped the project in that it has allowed for a large number of contributions from many different people. Frankly, if piefed wasn't in python, it would not be nearly as feature complete as it is now thanks to the wide range of contributions we have received from folks.

the mobile implementation of the website is surprisingly good

This makes me feel good. I have done quite a bit of reworking the UI to make it more friendly at mobile screen sizes. Thanks!

Add ability to use keyword filter on community names

This should already be live. In your user settings on the Blocks & Filters page, you will want to look for these options:

Since you are on piefed.social, rimu has tried to designate basically all the meme communities as "low quality" so that they are easily filterable by checking that box (new ones pop up all the time though). Additionally, the text box below lets you filter based on community name.

I'd like to sort communities by Top X amount of time, IIRC that was already in the works.

This is already live. If you are viewing a community, click Top in the bar and it should be a dropdown menu where you select the timerange:

If you are on a small mobile screen (like using the PWA), the different time options are listed out with the other sort options:

Alright...I don't have a solution for you, but I am going to try some stuff and see if I can replicate this. After talking with some of the involved admins, I don't really know the problem, but I have some leads to follow up on. I was able to confirm it is related to reports, but why you are the one getting a notification, I am not sure yet.

If this happens again, feel free to reach out.

Hmm, that is an interesting idea...

I might look into this one. Would something like voting buttons in the crosspost dropdown be an acceptable alternative? I think I would prefer to keep 1 action (click) means 1 vote, but making it easier to vote on crossposts makes sense with the way that piefed consolidates comments.

So, voting buttons here maybe? (no promises, just an idea) -

This is planned for the 1.2 release (at least it is on the kanban board).

Are you using an app or the web ui? It is still an open issue that posts are not being marked as read when they are interacted with via the api. It should work as expected if you use the web ui.

I've done a lot of work on the markdown to html edge cases. So, I think things like bold and italics intermingling and garbling each other shouldn't happen any more. If it does, feel free to let me know!

I don't think that's the issue since you can upload images for an image post. It's more the effort of doing file uploads from a dynamically inserted part of the page (the reply box). I don't know enough Javascript to be able to do that.

Not a bad suggestion. When you are browsing the /communities page for example, the leave buttons are in the warning color (yellow if you are using the default dark theme) while the join buttons are in the primary color (blue). I can try to whip up some code for this.