lrhodes

joined 1 year ago
[–] [email protected] 4 points 1 year ago

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.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

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]

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 6 points 1 year ago

"With certain exceptions" = A blanket ban, except for anything that isn't the thing I'm trying to single out.

 

I've noticed several people remarking on something that leapt out at me when I first starting using Lemmy at the beginning of the week: Topic redundancy.

There's redundancy on Reddit, too, of course, but the propensity is much higher on the fediverse. There are already hundreds of Lemmy/Kbin instances, and the fact that users on most of them can create their own verticals means we're bound to end up with hundreds of communities/magazines dedicated to broad categories Technology and Politics and Games and so on.

As I've pointed out elsewhere, that redundancy is not necessarily a bad thing. The nature of federation means that not all Technology verticals will be available to every instance, so having a choice of instances with thriving Technology verticals ends up helping instances avoid getting locked out of a topic that they may not want to host or can't handle particularly well.

But there are limits to the utility of redundancy. And there's a point at which subscribing to multiple verticals of the same topic turns counterproductive, filling your feed with so many duplicate links that they can push out worthwhile posts that you might have otherwise seen.

What's needed is a middle ground: Enough duplicates to serve everyone interested in a given topic, but not so many as to undermine the benefits of federation. Coordinating that across hundreds of instances is probably impossible, but instances can cut down on a lot of needless redundancy by being selective about which topics they cover, letting federation connect them to communities for the topics they don't.

That requires some restraint. As software, Lemmy and Kbin have taken their cues from Reddit, letting regular account-holders create their own communities. That feature wasn't originally part of Reddit— they added it when growth reached the point where admins couldn't keep up with subreddit requests. The situation is different on the fediverse, and most instances don't need to operate the same way as a single-domain website will millions of users. Beehaw, the instance I'm on, reserves community creation for the administrators, and so long as they're responsive to requests, I think that's probably the wisest course of action.

More than that, I don't think they should approve every request. Too many verticals becomes difficult to manage. And (more to the point) there's no need to cover every topic. Other instances are going to handle some better. There's no reason Beehaw users shouldn't subscribe to those.

Take politics, for example. Someone recently requested a US Politics community to keep US-centric posts from drowning out the politics of the rest of the world. That's reasonable, but why stop at US politics? Why not politics for every country? Every state or province? Every city? At what point does it stop being reasonable to subdivide the topic?

What would be better for everyone, I think, is for each instance to decide which regions they're best qualified to host a Politics vertical. Let admins who know how to handle US politics manage the community for that region. The admins who know EU politics can handle that. There can be a Politics for every region instances feel competent to cover. And once we get a sense of who covers what, people will gravitate to the ones that cover and moderate them well.

[–] [email protected] 7 points 1 year ago

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.)

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago

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.

[–] [email protected] 4 points 1 year ago

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.

[–] [email protected] 3 points 1 year ago (2 children)

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.

[–] [email protected] 3 points 1 year ago

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.

 

145 giochi di ruolo per $10

 

Some context: I was /u/Blackstar9000 on Reddit. You might know me from /r/TheoryOfReddit. Or maybe not—I ditched my account there a number of years ago. I've been on the Fediverse for about 6 years, primarily via Mastodon. Last October, I deactivated my Twitter account. I've been through a bunch of social media sites, and I've seen the patterns. This post is about those patterns.

A lot of you are trying out Lemmy or Kbin because of what's been happening at Reddit. (Welcome to the Fediverse!) And a lot of you will be going back to Reddit as soon as things quiet down. You might not think you're one of those people, or you might not be sure where you stand. I'm not here to tell you what to do, just to prepare you to decide. That's the goal: a decision. As opposed to letting inertia decide for you.

There are a few factors at play here. One is that you're accustomed to Reddit. You may not like what's been going on there lately, but the platform is familiar, you know how it works, it feels like a broken-in pair of sneakers. Every bit of friction you feel here is going to nudge you back in that direction.

Another is that the Fediverse is different. Lemmy and Kbin are designed to do something very like what Reddit, Digg and other link-aggregating social sites do, but the fact of federating with the broader network makes certain complications impossible to avoid or ignore. And there are deliberate differences that have less to do with federation than with what the devs thing might work better. Some people adapt quickly, others don't. Some people just plain don't like it. In any case, there's a learning curve, and that's bound to be a source of friction.

A third is that Lemmy and Kbin are still finding their footing. These are independent, open source services, and they're in the process of becoming the things they'll one day be. Mastodon went through similar growing pains, and a lot of people bounced off of them during those awkward years when the UI was rough and the feature set incomplete. People's ideas about Mastodon changed more slowly than the service itself, and it wasn't until things got really bad on Twitter that adoption rates kicked back up again. Mastodon still isn't what Twitter became, and probably never will be, but it's a much more professional-feeling piece of tech than it used to be. Someone is building the airplane we're flying on. Any Fediverse service that survives long enough will go through that process, and if you're not clear-eyed about the need for patience, that too can push you away.

A fourth factor is social. If you've been on Reddit for a while, then you probably have a decent mental map of your relationships on that platform. You'll probably reconnect here with some people you know from there, and maybe even carve out spaces where you can reconstruct some of the communities you were a part of there. But you can't transplant your entire social map. To stay here—to even want to stay here—you'll need to build a new web of relationships, one that might include some portions of the old web, and that's more friction.

All of that friction adds up, and the only antidote, really, is resolve.

So you'll hang out here during the blackout, when there's friction on both sides of the line. A small minority of you will take to the Fediverse immediately and move most of your activity off of Reddit. But only a small minority. Some of you will get a taste for it and split your time between here and Reddit. For most of you, though, the gravity of your history with Reddit will win out in relatively short order.

No hard feelings. We're happy to have the people who stay. But if you go back, let that be something you've decided to do, not just muscle memory taking over. Because that's another thing I've seen happen time and time again: People try out the Fediverse, only to drift back to the corporate platform. Then six months later, a year, two years, something new comes up. The platform finds a new way to alienate users, and some subset of them will go hunting through their email to figure out which Fediverse server their forgotten account is on, and what login name they used. (Trust me: keep that info somewhere you can find it.)

Going back is a valid decision! I just want you to decide, rather than let muscle memory decide for you. And if you go back, set a limit for yourself. Figure out the straw that would break the camel's back. Tell yourself, "If they ever do this, I'll delete my account," so that if they ever do that, you actually will.

view more: next ›