Thread Starter
unmus
(@unmus)
Argh. It has nothing to do with @name. It seems that a local comment is shared in the fediverse, if a activity pub comment is above. In the workpress configuration I do not use the thread feature with comments.
Hey @unmus 👋
the comment normally inherits the same content visibility as the post itself. so if you publish something as public, the comments will also be public, if you post something as quite public the comments will be quiet public to, … you get the point.
the plugin does not assume that a comment might be private, when it starts with an @reply (and that is also not the case on mastodon btw.)
so I would say it is a feature, not a bug 😉
but we plan to work on a post independent direct message feature, maybe that also solves your problem?
Argh. It has nothing to do with @name. It seems that a local comment is shared in the fediverse, if a activity pub comment is above. In the workpress configuration I do not use the thread feature with comments.
Every comment that is added to a post, that was shared on the fediverse, will be federated. this is regardless of other comments above or below, if you do not use the threaded feature.
Thread Starter
unmus
(@unmus)
Thank you for the very fast answer! Great!
I think, I have understood the concept now. I summarize. Comments are always inheriting the visibility from the post. This means, all comments will be federated, if the post above is federated.
I have 2 followup questions.
- One thing I do not understand. I refer again to mastodon. Normally the comment should only be visible in the profile in the “Beiträge and Antworten” section, but not in the main timeline section (Beiträge).
- With my latest wordpress post, the (local) comments are not federated, even the post above is public (regarding the fediverse). This is now a bug, correct?
One thing I do not understand. I refer again to mastodon. Normally the comment should only be visible in the profile in the “Beiträge and Antworten” section, but not in the main timeline section (Beiträge).
That is how it works for my profile… The posts are on “Beiträge” and my comments are on “Beiträge and Antworten” 🤔
I will have a look at that on monday!
With my latest wordpress post, the (local) comments are not federated, even the post above is public (regarding the fediverse). This is now a bug, correct?
Either that or it simply takes a while. We had to use the WordPress scheduling mechanism to be able to also handle sites with lots of followers. So depending on the setup of your site and/or hoster, this could take a bit from time to time.
Thread Starter
unmus
(@unmus)
Sorry – I do not want to make you a lot of work… 🙁
Following you have examples for both issues from above.
I hope this helps.
- Comments @ “Beiträge” Timeline
https://mastodon.social/@[email protected]
The post, which is labeled with “fortgeführter Thread”, is a comment. It starts with “Alles gut.”
What is also strange: If you open the “content” post in Ivory, the comment will be shown twice below the post. Once as “Thread”, once as “Reply”.
- Comments are not federated
https://www.unmus.de/sicherheitsluecke-beim-vorhaengeschloss/
https://mastodon.social/@[email protected]/114236424827258392
I push the wordpress scheduling system with an external cron every minute. If I publish a new post, this post is more or less directly available in mastodon (meaning 1 or 2 minutes later). So I would expect the same for comments.
I have reviewed all comments since I have activated the plugin. Some comments will be federated, some not. It is also mixed below an federated post.
-
This reply was modified 1 year, 2 months ago by
unmus.
Thread Starter
unmus
(@unmus)
To avoid confusion, I will create new separate topics in the forum for the issues above, and close this one. The identified issues are not in relation to the initial question anymore.
Sorry for the strange initial report. I was really confused about the process as some comments are federated, others not. Our discussion has brought more clarity for me about the standard process of the plugin.
