It will show up automatically if you meet some conditions (which you won't until 1.2 is deployed):
I don't know all the details as this is something rimu coded up, but I suspect that your instance would then be listed as a choice for any other piefed instances that have the instance chooser enabled and that you are federated with.
This snippet worked for me when I just tested it:
.post_teaser_image_preview a {
max-height: unset;
}
Basically, any css rules in your custom css overwrite the rules specified elsewhere.
Edit: I just wanted to add why the max-height was set initially. This is the codeberg issue that caused there to be a limit. Basically, without setting a max-height, really tall and skinny images can take up a huge amount of vertical space.
Just wanted to ping @rmayayo@lemmy.world to let you know about these tweaks since I know you are using the 1.1 version of this endpoint (I think Boost is the only app I saw using feeds, but I can't claim to have tested all of them).
I actually kind of like it being a separate endpoint, so I don't mind that. One thing I thought about changing though, that I opted not to, was to make both /ban and /unban the same request method. Right now /ban is a post while /unban is a put. I feel like they should both be the same. However, this felt like more of a bigger change than some field name tweaking, so I held off.
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!
Either in this thread or simply by pm works. The blahaj admins have been helpful in trying to debug this, so the most useful thing for me would be the number that is in that url that goes nowhere, 15179 in your example. That is the id of the notification that lets me get more info about it from them.
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.
Again, pinging @rmayayo@lemmy.world to let you know about these tweaks since I believe you are using the 1.1 version of this endpoint.