wjs018

Piefed version != api version. The api is still listed as alpha and uses alpha endpoints, so changes are to be expected on that front. For the past couple of weeks, we have been making posts to [email protected] about changes coming in 1.2 as we have been working through them.

The devs have been really responsive as well. If I am honest, I expected a lot more problems than what has appeared in the wake of the changes. This release included a huge overhaul to the api to help make it more stable for the future, and as part of that included quite a number of changes where things were really inconsistent before. There shouldn’t be breaking changes like are in this release going forward as we are working from a much more solid foundation now.

Piefed doesn’t currently natively support setting up an rss feed to populate a community (though there is an issue for it on the codeberg, so hopefully soon). However, we do have an api at this point that is feature complete enough to cook something like this up without too much trouble.

As for self-hosting piefed, it is pretty comparable to lemmy. They both are dockerized and I have a personal instance of both of them. Resource-wise, for a personal instance, I haven’t really noticed a difference, though my VMs are well enough provisioned that I doubt I would run into any bottlenecks for a 1-user instance.

I’m more familiar with the Python ecosystem than Rust

This is basically how I have ended up becoming a piefed contributor. There were features that weren’t in lemmy that I was frustrated by, but don’t know a thing about rust. So, I just started implementing things in python…and have just kept doing it.

Going to the communities page and clicking the “Joined” button gives you a big list of the communities you are subscribed to and a convenient button to allow you to unsubscribe from each.

direct link

That notification url is only going to work for you because it’s your notification, other users are going to be blocked.

As for why this is happening for threads with a large number of comments, it is probably because once a post gets more than a certain number of comments, piefed loads them “lazily”. This means it loads the rest of the page first and then loads the comments and fills them in. So, the page isn’t automatically scrolled to the correct comment when the page loads because the comment isn’t there yet.

I haven’t really looked at this area of the code, but I suspect the solution will have to be some Javascript that triggers the scroll after the comment has loaded. @[email protected] probably knows better though since he wrote the lazy loading.

It will show up automatically if you meet some conditions (which you won’t until 1.2 is deployed):

1. Running version 1.2 that has the code for the instance chooser (or maybe a custom build like piefed.fan must be)
2. Enable the instance chooser in the admin settings

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.

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:

Yeah, that should work then. I haven’t really looked at that portion of the code, but I can try to take a peek.

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).

Do you mean on the bar with the voting buttons instead of being behind the three dots menu?

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.

This is actually a known issue: https://codeberg.org/rimu/pyfedi/issues/1018

The basic takeaway is that you must have already enabled notifications by clicking the enable button that shows up in that box. Then, since they are enabled, the button doesn’t show up any more, so there is just an empty box left. To disable notification, you need to do that through your browser. It’s on the list to make this UI a bit clearer at some point.

Edit: This is what it looks like if you don’t have notifications enabled

Yep! Absolutely. Here is the relevant portion of the docs.

I am using R2 for my instance and I set up those environment variables in my .env file before building the docker container for the first time, and everything just worked. The specifics of different S3 providers can vary a bit. There is a special set of instructions for using Wasabi S3 for example (I think this was contributed by Jerry of feddit.online).

Specifically, from looking at the code, it counts the most recent 50 votes on posts and the most recent 50 votes on comments for the calculation.

When you don’t have too many votes cast, it doesn’t take much to cause a big swing. There is a section in the code where it doesn’t actually calculate the attitude until after 3 votes are cast, but perhaps that should be increased.