Isn’t it? Even if I knew what exactly was supposed to happen, the fact that it ACTUALLY happens is almost magical.
This changes the notion of forum registration and membership… I mean, you still need to register here to participate here, but having this possibility to participate casually from the outside is great.
How should one go about finding/boosting/following the posts/account/server from Fedi?
I can get Note links from the federation icons, but pasting the URL in mastodon.social yields no results.
EDIT: Can confirm it’s reachable from Misskey – so probably just a Mastodon- or DotSocial- specific thing? (I don’t have another Mastodon acc to check and idk if URL lookup on other Mastodon instances works if you’re not logged in )
Count one more for the “I find the helpful and engaging onboarding experience of Discourse to be helpless and enraging” camp. (Special greetz to @discobot!) Well, chalk off all that to habits, acquired taste, personal preference, accident, coincidence, or concerted action – either way it’s good to see you on here @sknob@mamot.fr!
@icaria36, I know you’ve had enough of us nasty curmudgeons, but here’s another you might want to be aware of – probably belongs in the Discourse federation plugin developers’ backlog: seems to be impossible to tag a Fedi actor from a post.
Actually it’s a fun one – I hoped that if someone’s username here is the same as on their homeserver, maybe it makes for a cool way to tag someone in both platforms? But I don’t seem to be able to tag @sknob who is accessing this thread entirely over Fedi and the blue/green federation icons seem to have misled me about that one.
I also don’t know yet if edits are being federated, and you don’t seem to actually be registered to have a profile settings page, so Categories - Social Music Network is where the good stuff starts.
Philosophically (and, hopefully, federatedly), I don’t think “the entire point” arguments count here (even though I’m also prone to making them — by goodness, people! how can you not see! — and all that; very much in my style, I kid you not)… while discussing things “in depth” is something that recovering exclusive microblog/chatroom users especially might need to become reacquainted with, because, after all, who knows what horrors might lurk in those depths, that Twitter was valiantly protecting us from for has it been nearly two decades?
Anyone else remember being shepherded onto corporate social media and thinking “oh, so a cool big forum with everyone!” Such sweet summer children we were. And now… surprise me with horrors beyond my comprehension, O World, for I really need to catch some shut-eye and could use those
@icaria36@the.socialmusic.network@sknob My message above is a reply to you, but because I'm still learning how this federation works, I'm not sure you have seen it in your notifications as a reply or mention.
Thank you for your criticism to the project (it help us improve) and your help testing this federation thingy!
(If I understand your comment correctly…) Yeah, no, Discourse doesn’t have different permission levels at a topic and a comment level. If the topic is in a public category, the first post and all the rest will be public as well. At least this makes sense from a Discourse perspective.
Similarly, is there an option to unferedate certain posts? Some of mine certainly aren’t federation material, but it seems to be determined by the thread settings.
Topic was published via ActivityPub on Sun, 5:01 pm.
A dialog opens that shows the Fediverse account that published the post. I’m able to find that account from my Mastodon account, and then find the opening post and the replies. I just wish there was an easier way.
@unspeaker Discourse offers a setting to federate all posts in a topic (that’s the one we have selected) and another one to only federate the top post and not the replies.
In the latter case, moderators can federate specific replies. But “de-federating” federated replies isn’t obvious. Maybe deleting your own reply? Moving it to another thread? Not sure.
Moderators may be able to act in serious cases, but it is not sustainable to offer a service à la carte in a scenario with many topics federated and many users commenting. On the other hand, what is good for TSMN shouldn’t be that bad for the Fediverse, right?