@snacks Doesn't seem like it, but Netzsphaere isn't in the federated instance list. Looks like the same bug I have with MKAB, where posts get to me only when I force fetch them, or someone reacts to them in some way. Probably a Sharkey thing. image.png
@Suiseiseki@snacks Basically all pisskey forks removed that API from the public. Sharkey doesn't show the "blocked" instances as a filter in the /instance-info route and Iceshrimp removed the federation tab completely (probably only for unauth access). There's basically no way to tell without looking at the logs which might have some error usually related to signed fetch (I know Mastodong does that, put I have no idea about *key).
@meso@snacks I don't really know. The last request was 9 minutes ago (as can be seen in the screenshot). But also the latest change was 9 minutes ago, so that might be the time of block.
What's weird is that there are apparently zero users anybody from Netzsphaere follows and nobody from TFS follows a Netzsphaere user. That's certainly strange.
@meso@snacks Or, it could be that the last request was 9 months ago, which doesn't really check out. <time>m should be minutes, but unmodified misskey has "min" to denote minutes.
@snacks@meso It's also looks like the dates and time are lies. They don't represent reality. Ignore the newest post, I've fetched that one through IEx manually.
Try running pleroma_ctl remote or whatever is the right command to get into IEx and run this command Pleroma.Object.Fetcher.fetch_object_from_id("https://transfem.social/notes/a2yvk641e0s800mg") It should spew out tons of debug output and end with {:ok, %Pleroma.Object{...}}.
If you are blocked and they have signed fetch enabled (probably do), you should get something like {:fetch, {:error, :forbidden}}. At least that's what Mastodon gives out.
If you can force fetch the objects, their federation is just broken in true Sharkey fashion.