Astronomer & video game data scientist with repressed anger

  • 0 Posts
  • 97 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle
  • I guess, but it also puts a lot of pressure on those small ones to be indistinguishable from the big ones, by having people treating them like they’re the same place.

    I don’t think Lemmy scales the same way that Mastodon does. I don’t think this topic-based community forum model translates to federation the same way the individual-based microblogging space does. It’s a more complex space, with more layers to manage. It’s often mod or admin driven, whereas microblogs are entirely about average user behaviour.

    I don’t think it replicates Reddit the same way that it replicates Twitter. I think the mental model just doesn’t fit the tech.

    Like, yeah, letting users make personalized community lists is one thing, and I get the appeal, but it ends up functioning very differently in a space where multiple communities can have the same handle, you know? I can lump 5 different gaming subreddits together into a single stream, and be totally and intuitively aware that they’re different. They have different names, and they present differently, with different stylings, when you actually click through to a post. Without those signals, though, empowering users to lump communities together only has benefits to smaller communities if those communities are looking to grow for growth’s sake.

    Mastodon has done a great disservice to its admins and users by trying to mask the federated nature of the fediverse. By trying to sell ‘Mastodon’ as a space in and of itself. By trying to make the actual website you’re using invisible. I don’t think we benefit from that in any way. Indeed, I think it’s only the platform developers who benefit, by making their product the only thing people really see. But the individual websites that make up these networks of social networks are entities in and of themselves. They’re like neighbourhoods, or towns. They have their own infrastructure, their own residents, their own characters, and their own needs. Treating them as interchangeable or invisible, ultimately, I feel, stymies the actual potential of the space.

    Because this isn’t Reddit. It doesn’t work like Reddit. It can’t try to be “Reddit, but ____”, because it fails at the first word. The way forward is in recognizing that, and trying to figure out what this new space really is.

    And one of the things it is is not one space.


  • community discoverability, […], and moderation tools

    Those are big. But so is the lack of smooth interoperability with Mastodon. There’s a large population using Mastodon right now that could be participating in threaded discussions here, who are just totally blind to the space, and those that do engage have a super jankey experience.

    And on top of that, it’s also a super jankey experience on the Lemmy end when Mastodon users engage.

    Hopefully things get better on that front once Mastodon has implemented groups.

    not being able to group communities together

    I honestly see this being a continued expectation to be a bigger issue. Two communities with the same name on different servers could be very different spaces. Giving users the ability to group them together homogenizes them in a way that is likely bad for the ecosystem overall.

    Like, it’s fine to have federated or merged communities, but I think that power needs to be in mods and/or admins hands, not end users.





  • I like the “antennas” feature a lot

    For the uninitiated, Firefish’s antennae are saved searches, where you can specify lists of keywords and users and come back to them over and over again. It’s similar to Mastodon’s hashtag follow feature, only more flexible. Though, IIRC, it doesn’t add the search results to your home feed; it keeps them separate, and undiluted.

    From an administrator’s point of view, Firefish’s Recommended timeline is super cool, and is similar to Akkoma’s ‘bubble’ feature. It lets you specify a list of other federated servers to display posts from, creating a kind of “super-local” timeline. It’s the kind of thing I’d love to see in Lemmy and kbin.


  • Firefish is definitely a bit of an unfortunate rebranding. Though ‘Calckey’ wasn’t exactly setting the world on fire, as a name, either. But at the end of the day, we really need to learn to recontextualize fediverse plataforms as software that runs a service, not the service itself. They’re website engines that power social websites, not a social brand in and of themselves, kind of like how WordPress is a quasi-static website suite that is used for a huge number of blogs and quais-static websites.

    No one shares something from, say, the TechCrunch website, or Time website, and goes “Hey, Iook what I found on WordPress!”



  • No, that’s not actually reasonable given how federation works. You’re not viewing content on other instance, you’re viewing content imported from other instances. Copies hosted locally. This puts admins in the position of actively hosting content they may find objectionable if it’s allowable on other sites and they’re federating with those sites.

    Your instance is not some neutral community browser for remote communities. It’s not the equivalent of Chrome or Firefox. It’s the equivalent of a website hosting guest authors, and the website admins are responsible on some level for what they choose to host.

    If you want wide open freedom of choice, you have the ability to host your own instance. That’s how you get carte blanch to decide what you see and what you don’t.





  • If a Threads user is following you, they need most of this information. It’s literally how the Fediverse works. The only thing that isn’t is your IP address, and that’s something that I’m not sure they’d even get. That might be your host’s IP address.

    Remember, the Fediverse isn’t a bunch of iframes looking at 3rd party websites. It works by mirroring remote content. A follow is literally a request to ingest posts from a user.







  • It would be nice if servers could be tuned to prioritize locally hosted communities over remote ones. There’s a real opportunity for each community on the same topic to have distinct flavours and cultures, but so long as they all appear to be the same damn thing and appear with the same frequency in the content stream, it’s never going to happen. It’s not like people really look at the remote server domain.

    It’s really nice that the Local feed exists, but when people just bulk subscribe to 8 different communities with the same name, stick to their subscription list, and then treat them all as the same place, that just kills a lot of potential for heterogeneity.