The ~ symbol is how you prefix a feed in piefed. Just like you use an @ for users and a ! for communities.

More recent versions of piefed should have a much improved compact mode. I basically made the thumbnails for image posts render just like thumbnails for link posts when in compact mode. It was a pet peeve of mine too that compact mode said it was thumbnails, but it still put images on a whole separate line which made them much larger than other thumbnails.

PBZ is on 1.3.0 now, so it should be available if you want to give it another go. Just make sure that your UI option is set to compact mode. This setting is per-device, so you might need to reset it for different browsers/phone/etc.

Rust vs. python might be part of it since python is basically designed to be quick to write. However, the lemmy devs, to their credit, are extremely thorough. They make sure that any feature they implement is fully available in the UI, the API, and has tests written for it.

For piefed, we test stuff as we work on it…but there isn’t a formal test suite or anything like that. And, as evidenced by this post, many new features only show up in the web ui and may get added to the api later, time/effort depending. This is something we have been trying to get better at, adding features to both the web ui and the api at the same time, but it is more work so it goes slower.

Sunshine waits for no one!

This commit is only ~6 hours old as of my writing this. Also, this is just the first step of adding polls to the api since it allows the api to view polls, but api clients cannot yet vote in polls. That will be the next step.

This feature helps avoid reaching the block limit.

There is a block limit? I don’t think that’s right…but I haven’t looked too much at the block code other than to make it work without needing a page refresh

I’ve never used the baremetal setup, so I can’t speak to that. However, I actually agree with your points on the docker deployment. It’s something I have spoken about to some length with people in our matrix channel as well. There are a couple things that I don’t love about the current docker setup process, but just don’t know docker or linux stuff well enough to fix:

• Needing to set up external cronjobs like you mentioned
• Needing to exec into the container for initial setup
• Not having pre-built containers that we can put in a container registry to make things easier

Docs are an always evolving thing and we have been fortunate enough to have some other admins go through the setup process and provide feedback, which has helped flesh the docs out some more. However, there is always more that can be done.

In Skavau’s defense, they aren’t a programmer, but are probably one of the most active people on piefed’s chat server/matrix room as well as the codeberg repo providing ideas and feedback. So they are volunteering time that way (in addition to being site staff for piefed.social).

Some of the ideas in this post are good imo, but are currently not possible yet using the piefed api due to it being much less complete compared to lemmy’s. So, it helps us figure out prioritization on what kinds of endpoints would be useful to flesh out next.