Identity isn't federated. You can access other instances from your home instance. Just search for the community you want from your home instance, using the [email protected] syntax, e.g. !games[email protected]
lrhodes
https://writefreely.org/ federates via ActivityPub. Last I checked, it was send only — meaning, your posts will federate to other AP services, but you can't receive messages or otherwise interact with accounts on other services. https://write.as might have more features in that regard.
One workaround is that you can set posts to include a signature with another fediverse handle, like a Mastodon account. Then, when people reply to your blog posts, your microblogging account will get a notification, and you can reply from there.
Mastodon splits the difference, giving individual accounts a number of tools to mute or block content or accounts, but also providing instance-wide tools to admins and moderators. Lemmy and Kbin are several years newer than Mastodon, so I assume that they'll eventually catch up in terms of moderation tools.
My long form answer applicable to the general trend in proliferating communities on the fediverse, so I put it here: https://beehaw.org/post/565096
tl;dr: Whether or not Beehaw starts a USPol community — or any community, for that matter — should depend on an assessment of whether we'd be a better home for it than an instance with which we're federated.
"With certain exceptions" = A blanket ban, except for anything that isn't the thing I'm trying to single out.
It can make sense to have duplicate communities on multiple instances in some situations. For example, if instance A and instance B both have Technology communities, but instance A is defederated from instance C, then that redundancy is valuable to instance C.
There are also ways to reduce redundancy — for example, different rulesets on instance A and B could result in different content in their respective Technology communities. And the questions that show up on each are bound to diverge in some ways.
Ultimately, though, my hope is that admins on the post ranking flank of the fediverse starting looking for more ways to distinguish their instances from one another. Self-hosting presents a number of opportunities that weren't really available on a siloed corporate platform like Reddit. There's no reason, for example, that an admin couldn't start up a Medical instance, and subdivide it into much more topical communities/magazines than you'd find on a "generalistic" instance, e.g. Neurology, Cardiovascular, Podiatry, and so on.
(Just as an aside, Beehaw is a Lemmy instance, so it's not really distinct from Lemmy in the same way that Kbin is distinct from Lemmy.)
The standard fediverse method for dealing with instances that have toxic or egregiously permissive moderators is to defederate from them. The best thing Beehaw can do along those lines is to have clear, comprehensive guidelines about defederation; enforce them consistently; and be ready to update them when unforeseen variations arise.
It was. But dissemination wasn't one of the charges in the Florida indictment, which suggests that they're either not going to charge him with dissemination, or they're holding off on those charges for now.
I imagine that having the other parties testify about what he showed them, couple with the audio, would suffice to establish dissemination. It's not clear to me that he would even have to show them. If the audio has him revealing info from those documents, such as the number of troops called for in the attack plan, that may be enough for a guilty charge.
I didn't mean to imply that they'd be state charges. Federal charges have to have a venue, and venue is generally chosen based on where the crime took place. These would be in a different venue because the crime arguably took place in New Jersey rather than Florida.
I'll add, one thing that the admins of lemmy.ml and lemmy.world should think about ahead of June 30th is whether its healthy — for the network, their instances, and/or their mod teams — for two instances to host the majority of accounts on the service. Personally, I suspect that a broader distribution is probably better for everyone, and if they agree on that point, then one thing they work out in the meantime is a plan for how to limit new sign-ups and the best way to direct them out to other instances.
At the moment, you have to create separate accounts for each service. It may be theoretically possible to distinguish account hosting from service provision, but at the moment, nearly all accounts are hosted by the same software that provides the service (e.g. pixelfed, peertube, kbin), and no service that I know of allows you to authenticate from a different service.