wjs018

I think hendrik covered the basics. Plugins within piefed are pretty basic right now since there are only so many hooks that they can tap into. However, if you come up with a use case that the current set of hooks don’t allow you to do, please reach out and we can add more hooks in as the need arises.

The system itself can be extremely powerful, but similarly dangerous. Plugins have full access to the piefed database and any functions/modules in the codebase. If you want an example of a plugin that is currently being used in production (by at least two instances I know of) you could look at the onboarding plugin that I wrote.

I think the developers welcome people finding use-cases and expanding on the concept

Absolutely! It was actually an admin reaching out like this that led me to add some hooks for plugins to use and to create the onboarding plugin.

Alright, after another user pointed it out to me, I suspect the reason you aren’t seeing links to the modlog is likely because you were on piefed.world. They have been slow to update their piefed instance and are still on the 1.1 version. That means that updates to piefed that have been introduced in 1.2 (current stable version) and 1.3 (current dev version) are not present. Some updates to the modlog since then:

• (1.2) searching and filtering the modlog if you are logged in
• (1.3) introducing a dedicated link to the modlog on the footer of every page
• (1.3) adding a link to the modlog on each community’s sidebar
• (1.3) adding a link to the modlog on a user’s profile page

I just added it there a couple days ago, so don’t feel like it’s always been there hiding under your nose. 😀

piefed.world is on an older version of piefed where that wasn’t added yet. Similarly, instances that are on older versions of piefed won’t have links to the modlog on a community’s sidebar or on a user profile’s dropdown.

I’m not sure what is holding up piefed.world from updating. They are still on the 1.1 branch when 1.2 has been stable for some time now and we are preparing 1.3 for release very soon.

Without being an admin you won’t be able to see the username of the mod that banned you. This is also true for lemmy.

It is in the dropdown on their user profile page. Putting it on every single post/comment feels like overkill to me. Or, I just use the modlog way less than most people.

It’s also linked in the footer of every page.

I’m confused why you are talking talking about lemmy containers in a piefed-focused community. Piefed doesn’t separate out the web ui into a separate container by design. So the solutions and difficulty of implementing are very different.

For piefed admins out there, a simpler way to basically kill scrapers dead is to simply enable the Private instance option in the Misc tab of the admin settings. This prevents non-logged in users from browsing your instance without blocking the /inbox route for federation or the api routes.

Not the person you are replying to, but I wouldn’t call it obscure, no. It’s getting used more and more in recent years and there are pushes to even use it for parts of the Linux kernel. However, it is a language that you wouldn’t be familiar with unless you are most likely a professional software engineer (or a very dedicated hobbyist).

One of the benefits of python is its relative ease of learning and readability make the codebase easier to understand and make contributions. I don’t work in software, but I have made numerous contributions to Piefed for features that I have wanted in lemmy, but I haven’t ever been able to wrap my head around rust.

Nothing against lemmy though. Their codebase is a couple years more mature, and since they develop api-first, it is more feature complete from a mobile app’s perspective. Piefed is developed web ui-first by comparison.

Federation can be fickle sometimes. I don’t have direct db access to check what happened to this exact activity announce to mander, but the logs I do have access to are littered with mander.xyz timeouts. Something might be up on their end.

I did try to force-federate it over using the lemmy search from their end, but the only result that came up is this post asking if there is a problem. Also, for what it’s worth, I was able to force-federate it to a personal lemmy instance I use for testing just fine. So, the issue seems to be on mander’s end, but I could not begin to tell you what the issue might be as I don’t know lemmy technical details nearly as well as piefed.

@rimu@piefed.social would be able to provide more insight probably.

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 !piefed_api@piefed.social 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.

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.

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.