hi @julian , I wonder how search engines and SEO will work for federated posts? Let's say I published a post specific to forum-1 on forum-1, however since it is federated out, the same posts and topic can be found on 10+ more websites simultaneously... and let's assume forum-2 is higher ranked on search engines for some reasons...
when people are searching related keywords on search engines, will they be directed to forum-1? or forum-2, namely the forum that search engine favors/ranked higher?
@crazycells That's a good question, and not one I'm sure I have the answer for.
It's something I wonder about because it has been said that search engines will penalize sites that contain repetitive content. Does that mean we may see downweighting because federated content can be found word-for-word elsewhere? I don't know.
I think what might be a good practice would be for a site to refer back to the original site if available.
For example, if you inspect the source for this topic, you'll see that it contains a canonical reference:
<link rel="canonical" href="https://community.nodebb.org/topic/17867/pre-alpha-activitypub-related-bug-reports?page=3" />
If this topic appears elsewhere (and it does, on the ActivityPub SocialHub), then it would be better if that site also provided a canonical reference back to community.nodebb.org, but that's not a requirement anywhere at this point in time.
That way, a search engine upon encountering a site, would be able to learn the appropriate original source and weight it accordingly.
@julian thanks for the answer. my guess is that since google or bing do not have any contribution to the fediverse or any activitypub adopting sites (or do they?), maybe they will simply not care enough or change anything about their calculations... lol...
additionally, I believe there is this bug 
... edited federated posts are not updated on other sites? This is what it looks like on mastodon social however I have edited the second to the last word as ranks 4 days ago?
@julian additionally, I have just checked "ActivityPub SocialHub" , my edited post is not updated there either...
and here -originally- I just made a comment in a topic, but there it looks like I opened a new topic... and with a very ugly title 
is this because you have adjusted it that way?
@crazycells said:
originally- I just made a comment in a topic, but there it looks like I opened a new topic
That one's because SocialHub (more specifically, Discourse's implementation of ActivityPub) does not automatically traverse up the reply-chain to discover the original post. The original topic pre-dates @angus@socialhub.activitypub.rocks and I syncing the categories together, so SocialHub does not know about the other posts in this topic. In that scenario, it will create a new topic like you saw.
@crazycells said in Pre-Alpha ActivityPub-related bug reports:
edited federated posts are not updated on other sites?
We're sending the appropriate activity out (an Update activity) whenever a post edit takes place.
I believe @oplik0 worked on this a bit, so if there are issues perhaps he may be able to speak to that.
However there is no guarantee that updates are properly handled across the fediverse. Best effort, I guess 
Hi @devnull . I haven’t been following the forum topic federation discussions very closely, so this may be a silly question. Are forum topics going to be fully federated or just replicated (which is not quite the same thing, even for 2-way sync)? For example, if in the future there are 1000’s of NodeBB instances running and there’s a topic X, is it possible that the posts for that topic could be coming from multiple NodeBB instances (or other instance implementations)? If so, a topic-level canonical link will not work.
Google currently indexes individual Mastodon posts (at least some of them, not sure about all of them). The AP Note identifier is the canonical URL in this case. (Google also indexes actor profiles in some cases, but that’s a different discussion. )
FWIW, this is the canonical link I see for this topic:
<link rel="canonical" href="https://socialhub.activitypub.rocks/t/hi-julian-i-wonder-how-search-engines-and-seo-will/4135/2">
I’m guessing the canonical link you quoted is on the NodeBB side? Since these are different canonical links, I’d expect that Google will consider these (SocialHub and NodeBB topics) to be different web resources with mostly replicated content.
@julian said in Pre-Alpha ActivityPub-related bug reports:
@crazycells said in Pre-Alpha ActivityPub-related bug reports:
edited federated posts are not updated on other sites?
We're sending the appropriate activity out (an
Updateactivity) whenever a post edit takes place.I believe @oplik0 worked on this a bit, so if there are issues perhaps he may be able to speak to that.
However there is no guarantee that updates are properly handled across the fediverse. Best effort, I guess
thank you for your efforts. are likes and dislikes on a post also federated out?
@stevebate@socialhub.activitypub.rocks hmm... I cannot see the canonical link you posted here...
thanks for the explanation, if I understand it correctly, this means that search engines will probably penalize the websites for federation with the current settings, right?
@stevebate@socialhub.activitypub.rocks hmm... I cannot see the canonical link you posted here...
thanks for the explanation, if I understand it correctly, this means that search engines will probably penalize the websites for federation with the current settings, right?
@stevebate@socialhub.activitypub.rocks said in Pre-Alpha ActivityPub-related bug reports:
Are forum topics going to be fully federated or just replicated (which is not quite the same thing, even for 2-way sync)?
Fully federated, if I am able to. That statement means that if two categories are synchronized, be they NodeBB, Discourse, or Flarum, responses to one would end up propagating over to the other and vice versa. Things like likes would propagate through.
I haven't quite thought through the potential implications of changing rel="canonical", so there are probably gaps in my logic. Maybe rel="alternate" is a better fit.
