• 1 Post
  • 48 Comments
Joined 6 months ago
cake
Cake day: July 15th, 2025

help-circle
  • I haven’t had to restore from my backup in production yet, but I run two instances and just periodically rsync the mapped volumes to a backup folder. I also use S3 for my media, so it is really just the database that is critical.

    Doing dev work, when I know I am about to really fuck up my database doing an experiment, I will rsync myself a backup…blow everything up…tear down the docker stack and swap back in my database folder and it is good to go.









  • tl;dr - Very specific way that lemmy.world broke means that there is a gap in activities that isn’t going to federate

    From a brief discussion on matrix with MrKaplan, it seems like the specific way in which lemmy broke for them (only really possible at their scale), the activities that happened during that period were marked as successfully sent even though they weren’t. Going back and resending all activities from that point on could do really weird things and end up duplicating tons of posts/comments all across the fediverse, so they have opted to not do that. So, we will just have to live without those posts/comments in the wider fediverse unless you manually force federation for them.







  • Is there a software solution on the app developer level that combines like posts together?

    As mentioned in this thread already, piefed consolidates all the comments for crossposts when it detects them. As an example, you can look at this post on piefed.social. The link I shared is for the post on [email protected], but below it you can see comments from the same article posted in [email protected] as well as [email protected] in their own sections as you keep scrolling. So, problem solved, right? Well…

    One of the key phrases I used above is “when it detects them”. So, how does piefed detect crossposts? The answer is pretty simple, it basically just looks for other posts that point to the same destination url. In the example I linked, that would be the Guardian article that is being discussed. This is the same way that lemmy detects crossposts. This approach is nice and easy and computationally cheap on the database (quick), however, there is a big shortfall of this method…posts that don’t point to a url (discussion posts) can never be detected as crossposts. Lemmy offers the ability to hit the crosspost button on a discussion post and it will create a big block quote of the original post for you, but it isn’t actually recognized as a crosspost in the software.

    I don’t have a good technical solution to be able to make discussion posts (and other non-url posts, like piefed events or polls) be crossposted properly. It likely would need to be tracked in the database somehow, but it would rely on users somehow indicating that the post they are making is meant to be a crosspost. I don’t know really…

    Anyway, that is the current state of crossposts. Thanks for coming to my TED Talk.


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



  • 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


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