Korthrun

Microsoft pivoted to Skype. Saved you a click and reading about 1000 words.

I must have been way out of it late last night. I totally missed that you were asking why people do it and not looking for recommendations. Sorry for the spammy nonsense response to your OP.

To the latter question, I’ve seen devices that do OTP and FIDO in addition to basically storing arbitrary strings (e.g. your cc number).

I get harassment scolding me for using Lemmy to advertise when I mention any of the products by name, despite having no affiliation with any of them outside of being a user, but they’re not hard to find if you look.

I’m curious why your listed options are all software that runs on the internet as opposed to a piece of hardware that you connect to your devices.

Is that just because this is the self hosting community?

Why not a piece of hardware instead of self hosting, cloud hosting, etc?

Tiling WM that you are not sure you want to get into: Sway. It’s a great alternative to i3 IMO.

What I use when I care to put in the effort of setting something up in great detail: Enlightenment. Some may argue that it’s not “lightweight”, but you can readily include only the bits you want, and avoid things like network config guis and system tray apps or whatever it is that you don’t want. Even when you’re using “all the things” which is not technically “lightweight” what it IS is performant. Oh, it’s also very pretty.

In addition to many of the fine points made in other comments I think it’s silly to overlook the power of celebrity worship and weird-ass parasocial relationships with famous people.

There exists a large number of people who aren’t really interested in discussing <topic_x>, they just want to know what <favourite celebrity whos life I have deluded myself into thinking is attainable by me> thinks about the topic so that they can regurgitate it and feel like they’re “the same”.

I’m sure if Chappell Roan or whatever “the kids” think is cool these days had jumped to Mastodon we’d be seeing something very different. TBH I’m mildly surprised that we didn’t see more record labels standing up instances. It’s always boggled me that people have just trusted the service desperately trying to be known as “X” as an authority on identity.

E

Why do people do this? There is neither a clubhouse sandwich or any fries in this image.

This looks like a great lunch but why is it so common to call things what they aren’t? “Fries” isn’t a shape. Apple sticks? Slices? Roughly julienned apples?

Put pork flavoured soy on whatever you want, but why the need to call it vegan bacon ya know?

You’re absolutely right. For what it’s worth, it’s just the first part that’s important.

When you pick up a new concept from a “resource” such as a tutorial, take a minute to explore the concept and understand the semantics of what you’re doing. In the name of illustrating a concept tutorials can often be misleading in subtle ways.

An explanation of my “useless use of cat” example:

The command line has a concept called “piping”. This lets one command send output to a second command. It’s very handy. There is usually also a “cat” command, which will read a file and send the contents where you tell it. This is often your screen, or through a “pipe” to a second command. There is also a “grep” command that lets you search data for certain words.

Many “linux newbie” tutorials combine these tools to show how “piping” lets you send data from one command to another. “cat” some text file, then “pipe” the output to “grep” to search for your words. It usually looks something like cat ./my_address_book.txt | grep Giles to find lines in “./my_address_book.txt” that contain the word “Giles”. The thing is that “grep” can take a file name as an argument. You can just do grep Giles ./my_address_book.txt, and cat is for concatenating files into one. If you want to simply read a file there are more appropriate tools such as “less”. This by the way is the “useless use of cat”

When you’re a newbie though, it may be the first time you’re seeing either “grep” or “cat”. The tutorial is just trying to show you “pipes”. Along the way you’re picking up these “bad habits”. I’ve met professional sysadmins who didn’t know grep took a filename as an argument. It was always “cat blah | grep my_search”. I will see people type “cat /some/file | less” instead of “less /some/file”. It shows a lack of understanding of what these tools actually do, and IMO it just comes down to regurgitating tutorial actions without bothering to understand the semantics of what you’re being shown.

Don’t follow tutorials, understand them. I’m so tired of seeing useless uses of cat because some asshole writing a tutorial 20 years ago decided to illustrate how pipes work with a good ol cat file | grep string as if grep didn’t take a file name as an argument.

The more time I spend being mad about this the more I notice people using horrible practices in tutorials because they’re too lazy to setup a legit use case.

A new user sees this and thinks this is how grep works.

Loops are another common one. People going around not knowing you can pass a glob to a shell for loop. Because the tutorial they read was lazily written and they didn’t bother to understand the bits of what they were being shown, only how to reproduce/mangle the command until they manage to get close enough to what they want out of it.

Configuration management and build automation are definitely worth the time and effort of learning. It doesn’t have to be ansible, find which tool suits your needs.