Asklemmy

44978 readers

1120 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

Do you have any rules you try to follow when engaging with others online? (sopuli.xyz)

submitted 1 day ago by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

I'm curious what, if any, guidelines people self-impose to try and engage in a productive way online (both on Lemmy and elsewhere). "Netiquette" if you will.

A couple of rules that I think are good practices, but still see too often, are:

don't pile onto the most downvoted comment. Kinda like don't feed the trolls, but it's more about not letting yourself get rage baited. Instead, downvote them and move on.
don't give a non-answer to someone's question. Ex. if someone asks how to do X, don't answer with, "Why are you trying to do X? You shouldn't want to do X. Do Y instead." Instead, explain what it would take to do X, and then offer Y as a possible alternative and why it may be a better option. But assume they already know about Y, and it doesn't fit their use-case.

For that last one, finding a thread where someone has asked the exact question you want answered, only to find a thread full of upvoted non-answers is up there with the dreaded "nvm, I figured it out - 10y ago".

you are viewing a single comment's thread
view the rest of the comments

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

I think answering questions in the context of work is different, because then, yeah I agree, your goal isn't to answer their question, it's to solve their problem.

But if someone makes a thread asking "How do I serve a fileshare publicly", I think it's better to answer with something like, "Open this config, change these options, open these ports in your network, and restart these services. NOW, why do you want to do this? Because it might be a bad idea...etc." Assume that their usecase is private info, and that they are asking the question they mean to ask. Because when someone else who knows they need to do X comes searching for this thread later, you won't be able to ask about their use case.

I also made this adjustment in another comment, but I think at a minimum, if you're offering Y because you don't know how to do X, don't say "you shouldn't want to do X", instead be clear and say "I don't know how to do X, but Y might be an option for you". If no one reading the thread actually knows how to do X, then that's also useful info.