This looks interesting. At one point I wanted to use a third party library using luarocks, but I gave up because it wasn't immediately working/straight-forward.
It may have been a skill issue though...
I actually prefer the "when it's done" model rather than the "train leaving the station" model, for software like this. I feel it better allows for broad-scope changes, which may touch large swaths of a codebase, to more fully gel/mature before being released. For something that I might only update once every few years anyway (ie: not very security-critical), it seems worthwhile to reduce the overhead of release process/logistics for the developers, letting them spend that time on features/fixes instead.
Or maybe there was another model you were suggesting? What do you find non-sane about the current one?
They basically stopped doing the previously-usual updates for a 7 years to focus on porting to GTK+ 3; GIMP was very tied to GTK+ 2. There were a bunch of much-anticipated features (esp. non-destructive editing) that were finished but couldn't be released because it was half-way through the big GTK transition.
Hopefully the now-impending port to GTK 4 will be a lot smoother and won't be such a disruption to their ability to ship the features they've been working on.
People seem to forget that GTK was originally created for GIMP, Gnome came around and co-opted it since it was more free (libre) than QT.
GTK3 was a full rewrite divorced from the GIMP development cycle so broke a huge chunk of things GIMP put in place specifically for their code styling. Thus the long development cycle.
The problem, like most things with GNU itself, is that large dreams are thought of but never actualized. So, just like using the Linux Kernel vs Hurd, the GNOME project had to plugin what was available; and that was GTK.
If those fixes take years to get released, that's not really a good thing. One year with bug fixes is typically okay unless you're dealing with hardware.
From the release notes: "we also intend for minor releases to be much more frequent. Rather than having another 6+ years development schedule for GIMP 3.2, we plan to release it within a year of 3.0".
As a user of a Firefox-based browser, YouTube's performance really is hit or miss. Sometimes it's ok, other times it's barely useable.
These days I simply queue up videos in mpv. It is much lighter on the resources, and also provides a nice cache that makes seeking through videos a breeze. I can open a link straight in mpv using a very nice system[1].
Once I have an mpv instance open I simply drag links on top of it to enqueue them. (shift+drag if you haven't set the following option in your config: drag-and-drop=append)
It works so well I find myself doing it for other online sources of videos too (e.g. Twitter/X, local TV websites, ...)
I use h264ify plugin and didn't see performance issues for playback. The UI depends on test group you go into, but only the first load is really terrible.
I would only donate for firefox specifically, when given the promise that it would be spent on development. Never to Mozilla with all the weird stuff they fund and work on.
It's not, It's adding a global variable called _gaUserPrefs to every site. If the actual GA script is loaded it would look for this as the opt-out signal.
Of course any other tracking (or GA tracking) could use this as a part of fingerprinting.
Yes, if you use googles products to block googles products you have to trust google.
My main point is that the extension itself does not load GA, which the parent seemed to say. It can also be used for other fingerprinting since it is a variable accessible by other scripts.
Continent is a mass of land, it can't have values. E.g. countries on the European continent include Turkey and Russia. European Union on the other hand explicitly declares shared values.
Looks really nice. I do have my doubts about the ergonomics of it though. Once you've had a taste of concavity and column-staggering nothing else feels the same.
That's how I feel about keyboard tilts away from a full pronation/flat and towards a neutral position. Once I switched to having a rotated split keyboard, my forearms and wrists felt incredible, and I hadn't even considered them uncomfortable before.
I really hope the Ladybird browser project succeeds in the next few years, because it seems that Mozilla is digging Firefox' grave deeper with every step they take.
I think the main issue in this case is that the maintainers provide an official flathub entry themselves. People using the fedora flatpak are not aware that they are using an unofficial (and incomplete) package, and then go to upstream with their issues.
