Kobolds with a keyboard.

  • 1 Post
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2023

help-circle





  • KoboldCoterie@pawb.socialtoFediverse@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    4 months ago

    It does, though, because not every instance federates with every other instance. If someone is coming from Reddit, and they interact with a set of specific subs there, and they want to interact with the analogue communities here, they don’t want to join an instance like, for example Beehaw, that has very strict federation policies, or (probably) .ml or lemmygrad, where they’ll be exposed to stigma they weren’t aware of going in and which might not apply to them.

    A list of servers with very open federation could solve this problem in theory, assuming new users knew to reference it, but that might not be what they want, either.

    The invite code idea is actually solid, I think, assuming they’re handed out to people who have things in common with the target userbase of the instance, and not arbitrarily.

    There’s also some instances that hold united views on specific topics, for example blahaj with trans rights, and someone arbitrarily choosing that instance that doesn’t hold those same views might feel that they don’t fit in.

    Obviously anyone can just choose a new instance and move, but for a new user coming in, that’s a ‘quit moment’ in many cases. Giving an invite code to someone that leads them to an instance that at least broadly fits what they’re interested in could help solve for this.

    Edit: I think having more instances that have specific themes and topics, like slrpnk or programming.dev (or pawb, for that matter) would help, too. Someone looking in from the outside might not understand federation, but if they see an instance geared towards a topic they’re interested in, they might be inclined to join it even if they incorrectly think that’s all they’ll be able to interact with.




  • if you have a more effective metric in mind, I’d love to hear it instead of just pointing out flaws

    I mean, isn’t the whole point of this comment section to discuss the merits and flaws of the proposal you’ve made? If we’re not discussing the downsides, too, what’s even the point?

    That said, an ideal system would be a measure of the quality of content, not the quantity of content so, as another user has suggested, some measure involving net upvotes might be more effective. Yes, obviously a user can create multiple accounts to upvote everything and fuck with that metric, but I kind of doubt many folks would go to the trouble.

    Maybe some combination of PCM and the average number of votes divided by the number of active users could generate some sort of quality metric. At the very least it might be a measure of engagement.



  • This is kind of up to the individual community, not the instance as a whole. An instance theoretically could make a general ‘No memes on any community on this instance’ rule but it would be awful to enforce, and it’d be easier to leave it up to communities.

    That said, I think Lemmy is a long way off from having the userbase or popularity to create that problem, and the absence of karma or any analogue really narrows the impact. Personally, I’ve seen significantly less low-effort content here than on Reddit, with the exception of a few specific communities that exist for that purpose specifically.







  • In some respects it feels like many federated platforms have approached things backwards, trying to rework a centralized structure to be distributed/decentralized, creating some of the awkward UX folks experience.

    I think you’re right, but that this is also promoting faster adoption of the fediverse version of the apps. It’s a lot easier to say to someone, “Hey, here’s a FOSS alternative to this corporate app you already use, it functions the way you’re used to” than “Here’s a FOSS app that does something completely new.”

    Once folks are interested in the fediverse through adoption of Lemmy, Mastodon, etc., it’ll be easier to get them interested in completely novel applications.



  • The real problem (IMO) with it being automatic based on the URL is that it’d be impossible to isolate communities with radically different views or posting guidelines - for example, a conservative community and a liberal community sharing a comment section about a political article would be awful… neither group wants that, and it creates moderation problems - who would ultimately be responsible for moderation on the article’s comments? The content source itself? (That seems incredibly unlikely to end well.)

    I think it’s an interesting idea, but there’s some major implementation hurdles and I’m not sure what an ideal solution would be…


  • This effect could be achieved if cross-posted links simply all fed back into the comment section of the first community it was posted to.

    To maybe better explain that, let’s say I cross-posted a link to [email protected], and [email protected], [email protected]. Under such a system, all 3 of these posts (despite being to separate communities) would share a single comment section (in this case, the one from [email protected], since it was the “first” one I chose to post to)… so if someone opened the thread on [email protected], they’d see the same comments as someone on either other community.

    This implementation wouldn’t require getting content sources on board, and would cooperate with instances that weren’t federated (by simply creating a separate comment section for any instance that isn’t federated with the “first” one the link was posted to).

    This doesn’t help if two users post the same link to two separate communities, but it’s at least a little bit cleaner without requiring any external buy-in.