Oh, come on!

Thanks for the red circle, I was really lost there for a moment

I can’t find where your comment is. Can you please add a red circle so I can read it?
- Thanks for the red circle, I was really lost there for a moment
  
  ➕
  
  ⭕️
- 🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥
  
  🟥Thanks for the red circle, 🟥
  
  🟥I was really lost there for a moment. 🟥
  
  🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥

Here is a basic way to configure the service:

…

But this method has significant drawbacks and probably won’t work for most use cases, so do what works for you.

No other info whatsoever.

And then you go hunting for other people's config files.
- And those configs are clearly the result of someone else stitching together three different examples from different versions, with some settings that are silently ignored in the latest version or only exist when compiled with special flags.

“Just follow the build instructions on GitHub”

1000 error messages ensue.

That’s your own darn fault. You were supposed to know the 0.0.1 version was GA instead of assuming 0.0.3-alpha was stable. You would have known if you read the 2000 line README. On the second dependency there is no README though, so just use the latest and hope it’s still compatible.
Last commit 8 years ago "Updated for Linux 4.5"
Then do some digging and find that the GitHub instructions omitted some particular dependency, make a mental note to contribute a PR to the documentation later once you've got it working, get it working, promptly forget contributing that documentation, move distro later, try to reinstall the same program, make the same mistake, same discovery, learn nothing, repeat ad nauseam.
I'm trying to learn Houdini. I thought, "Oh, I'll just download a template and see how it should look."

Even already-made templates are apparently out-of-my-depth.

OpenSUSE microOS guys be like

dont install any RPMs
we wont help you adding RPM repos
you need to install RPMs for drivers and stuff

😂
Same thing with installing drivers in Fedora SB
- No on Fedora Atomic Desktops for some reason people tell you not to install RPMs, but actually it is unproblematic.
  
  Unlike OpenSUS microOS, Fedora Atomic Desktops have a reset function to delete all local changes and become 100% upstream.
  
  The issues really only come with /var, /etc and the user home where config-file-creep grows and you get random errors after doing to much shit with your install.
  
  But it is still safer to install RPMs on than on dnf Fedora.
  
  OpenSUS microOS has no advantages over traditional Tumbleweed afaik, apart from the atomic updates that you have a single fallback option.

"Just gotta enable the OEIS menu in the .sysbin folder and it'll make that program CHIM, that should solve your problem"

What it looks like when I ask "how do I put Cura on the taskbar"

I don't know why such answers get so many upvotes.

The real answer is: Right-click -> Pin to Taskbar. (In sane desktop environments like KDE. If you choose to install Fancy DE Alpha 0.0.2, you know what you got into!)

Yeah we are in a meme community, still I like my memes based on reality, makes them way funnier.

(Also having a standard place for documentation for everything is a blessing!)
- Sure but it’s not a rarity that forum answers expect you to be very familiar with linux file structures and terminal commands. If you’re a beginner who runs into an issue (as beginners do), you oftentimes need to find a tutorial and then tutorials that explain the tutorial. It gets even worse if you’re not on a debian/ubuntu based distro (although, to be fair, if you’re a newbie, that’s sorta asking for trouble).
I'm concerned if CHIM is what I think it is, I don't think I want the computer doing that.
- You don't want your computer to gain incredible, godlike powers?
"The real problem is that you're using Cura and not Orca"

This is some unnecessary red circle shit right here.

But look how pretty it is 😊.
Clearly added for emphasis, crucial instructions, we might mistake for other instructions in the picture.

As someone who works in manufacturing this makes prefect sense and wish more instructions were this clear

How 🤨... tighten, but don't...
- Tighten them but tighten them not too much but make sure not to tighten them too less, I guess
- Tighten but don't overtighten them, probably.
- It means “put all of the screws in the holes in order to start guiding the surfaces that you’re screwing together into the correct position, but don’t firmly tighten down all the screw until you have put all of them in so that you can ensure proper alignment of everything before you lock it in.”
- Like put them in a few threads but don't tighten then yet until you complete the next step
- It just lacks a torque spec.

If you did tighten, DO NOT LOOSEN.

Tighten't.

Clear your mind. Simply "be" the screws. Do not aim for completion, for one is never complete. Also, it's upside-down.

It's hard enough to express this in a first language

What is a first language?
- The first one you learned or became fluent in. For example, it's often English for USA people or Spanish for Spanish people, or Japanese for Japanese people
  
  Often also called mother tongue or primary language.
  
  Otherwise, it can be the one you are most comfortable with or default to.

Don't use sudo to run this command, but do so if it doesn't work. Using sudo may break your system.

The sudo thing should really be explained like "if you want this implemented system wide, run it with sudo, if not, don't use it".

POCKET GUIDE TO TIGHTENING TECHNIQUE https://www.atlascopco.com/content/dam/atlas-copco/industrial-technique/general/documents/pocketguides/9833864801_L.pdf

I did not think there was that much to tightening. I read the whole damn thing.
- If you love that, NASA has a whole 100 page PDF about fasteners:
  
  https://ntrs.nasa.gov/api/citations/19900009424/downloads/19900009424.pdf
  
  One particularly notable part is about split lock washers. They're useless, often detrimental, and need to go away. NASA said so in 1990 and there's no reason to think this has changed.

This is why I'm still on Windows 7.

English is slightly ambiguous here. As tighten has 2 meanings. Turning a screw clockwise is to tighten it, as opposed to loosen it anticlockwise. But it's quite loose. Finally, to make it tight and secure, you tighten it with one last turn.

Shouldn't "screw in the screw" be used instead of "tighten the screw" when you're just inserting it fully but not tightening it?
- Makes sense. You should design furniture manuals for IKEA.