update, got it to work by sending a different link and then editing the post: https://lemmy.blahaj.zone/post/18184598
This post:
https://lemmy.blahaj.zone/post/18177512
with this url:
Doesn’t seem to federate. I’ve posted, waited, deleted and reposted multiple times. I’ve checked lemmy.world and beehaw and it never showed up. The original got one upvote so someone on Blahaj could see it. I’m curious if anyone has run into this problem before and how it was fixed.
Other comments and posts I’ve been doing have been federating, but specifically not this one. They usually take less than a minute maybe a couple more to federate. Since it wouldn’t show on two different instances, after waiting, I would assume it has something to do with our instance, but it could just be a me problem.
I would appreciate it if someone else could try. Thank you.
Maybe users from blahaj.zone can see it and upvote? I had the same problem with 2 articles last week.
Yeah, it goes to our instance first. But then it’s supposed to be sent to the other instances we are federated with too. When I go to those instances’ web addresses, not via Blahaj, I don’t see the article.
It’s good to know someone else had this problem though. It happened to me once before, but reposting fixed the issue so I think that case was just lag. edit: typos
Other posts with different links work, just not this link. =/
I finally got it to federate. I had to post an article for CNN and then edit to post it to what I wanted. This is the link I used and then switched out:
https://www.cnn.com/2022/11/05/health/daylight-saving-time-explainer-wellness/index.html
I also tried these, but they had the same problem and wouldn’t federate: https://www.usnews.com/news/elections https://projects.fivethirtyeight.com/2024-election-forecast/
If anyone has an explanation for this I would be very interested to hear it. Are there exclude/include lists for certain websites on certain communities?
I guess it wasn’t a me problem or a blahaj problem, but it’s weird that two different politics communities on different instances had the same problem.
it may be related to the older lemmy version.
the latest lemmy version has changed how metadata is fetched for posts coming from federation and it will no longer be processed while receiving the federated activity, instead it will be processed in the background. sometimes, metadata for urls cannot be fetched within the time limit and then the post will not federate properly if it’s not happening in the background.
Is there a different put route for updating where the meta data is processed differently or given a longer timer? Because the federation seems to work fine in that case.