PieFed Meta

355 readers

1 users here now

Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.

Wiki

founded 10 months ago

there is something wrong with federation of posts (piefed.social)

submitted 4 weeks ago by OpenStars@piefed.social to c/piefed_meta@piefed.social

10 comments fedilink hide all child comments

See e.g. https://piefed.social/communities?search=forward - there are 2 communities listed there, both go to the same place if you click them, and that place has no posts from the last 3 days.

It almost looks like the existence of the second version of that community - changed mere seconds ago at the time of my writing this, except again, when you click the link it doesn't show anything new for several days - is soaking up all the new posts, but since it is inaccessible by the normal means those new entities cannot be accessed.

This is my favorite spot in the Fediverse, so I hope it is addressed soon! That community in particular is doing great work to make the Fediverse fun & welcoming to come to by all us nerds:-).

you are viewing a single comment's thread
view the rest of the comments

[–] andrew_s@piefed.social 2 points 4 weeks ago (1 children)

Shit, yeah. I think you're exactly right.

There's one community, with ID 870, that's in a Topic, but if you look at the host community's most recent post - at https://piefed.social/post/301064 - that's not in that first community (I don't know the ID, but I can see that it's not in a Topic). I don't know how the find the second community just using the website, because https://piefed.social/c/tenforward@lemmy.world only ever gets the first one, that stopped updating 3 days ago.

It might be that there's a call to 'find_or_create' where 'create_if_not_found' needs to be specified, because it's not being found for some reason.

[–] OpenStars@piefed.social 1 points 4 weeks ago (1 children)

I'm not sure what you mean by the latter - b/c in this case the community definitely exists, so "creating" it if the ID were to ever not be found would lead to... well, it could have lead to exactly something like this, actually? Also, would you really want to pull in posts from a community that doesn't already exist on a PieFed instance? Why even, especially if nobody has asked for it? So maybe instead of find_or_create, just a find_or_ignore?

But I have zero experience with ActivityPub, federation, or even much threaded-style programming, so I will leave such to you experts to puzzle out the actual solution!:-)

[–] andrew_s@piefed.social 2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

so "creating" it if the ID were to ever not be found would lead to... well, it could have lead to exactly something like this, actually?

Yeah. It's just one theory as to what's happened - something like a 'delete post in this community' has come in, and PieFed hasn't been able to find the community, so it's happily created a new one. I don't know why it would be able to find the community, but I'll look into preventing this kind of occurrence.

It might not be what's actually happened here: it's something for Rimu to solve really (he has direct access to everything). Edit: ignore me, he's just answered, lol.

[–] OpenStars@piefed.social 1 points 4 weeks ago

He's so fast!:-)