There’s always some risk to directly editing an app’s database even if it’s documented and that expands through all future updates. There’s also security implications for enabling the feature that lets me create custom badge triggers.
I’m also worried about generating distraction/work for creators if it’s something we can solve ourselves or we don’t critically need. Ideally when creators hang out in the community it should just be a source of fun so I made this thread to funnel tasks our way because we can handle them.
Just editing the Basic badge is probably the way to go, I was just curious if anyone might know a different feature or workaround.
I can also set a badge description that tells the user how to apply it and I think? that description shows up in notifications when you get the badge. Not sure on that. It could also be in the “Welcome to the forum” message but how to actually edit that message is a whole nother ball game
The best solution, IMHO, is that if you feel that it is necessary to communicate that you are new to Linux (or even new to app that your are troubleshooting), AND if you feel that communicating that would be helpful to those assist you, then say so in the body of the message.
Reduces barriers to asking questions. I’ve found new users can feel compelled to write a few sentences or a paragraph every time about being new.
Reduces read time for understanding a question and it’s context.
The presense of a group conveys that the forum welcomes new user questions.
Knowing someone is new to Linux can be generally helpful even if it’s in random discussion.
If a user removes their “new to linux” title, it’ll make it look like the answers to their former questions are contextually appropriate for a regular Linux user. If it’s a hackie work-around to avoid the CLI it could give other people a bad answer or compel someone else to correct/improve it later on which creates a lot of confusion.
The user would create their own profile. One of the features in their profile could include the user skills (terminal user, gui user). The whole idea is to identify what type of user is asking the question. I would love to see those new to Linux feel like they belong. I just thought this would be a useful feature that could benefit those who don’t have higher technical skills. I’m not trying to label anybody, that is not the intention. I hope that clarifies the idea.
Understood, but even though I could identify myself as a gui and terminal user, neither term really describes my actual experience level.
My stance is that requests for assistance are using very specific and trying to use a general label is akin to trying to put a square peg in a round hole. I would rather help new users at their specific experience level whether that be experience with Linux or the specific issue they are having.
That makes perfect sense though i’m not sure it applies at the edges.
I think someone who’s comfortable with even just a small part of Linux tends to have a massive advantage over new users in foundational and complementary skills that apply to everything else. Such as… somewhat knowing where Linux information is and grasping general concepts.
I think those new users are driven to describe that newness at length over and over because of how much the basics are usually taken for granted by people answering which is a VERY human thing to do.
It’s similar to how Windows users often take for granted how much they’ve absorbed about Windows to the point they think it’s inherently easy to use.
It’s an edge case that’s unintuitive and might be worth making it easier to convey.
This is just really valuable stuff to know in general, thank you @jjj12
^ this is the part i’m getting stuck on because there’s a few threads that get a lot of search engine foot traffic.
Having the questions posted in a “New to Linux” category would help solve that, great idea.
I’m not sure if it should a requirement that be in a “New to Linux” group though because it’d force them to have the title which should be optional and it increases the hoops they have to jump through.
What do you guys think about just having the category?
I agree in part. My message was intended to say ‘meet the user where they are’. While I am not a beginner to linux, I am most definitely a beginner with BTRFS (and many other things linux related). Everyone is different and everyone is at a different point in their Linux journey. Meet them where they are, so to speak and the assistance will be better received, and less time will be wasted. This comes from me working in IT for almost 30 years.
I don’t understand the inhibition to search for troubleshooting information. Even if you are a windows user (especially if you are a windows user), you have to learn to search and troubleshoot or forever be dependent on someone else to fix your issues. I just can’t be that person. I just couldn’t use a computer and feel completely useless with not being able to fix any issues myself. That would prohibit me from depending on the computer. But, that is just my opinion.
The more I learn about Linux, the more I realize how windows is actually harder/more complicated.
In conclusion, it really is up the the requester to voice their experience level when they receive information they don’t understand. We should probably be discussing how to better interpret one’s experience level. I’m so glad that I don’t see any elitist RTFM crap here. There is not bigger turn-off to new Linux users than to hear that.
FWIW, the sheer number of results that type of issue is what led me to purchase an AMD video card. While this might not be the typical case, the only issue, if I can call it that, was finding a distro that used a new enough kernel version. Of course that was the issue back when I first got the card. These days many distro’s are using new kernels. My next issue, specific to me, was to find a distro that included everything to get vulkan working with my card. Instead of learning about all the in-and-outs about vulkan and what is needed to get it working, I just used a distro that had all of that all worked out - Garuda.
So, that was my way of working around that issue instead of having to learn everything about Mesa.
Make it easy for users new to Linux to communicate exceptional and often unintuitive needs for answers that stick to the paradigm(s) they’re used to even if they’d normally be a bad or less than excellent answer. Bonus points for including the best solution below the one they need.
Also to extra-convey to that their questions are welcomed.
Request: If you’re new to Linux and would like any of these for yourself…
PM me or post below which ones you’d like for yourself.
Is integration with Nextcloud something that has to be allowed on the discourse side? When I get redirected to https://forum.tuxdigital.com/user-api-key that’s the end and nothing else happens. I’d consider it an improvement to get this working haha
Beyond that it’s hard to find information so i’m pretty lost on the context. Does this require the Network have a NextCloud in order to use this? Is it for 3rd-party NextCloud’s tying into the forum? Questions like that…
My Nextcloud should just pull in the normal notifications from Discourse that would be visible if I was visiting the site in a browser. It doesn’t require the Network to have Nextcloud. Thanks for looking into this, I’ve left a comment on a related Github issue for the Discord integration app.