Go to https://piefed.social/user/settings/filters and check your Instance filters. You’ve blocked lemmy.ca so none of your posts in lemmy.ca communities get sent there.

I will see what we can do at the UI level to warn people about this.

Man, I am a cranky bastard sometimes. Shouldn’t post when I’m tired.

How about - the origin server, the place where the post was originally created, gets all the metadata (og:image, og:title, etc) and includes that in the Activity that tells other instances about the post? That way there is only one request made to the link and receiving instances can use that to make their preview?

It does mean that receiving instances will need to trust the sender so there’s potential for some misrepresentation but that seems acceptable to me.

I definitely did read it.

This idea is so bad that I’m not even going to bother elaborating.

This will just lead to more requests being made.

Also anonymous requests, like those done by Mastodon to generate previews should be cached at the CDN or web server level, making them inexpensive to serve.

Thanks for bringing this to my attention. There have been a couple of other similar cases in the last few days, so a pattern is forming.

There’s nothing you can do. Possibly creating a new account would solve it, if my theory about the root cause is correct. Some accounts may have corrupted data that got federated to other instances and now those instances are confused about the validity of your account. This should solve itself over time as caches expire and get refreshed but it’s been 3 days now so they should have by now. Perhaps my theory is wrong.

Anyway I’m monitoring the situation and will be doing more tests as time permits.

In Lemmy you can force a post to be federated by putting it’s url into the search. I did that on lemmy.world and how your post shows up in the community but the date is wrong:

odd.

Looks like it is back to normal now.

About an hour ago I deployed a lot of code changes and in doing so restarted everything. If something had gotten clogged up inside then that restart would have flushed it out.

on it

The sycopathy is because to make the chat bot (trained on Reddit posts, etc) to respond helpfully (instead of “well ackshually…”) and in a prosocial manner they’ve skewed it. What we’re interacting with is a very small subset of the personalities it can exhibit because a lot of them are extremely nasty or just unhelpful. To reduce the chance of them popping up to an acceptable level they’ve had to skew the weights so much that they become like this.

There’s no easy way around that, afaik.

PieFed has this in the admin area:

So admins don’t need to stay on top of the latest defederation drama, just choose who to outsource that work to. From that baseline you can add more defederations manually.

Are you using an iPhone?

Good question!

PieFed sends delete requests to every known server, including defederated ones. I’ve seen a ton of delete requests from Mastodon too, for accounts that don’t exist on PieFed so it looks like Mastodon does that too. No idea about other fedi platforms.

It is a basic feature and it does work. Except in rare cases.

You are technically correct but the fact is that 99.9% of federated activities, including delete requests, are processed normally and in the expected way. That is not “impossible to delete” that is “will be deleted except in exceptional circumstances”.

These are my thoughts https://distantprovince.by/posts/its-rude-to-show-ai-output-to-people/

503 errors are problems on the server, there’s nothing you can do at your end to change them.

I did some experimental stuff a few hours ago, you probably got caught in the middle of that. Should be ok now?

Maybe they were already banned at the instance level. I do that a lot. You can PM me their name if you’d like me to check.

Oh :)

Once per day a request is made all instances to retrieve the list of their admins. If that request fails then they’re flagged as ‘dormant’. If dormant for 5 days, flagged as ‘gone forever’ and then PieFed doesn’t try to federate with them again and all their communities have that warning on them.

If any Activity arrives from a dormant / gone instance then it’s restored to full operation.

It looks like this - https://piefed.social/c/adultswim@lemm.ee

PieFed does this.