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