It’s in the sidebar of the community when viewing the community feed. There is a link that says “Retrieve a post from the original server”.

Ah, I see what is going on. This basically requires maliciously formatted markdown that takes advantage of some placeholder text we use to protect codeblocks from getting incorrectly formatted by the markdown_to_html function. You basically stuff the markdown full of those placeholder strings so that they are incorrectly being substituted.

I will give this one some thought. I think it might make sense to have something like a short, random string tacked onto the end of the placeholder text (like I did for the footnote links to prevent id collisions).

Like others have said, votes are not backfilled the same way other content is. So, you will only ever get votes that are cast after the point in time that the content being voted on is present on your instance. Additionally, the community’s home instance won’t send new content unless there is one user from your instance subscribed to that community. So, even if you add a remote community to your instance, but then never subscribe to it, you won’t get any new content for it.

Tsukimichi: Moonlit Fantasy Vol. 11

Looks like this is the volume that goes past where season 2 of the anime ended. So, if anybody out there wants to read ahead for season 3, you would probably be able to muddle along from this point on without too much trouble. There was definitely skipped content in the anime, but nothing too vital; mostly Tsige and demiplane stuff.

A PieFed admin can disable not-logged-in users from viewing NSFW content. IIRC, this was added after the recent UK laws about NSFW content.

Yeah, I think I see the issue in the jinja template. PieFed handles some video hosting sites a bit specially to make the compatibility a bit nicer, but the blur setting was not being passed on to those special cases. I think this is a pretty simple fix.

In the meantime, if you switch to either of the compact view settings, then the videos won’t be loaded in the feed.

I don’t think so, but I wasn’t working on it. Tagging @rimu@piefed.social for awareness.

To do this, they would need to be an admin running a modified version of the software no? If that was really happening with any kind of regularity, it would surely be grounds for defederation.

In any case, if this were to become an issue, then I am sure we can change it. We have already had to change how community flair federates a few times to try to keep up with lemmy’s PRs on the feature to try to make sure it is compatible.

As a contributor to PieFed (by my count, 7 of those bullet points in rimu’s post were done by me)…there is not more to this story as this is just some rando’s perceived grievances. If there was such animosity with the lemmy devs, why would piefed.social remain federated with lemmy.ml? There are definitely ideological differences between the devs of the two platforms, but the working relationship has been cordial and I truly believe everybody involved is aligned in the goal of promoting federated alternatives to corporate social media.

In the current stable version of PieFed (which piefed.social is on), there is a button to “Leave all communities” down at the bottom of the all communities page.

If you would like to be more selective, then it is pretty quick to go to filter that list to just communities you are subscribed to, and leave a bunch from that page.

Another option is that the Interstellar app has an option to unsubscribe you from everything. That option is in the Settings -> BETA: Data Utilities -> Account Reset.

In the next version of PieFed, I moved the leave all communities button into the Edit Profile section of the site, next to the account deletion option. I also added this ability to the API to make it easier for apps to implement.

It is slightly different in PieFed compared to lemmy. On the search page there is a button labeled “Retrieve remote post” that lets you do it.

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.

It’s been an issue on the codeberg for a little while now. It is currently on the board for the next piefed version, but it has gotten bumped before. There is only so much dev time/effort to go around. However, it is on the board, so it is something we are aware of and want to make happen.

I think they are planning a couple OVAs next year. I think they are running out of source material from what I can gather, so there might not be enough left for a whole other season.

Some that I haven’t seen others suggest yet would be The Tale of The Princess Kaguya by Studio Ghibli and the recently-aired Apocalypse Hotel.

Edit: Missed the MAL link. Looks like you have already watched Princess Kaguya.

I think it was just so that the triangle lined up with how the piefed logo normally looks. Just a stylistic choice.

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 !news@lemmy.world, but below it you can see comments from the same article posted in !unitedkingdom@feddit.uk as well as !world@lemmy.world 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.

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