I think the ones added by plugins are still a little inflexible when it comes to customising the sidebar. I think this is still the advised way of doing it:
Thank you this worked for me
For some reason it still appears in the sidebar on mobile, any clue?
Best regards
Olle
Ah, this looks like it may have changed for mobile based on the new way āmoreā is displayed.
I think this should do it for āFederationā:
.sidebar-more-section-content {
li[data-list-item-name=activity-pub-about] {
display: none !important;
}
}
Great thank you!
I think you can also use
.sidebar-section-link-wrapper[data-list-item-name="activity-pub-about"] {
display: none;
}
to hide the link on mobile and desktop
A post was split to a new topic: Actor not discoverable on other sites
Hello, I installed the plugin, which was very easy, even I did not know either Mastodon or the plugin. Everything works well except for one small detail that Iāll explain here.
When I personally publish a topic as an administrator in the categories that are subsequently published on Mastodon, there is no problem. However, today, one of my users who had never posted on my forum before published a post in one of the categories. Naturally, this post went into the approval queue. I approved it, and the post was published in the category. However, it was never picked up by ActivityPub and published on Mastodon as I believe it should have been.
I considered two potential issues: first, this user is not an administratorācould that be the problem? Second, perhaps the issue stems from the fact that this post first went through a moderation queue before being approved by me. Could this have prevented it from being published on Mastodon? What do you think?
I also have a related question: uncertain about what was happening, I published a test post myself as an administrator, and there was no problem. After five minutes, it was posted on Mastodon, but I was unable to delete it from Mastodon. I suppose this is because it didnāt go to my main account but to an account linked to one of the actors. It seems impossible for me to control these actor-linked accounts on Mastodon, but that is more of a Mastodon-specific question.
Thanks for your attention.
I reckon this comes from same ground that any topics, that arenāt kind of organic, written in that category and published in normal way, donāt be federated.
You can do it manually, though.
Same happens with WordPress plugin or if a topic is published with the timer. Or moved from non-federated category to federated one.
I think that is more lacking a feature than a bug per se. ActivityPub isnāt totally ready yet.
You can remove a message from your sight, or from local timeline, if you are an admin of that instance.
But you canāt ever delete a message that isnāt yours. You must be the OP in the original instance to delete ā and even then it is pure luck if all others in the Fediverse will follow that deletion request.
So you have to delete it from your forum and Iām not sure if that deletion will be federated too from Discourse. But you should be able to un-federate in Discourse. Anyway⦠it isnāt that big question because after few minutes no one sees such posting because of high traffic from Fediverse
Thanks for your answers, not a big deal overall, but I wanted to exclude a possible wrong manipulation on my side.
Hey @patrickemin, thanks for trying out the plugin and Iām glad itās working for you, and that it makes sense. Thatās nice to hear
Yes, this is expected behaviour. We donāt auto-publish posts on approval. As @Jagster notes, you can use the activity pub topic actions to manually publish a topic and its posts after approval. We may add a setting to auto-publish posts after approval. Some folks may still want to do that manually as people use the approval queue for different reasons.
Yes, this is also expected. When a post is federated, the āactorā that controls it is the actor that federated it. You wonāt be able to delete it using your mastodon account. You need to delete it on Discourse itself. We then tell mastodon to delete it there too.