My uncle in Oregon can't get into his laptop because his Microsoft account got b0rked and the bloody 2FA won't let him log in because he registered it to his home phone number without thinking about it.

I really want to grab some microsoft exec by the giblets and swing them around until they reach orbital velocity.

My utter disdain and hatred for that ruddy company has ripened and reached 180 proof over the past thirty years.

@RL_Dane
Ah, I remember when my Windows laptop enabled FDE without telling me then locked me out of my account, saying my password was incorrect. I couldn't do a reset without the key unless I willing to lose my data.

I waited literally 7-9 hours in a queue to *virtually chat* with a Microsoft representative. He told me that the key should be backed up to my account.

It wasn't. I lost all my files that weren't synced to GDrive, including the first 43k words of my in-progress NaNoWriMo novel.

@RL_Dane
This is (1) when I made Ubuntu the primary install I'd use rather than just a dual boot I had for kicks and (2) the main inspiration for why I now run hourly backups on most of my data.

@RL_Dane
Anyway, here I am a couple years later and I don't use a single Micro$oft product that I'm not required to for uni. No GitHub (except issue reporting), no npm, no Windows, etc.

@RL_Dane
And never will I recommend a Micro$oft product to anyone.

@benjaminhollon

Word.

@RL_Dane
Not sure whether the next step should be de-Applifying or de-Googling.

@benjaminhollon @RL_Dane I would say De-Googling is probably of higher imperative than de-Applifying, but I'm an Android user, so they basically own me.

@gordoooo_z @benjaminhollon

De-Google your Android!

@RL_Dane @gordoooo_z
Not sure I've ever understood going half-measures; for example, using degoogled chromium rather than something else altogether, like Firefox. If I ever switch away from a mainstream mobile OS (which I hope to someday) it'll almost certainly be to a pure Linux-based system.

@benjaminhollon @RL_Dane Degoogle Chrome is a terrible time. I just jumped straight to Firefox myself, which overall is a pretty good browser. Most of the problems I've experienced are the result of devs not testing for Firefox :/ Android on mobile is not quite there yet. I plan to get one anyway, but idk if it's ready to be a primary device.

@benjaminhollon @RL_Dane *Linux on mobile, is what I meant to say

@gordoooo_z @RL_Dane
Yeah, might be worth trying. I think I could actually make it work if not for a few apps I have to have for uni; I don't use my phone much.

@benjaminhollon @RL_Dane Honestly I probably could to. The majority of what I use my phone for is browsing. Unfortunately I do all my business communication on WhatsApp though, so that would be a problem.

@gordoooo_z @RL_Dane
Yeah, that could be tricky. I wonder if it would be possible through Waydroid (https://waydro.id/).

@benjaminhollon @RL_Dane might be, but sounds like an exercise in frustration lol

@gordoooo_z @RL_Dane
Well, I plan to at least try it out on my laptop and see how well it works; I know for sure anything requiring a phone number wouldn't work that way though.

@benjaminhollon @gordoooo_z

The good thing is that you're already on Wayland. I have zero plans of switching. Just too many things to re-learn. We needed a new-and-improved X12, not a glorified framebuffer with a quarter of the features, *grumble* (As always, we write code for Gnome, begrudgingly support KDE, and flarg the rest of the world that just use X)

...

@RL_Dane @benjaminhollon @gordoooo_z Wayland kind of is X12. With a new major release of a program the api is likely to change, which requires programs that were using it to be updated.

It's not complete yet, but already usable for some people.
The reason it seems to work better for gnome is because gnome does everything their own way instead of creating standards, like wlroots and kde are doing.

Many applications require specific environment variables to be set to determine if they are running on wayland, but these are often not set, causing them to use xwayland instead (which breaks things like screenshot tools and screen recorders).

Other things that come to mind are the lack of nvidia support and global hotkeys.

It's not quite ready yet for most people, but it will probably be in a few years.

@Haijo7

My problem is that instead of implementing a lightweight X, it's completely new and different, as if nothing other than the major DEs amount to diddlysquat.

Then again, I appreciate the fact that a lot of the Wayland devs are former XOrg devs, and this is the best they felt they could reasonably do without a herculean effort, so

@benjaminhollon @gordoooo_z

@RL_Dane
Instead of clunky DEs, try Sway — that's what SWMO is based on I think. It's lightweight and blazingly fast, scrolling is butter-smooth on Wayland. If your hardware is well supported, it's perfect. I use it on two different laptops running Void and I'm very happy with it. Both use integrated Intel graphics though, I'm not sure how things are with discrete GPUs.
@Haijo7 @benjaminhollon @gordoooo_z