this post was submitted on 13 Oct 2023
12 points (100.0% liked)

Programming.dev Meta

2476 readers
1 users here now

Welcome to the Programming.Dev meta community!

This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.

Links

Credits

founded 1 year ago
MODERATORS
snowe
Ategon
12
outbound federation doesn't seem to be working right now (self.meta)
submitted 1 year ago by Die4Ever to c/meta
21 comments fedilink hide all child comments
 

I just made this post https://programming.dev/post/4307457

but it isn't showing up here https://sh.itjust.works/c/speedrun

I had a similar issue on a previous post but I didn't think much of a single failure and fixed that one myself by doing the search

https://programming.dev/post/4295735

but now I see it happening again and with a different instance I think there's something wrong

you are viewing a single comment's thread
view the rest of the comments
[–] mark 0 points 1 year ago* (last edited 1 year ago) (2 children)

IIRC, this is how it works by design. Posts don't get federated to another instance unless someone from that instance interacts with it e.g. searches for it, comments on it, etc

[–] Ategon 3 points 1 year ago* (last edited 1 year ago) (1 children)

Thats only the case for communities, not posts in an already fetched community

[–] mark 1 points 1 year ago* (last edited 1 year ago) (1 children)

What do you mean by "already fetched"? I've been on the fediverse for quite a while and I've never seen new posts from a community be automatically federated across every other instance in the fediverse without someone from those instances interacting with it (e.g. following the community, searching it, etc). Can you point me to where it says it works the way you say? Not saying you're wrong. But would be news to me.

[–] Ategon 2 points 1 year ago* (last edited 1 year ago)

That is what im saying. The thing is with that community above the community has already been interacted with (fetched) in that instance with the op having been making posts in it for a very long time and all previous posts federated. It sounded like you were saying that happens on the post level instead of the community level

Im guessing that this is a bug that got introduced with 0.18.5 since it hasnt been a problem until now

[–] Die4Ever 1 points 1 year ago

To convert the process into Mastodon terms, a community is like a dummy user, it's not like a hashtag. Making a post to a community is like doing a mention tag to it, like @communityname@instancename, so the community's home instance should always see all the posts to it. (This is the part that I noticed wasn't working)

The community boosts every post to it, so every user who is subscribed/following the community can see the posts that it boosts, which means the instances hosting the subscribers/followers will receive copies of the posts, so federation is automatic there because of the boost.