DevOps as a profession and software development for fun. Admin of lemmy.nrd.li and akkoma.nrd.li.

Filibuster vigilantly.

  • 1 Post
  • 30 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • I would still go with one that isn’t one of the biggest. My general advice is to find one that fits the vibe you’re going for, communities you’re interested in (e.g. some are focused on art or cybersecurity, etc), or is somehow tied to your locality. It shouldn’t matter that much, though some servers will be a little more (or less) strict with things like federation, content warnings, alt text, etc. Usually the server will have some info telling you some of this, and their admin should be linked and likely has a post or two pinned to their profile explaining some of this as well.

    I am partial to kind.social, though have opted to run my own instead of joining up anywhere.


  • Honestly it depends on what your experience level with running software is and what you want out of it. For me things have been rather smooth sailing as I already host a number of things for myself (so know all about domains, DNS, servers, reverse proxies, docker, etc.) and I am the only one actively using my instance right now so (local or admin-level) moderation isn’t really an issue either.









  • I understand that urge, and in my ideal world it would a whole new option of “Suggested” feed rather than a replacement for “All”, like how that other site has a /all but defaults to a more curated selection of content that has broad appeal (and IIRC even some things are excluded from /all over there). For now I’d just take being able to filter the “All” view of the most objectionable stuff that I only want to allow users of my instance to explicitly opt into by seeking out those sorts of places.

    Also, unless your instance is purposely seeking out and subscribing to every community in every instance the moment they are created “All” is never going to actually be all posts from everywhere… I imagine larger instances may approach that, but I am certain there is a ton missing from smaller instances like my own.







  • Be the change you want to see. Setting up an instance is surprisingly easy, it’s the admin stuff that will take much more time, and finding users that will probably be hard. Also scaling once you hit a certain level of size/traffic, but that’d be a good problem to have. To me the most beautiful part of the fediverse is that if you’re not finding the instance with rules/defederation/etc you want you can make that place exist.

    If you are interested in doing so I’d be more than happy to give what advice or help I can.


  • I expect the moderators of communities to do sufficient policing of their community to make sure it follows the rules of the instance it is on and the rules of that community. If those rules permit something you disagree with (or don’t permit something you do want to see) the power is in your hands as a user to not participate or even see that community. The only way for a user to guarantee they won’t interact with someone from instance X (whether that is exploding-heads or lemmygrad or whatever you don’t like) is to only interact with communities on instances that have them defederated. There are places you can get a more curated and aggressively moderated experience, and have been recommending places such as beehaw to anyone looking for that.

    I will take action against:

    • Local users harassing someone
    • Local users breaking local rules
    • Local users repeatedly breaking remote rules
    • Local communities that break local instance rules
    • Remote users harassing local users
    • Remote users repeatedly breaking local rules
    • Remote instances that repeatedly allow its users to break local rules
    • Remote instances that repeatedly allow its users to harass my users

    The first rule on my instance is a catch-all “Be welcoming”, that will be wielded to aggressively remove far more than just “racism, sexism, homophobia and transphobia”.

    As an admin I don’t have the time or desire to police:

    • Local users interacting on remote communities, so long as they are following remote rules
    • Remote communities
    • Remote users interacting with remote users/communities

    I do hope for a way to better curate (or just disable for now) the “All” feed, at the very least for anyone who isn’t logged in. Given the general rules above that feed may include disagreeable posts, and is not a good representation of my instance or the type of community most users there will experience.



  • Users are empowered to set what they want their default homepage view to be (“Subscribed” , “All”, or “Local”). I am unsure what the default is, but mine is set to “Subscribed” which I think it makes the most sense for most users.

    Unless you are on a heavily moderated/defederated server (such as beehaw) whose moderation policies, politics, etc. you are aligned with it is very likely that “All” is going to contain something that someone doesn’t like. I am personally not in favor of over-policing what users do outside the confines of their home instance, it’s a fine line that I haven’t had to define too clearly yet so perhaps my thoughts here will change.

    If you don’t like what’s in “Local”, then to me that is a sign that the instance isn’t for you. Local is a reflection of the sort of content that users on that instance want to see more of. The admin allowing such content is not necessarily an endorsement (unless they were the one to actually post it), but is tacit acceptance of that content and the community that content exists in.

    I think some way to make a “Curated” feed of posts only from certain approved communities would be a welcome feature and present a useful middle ground allowing for a moderatable discovery experience, like the default subscriptions provided on that other site.