I think there’s an element of prestige people are missing. At least in my country there were online options prior to the pandemic even, they however lacked the prestige / name recognition that other institutions had. Keeping mandatory in-person classes is another way to maintain this prestige, a differentiating factor, from the other institutions.

I also have to agree with most of the comments here. From an instructional point of view online classes are lacking, they can be less engaging, and pedagogically neutered. And in fields with lots of laboratory work, it’s frankly impossible to get rid of at least part of the in-person educational component. Even for the humanities, having access to a large on-campus library of scholarly resources is integral to research.

In my personal experience I’ve been quite grateful to have access to a large archival collection, items that could not be shipped to remote students because they are too old to leave a temperature & humidity controlled environment. An online experience would prevent someone like me from doing some manuscript / original publication related research.

Now, I do think online options are helpful. ESPECIALLY for summer classes, where students may wish to retake a class while also moving away for summer work. But I do not think they should become the default, they should be an option where possible, but not the new normal.

Normally I would say community forks have the power to continue the project. However, in this case I think chrome / safari would eventually add enough new features that Firefox forks can’t add quick enough. Mozilla at least has some power in pushing the direction of web-standards, which these forks would lack, as well as the larger development team and some corporate usage of the browser which Mozilla has. I also don’t see the smaller development community keeping up with security issues found in the browser, particularly pertinent for corporate marketshare and individuals with a stricter threat model (journalists, dissidents, etc.)

The only other factor, is whether Firefox dissapearing would officially create impetus for an anti-trust case against Google. I doubt so under the current American presidency, but I could see the EU being concerned (even if they lack the power the US has to force the company to split). If something were to happen here there would be substantial change in the browser market, but I wouldn’t be too hopeful of this happening.

What are your goals?

I would say it’s really a combination of the instances policies and their jurisdiction, and in terms of jurisdiction it also depends on where you live (e.g. you may have more protections under law if the instance is hosted in your country)

There’s also nothing stopping you from using multiple instances — siloing your interaction in different types of communities in different accounts on different instances. This may be useful if part of your privacy concerns are having all of your post / comment data on one account on one instance.

Edit: You can also use an email aliasing service to avoid even giving your email out. There are aliasing services such as Addy.io, Simplelogin (subsidiary of Proton AG), Firefox Relay (Mozilla), as well as some email providers which provide (iCloud, Proton, Mailbox.org to name a few)

If you don’t mind me asking, what makes gnome more adaptable in terms of functionality than KDE?

For iOS devices the most up to date client is “Strongbox”. I don’t think it is FOSS, but is compliant with the standard. It’s sadly a freemium app, but is quite well made in my testing. It cannot sync with syncthing, but does support several cloud services, its own service (which uses iCloud), and local file transfer over LAN. They also have a version of the app with all network connectivity removed for security (if you prefer)

This is perhaps overkill, but you can also encrypt the contents of your online cloud storage with CryFS / Cryptomater. This is particularly useful if you wish to store sensitive documents (healthcare, finances etc) in a cloud environment in case of catastrophic destruction of property (destroying computers / on site backups of data).

In this case you can also backup your keepass file in this encrypted virtual storage medium, on top of the prexisting encryption of the database itself.

My personal choice right now is KeePassXC (PC) / KeePassDX (Android) + Syncthing And Aegis (Android) for 2FA codes, with a yubikey for services that support FIDO keys.

Overall I like this setup because it’s decentralized and does not rely on a third party server structure. The only “weak” point would be the Syncthing relay servers or the Tailscale VPN that I use, but this goes back to ensuring encryption of the database is adequate with a long password, and using an open source synchronization protocol that ideally has been vetted by a trusted third party (or yourself if you’re capable)

I used to use Bitwarden, and I highly recommend it. I really appreciated it’s ability to integrate with email aliasing solutions to generate new aliases from within the bitwarden UI itself. However, my main reasons for switching were the following

• I don’t have the money to pay for it (uni student)
• I prefer a more self-hosted approach (I will consider using vaultwarden in the future when I have more money)
• I wanted to move away from using a browser extension for password management on desktop. KeePass’ auto type feature is really good, and a more secure input method than a browser extension autofill.

The only additional advice I have for both recommendations is that I do not think it advisable to add Totp 2fa information to your password manager even if it supports it. I feel like this should be separate, on a single device, and backed up in ~2 locations (one preferably off site). This is really to avoid problems if a device is compromised and if your password manager is compromised, but this is definitely in the more unlikely category I feel.

My only major issues with keepass are the potential for sync conflicts and the some feature differences between platforms. A centralized server config like vault/bitwarden prevents the sync conflict issues, at the cost of having one point of failure. The feature differences problem isn’t too great, but autotype doesn’t work on Linux if you install with flatpak, and you can’t prevent screen capture of the app on Linux (only on Android and Windows from my understanding)

Edit: I also tried gopass, it’s really fun to have an entire CLI based password manager, but frankly the state of mobile companion apps are appalling. The Android option only is good if you use a dev version, and the iOS one I thought was just ok. I also dislike the metadata leaking that is inherent to the format, and that PGP is the main form of encryption for the time being (some clients were looking at using AGE at some point). Overall it’s a cool but flawed concept, and I feel my other two recommendations are superior.

I think it’s important to see these types of efforts, while I’ll never go out and buy a MacBook the effort isn’t wasted since it gives current users more freedom and future people buying used laptops more options for Linux compatible hardware.

Without a project like this, that hardware will end up being e-waste a lot sooner than it should be, when Apple drops support. At least to me I see an ethical and moral imperative for projects like this, but I also understand people’s grievances with Apple.

I think you summed up my thoughts on the matter much better than I could have. In particular, the “digital” / “corporate” right to be forgotten is distinct and much more specific in its scope than a broader right, and is a rather important consumer protection in my opinion.

I have a few shortlisted

My parent’s 2010 Ram 1500, the interior is rather comfy but the reliability is just not there. At 100k km the engine blew up, apparently this is still an issue with the current ones as the 5.7L V8 still has the same flaw allowing for some components to drop into the cylinder. There’s also been random electrical components that have died relatively fast, and whatever metal was used rusted exponentially even with rust proofing being applied twice a year. It had more rust than their 2011 Toyota Highlander that had greater than 300k km

I also just hated when I had to drive it downtown, but I can’t exactly blame the vehicle for that.

2011 Toyota highlander, it went through 3 transmissions, 5 rear wiper motors, and it was about to go on to its 4th transmission when they sold it. The 3rd one didn’t even last much more than a year.

2006 Rav 4 (V6), this car also went through 2 transmissions, and then had to have the entire steering column replaced by year 2

~2016 Ford Fusion, this was a rental car for when my Civic was being repaired after an accident and my god was it awful. It handled like a massive boat despite being a medium sized car and the transmission felt significantly less responsive than even the CVT in the honda. The seats also sucked but i think that was how the rental company cleaned them, they made this awful noise every time you sat in them and looked and felt like a “casting couch” with several generations of children dried up in them…

Honorary Mention: my friends Nissan Versa, seemingly unreliable and falling apart but it refuses to ever give up. That thing will survive nuclear winter, and will remind you with every pothole that its existence is torture.

I understand why they wouldn’t want to suddenly change the branding of existing projects though.

I’m not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won’t immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.

I feel that I am 50:50 on it, immutable at least conveyed more information about what it is while Atomic feels a lot more “buzz-word-y” and does not convey as well what it means. Regardless, I’d say the bigger issue is keeping the old Silverblue & Kinoite names, they really should change them even if it means having a ~2 year period of having “Formerly Silverblue / Kinoite”.

Thank you for the very thorough reply! For god knows what reason I get this error: error: app/org.mozilla.firefox/x86_64/stable not installed when running the xdg-open firefox-reader command, yet manually running flatpak run --user org.mozilla.firefox about:reader?url=https://example.com works just fine. I’ll have to troubleshoot it when I have a bit more time ;p

Thanks again for your very thorough write up and the linked articles. Have a good day :)

Update: It seems like on my system, the --user flag was the issue, removing it made the script function. I am using Fedora Kinoite (Immutable version of KDE Plasma), so perhaps it is just a difference in how flatpak is configured between distros? I’ll have to read into it more later.

I’ll keep my answer focused on KDE Connect as I no longer use a TWM. You can most definitely use KDE Connect in non-Plasma environments. For non-Plasma (and non-Gnome ^* ) environments you can just install the kdeconnectd package. Then, to start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd. You can schedule this to autostart as a systemd unit, or in the config for your TWM (I know in sway/i3 you could start it, I’m assuming it is similar for many other options)

If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. If you use firewalld specifically, there’s an option to enable KDE Connect rather than manually specifying it. This also let’s you have it only work on private networks and not public if you so chose.

See Arch wiki for more details

*For gnome I would recommend using gs-connect even if you have a tiling extension

£ KDE-Connect: does that work on TWMs? Is there a good implementation? Can I use GSConnect elsewhere too?

I’d much rather use a separate Firefox (now Mozilla I think) account for my professional work. I also would prefer having separate extensions, notably Zotero connector is kind of useless for my personal browsing

I usually do 19C in the winter, and 24C in the summer, my parents do 22C (72F?) year around

Most of the documents I produce are converted to PDF or printed, so I use Nimbus Roman or Nimbus Sans (I believe). I do use Open Dyslexic font

For UI I really enjoy Inter, although Ubuntu, Roboto and IBM Plex Sans are also nice

For terminal I use Hack, although Source Code Pro is nice

I always assumed xeyes was made for that exact purpose, somewhat funny that it was not designed for this.

I have not personally tried it, but here they describe it as being alpha software.

Of course, that alpha designation could be unwarranted, I do not know.

archive . org link

I am sticking around for the time being. While it is a community project, Red Hat is still the legal entity representing it and is a sponsor of the Fedora Project. I am confident that Fedora will continue to exist (or if RedHat ruins it, the community would fork it), consequently I feel that this is more a question of morals / ethics or desire to distance oneself from Red Hat products. With switching you would likely be giving up either KDE or immutability, until OpenSUSE’s Kalpa matures more. Regardless, I’m not sure how much benefit Red Hat gets from you being a Fedora user. Unless you contribute to the project itself or are using Fedora as a means to gain more knowledge for using RHEL products in enterprise.

Some relevant articles for people interested; Fedora Project Wikipedia governance section, Fedora Project Wiki regarding the proposed “Foundation” and the mailing list discussing the “Foundation”.

I highly recommend silverblue! The only thing that can be frustrating is Steam and other game related things, particularly with wireless controllers it seems. But overall it makes it very hassle free imo.