Using a Firefox clone saves you the hassle of manually remove all the stupid annoyances and user tracking Mozilla enables by default. But thatβs basically it. Except a preconfigured setup and a new name and logo pretty much nothing is different.
Selfhosting is basically free. You already have an unmetered Internet connection, and sourcing some hardware to run Lemmy would also be super easy.
The βproblemβ is that setting Lemmy up is quite annoying and complex and involves multiple docker containers and volumes and networks. There are various installation scripts but it is still a complete mess.
It would also result in a metric shit-ton of traffic and data storage.
From what I researched some time ago: There are/were some federated blogging systems out there but theyβre all stuck in the pre-Docker era installation-wise and technology-wise (i.e. just outdated).
But in the end it makes no sense in my opinion. Blogs nowadays are just publishing and less networking/interaction.
A simple file loader and markdown parser could be enough. I set up my page based on Apache directory listing, a custom Action to parse markdown files, and some fancy CSS. There is figuratively nothing that runs my page, except a web server and a markdown parser.
There are also projects like qutebrowser which allow external programs to be plugins. In case of qutebrowser it uses the Chromium open source platform as rendering engine, etc. but completely relies on external Python scripts for plugins (including ad blocking).
If Firefox goes down the Chrome route with their forced advertisement I can totally see something like this happening.
I wonder how NEW open source project are still hosted on MS GitHub. I mean, yes, legacy projects hosted there are fine (but should work on leaving Microsoft behind) but new projects? Someone using MS GitHub doesnβt really understand the open source culture. Same with Discord (which is neither a support platform, nor a bugtracker, nor a help articles resource).
I won't be surprised at all. They bought an advertising network company and most of their user-tracking always was opt-out and βhiddenβ in about:config and this won't change now.
They also released this pamphlet against an ad-free internet, so instead of being less intrusive with their spam and user tracking, this will become more and more annoying and complex to circumvent.
The sad reality is, there was no significant change when they intentionally crippled the API to fight against ad blockers and there wonβt be a significant change now.
For me personally: Triton. I remember reading it 25+ years ago. I really had to fight through it, after circa half of it I put it away and never touched it again.
So remarkably not my favorite book that I still feel the exhaustion when thinking about it.
The screen capture protocol was merged a month ago.
Thatβs part of my issue I have with Wayland protocols. It was added a month ago. After several years! During research I found discussions ~6 years old, this PR was 2 years old, and superseded a 4 years old other request.
In the meantime some environments implemented that on their own without waiting for the protocol. If I understand correctly: Gnome as well as KDE have implemented it outside the protocol. And Hyprland devs forked wlroots to advance development faster and also add that. (Correct me if Iβm wrong.)
Since labwc uses wlroots (but is a bit slow with adapting to new versions) it will take quite some time before I can put a checkmark after my last usecase. I am optimistic that it will work. But I accepted that it may take several years to add new functionality and a few months before the functionality arrives in wlroots and at some point after that in labwc.
Now, 12 years later, it still is not production ready.
I use it on both my laptop and my desktop computer. It got better during the last 1-2 years.
While my laptop (13" 1080p screen) is pretty much fine running with Hyprland on an integrated Intel GPU, my desktop computer with a 28" 4K screen scaling is messed up completely and needs tweaking, sometimes down to a per-program base. Sometimes the font is gigantic sometimes I need a microscope to see anything. That was definitely better on X11.
On my desktop I run labwc, that does not come with own functionality regarding this: I just recently got whole-screen video recording and now have to wait likely another year or two for single-window recording. (There is a protocol for this, that took two years to be merged, which is just ridiculous for such a low-level base functionality that should be implemented from the beginning on.)
Other than that, all my common programs are running okay with Wayland.
I personally think it is a very bad idea to βspeed run developmentβ of protocols.
Stalling the development of protocols for nearly a decade is bad, too.
They should talk and meet somewhere between βJust develop in production!β and βI personally dislike it for non-technical reasons, so I will block it for everyone!β
I actually just run the update commands individually when I feel like.
bash
su -l 'pacman -Syu' # All regular packages
pakku -Syu # All AUR packages (I know this updates regular packages, too.)
flatpak-update # Update Flatpak packages with a function I wrote
Since I do not trust Flatpak (especially when it comes to driver updates and properly removing unused crap) I once created this monstrosity.
The initial problem with Flatpak thinking it would be a good idea to add dozens of Nvidia drivers and re-download and update all of them on every update (causing a few gigabytes of downloaded files on every run of a normal flatpak update even if nothing needed to be updated) is reportedly fixed, but I just got used to my command.
Absolutely. Theyβre advertised for being used in datecenters, so I assume noise optimization wasnβt a concern for Seagate when creating those drives.
Using a Firefox clone saves you the hassle of manually remove all the stupid annoyances and user tracking Mozilla enables by default. But thatβs basically it. Except a preconfigured setup and a new name and logo pretty much nothing is different.
Vivaldi is just Chromium with a non-free UI.