Google is still appealing it, so at best that will happen next year. But yeah, they’re probably adjusting their budget in anticipation.

Mozilla is set up as a non-profit with a for profit company as a subsidiary. The corporate Mozilla handles working on Firefox, mostly using money from Google for setting it as the default search engine. Because of that separation I don’t think they can easily mix those two piles of money together.

There’s this section from their FAQ:

Don’t Mozilla products, like Firefox, earn income?

Firefox is maintained by the Mozilla Corporation, a wholly-owned subsidiary of the Mozilla Foundation. While Firefox does produce revenue — chiefly through search partnerships — this earned income is largely reinvested back into the Corporation. The Mozilla Foundation’s education and advocacy efforts, which span several continents and reach millions of people, are supported by philanthropic donations.

No. It’s got a “source available” license allowing only non-commercial use, and revokes the license for anyone who tries to sue them.

I think they switched to usually using bing results last year. Their support site mentions they use both backends. I’d guess which one you get depends on which API is cheaper for each country.

I think that’s still closed, just poorly done in a way that isn’t very accessible.

That’s what burned in means.

I added an extra line break, but it already looked fine in the default webview and in Jerboa. Normally lists don’t need line breaks around them.

For anyone who wants to know the difference between these terms:

• subtitles - just includes the dialogue
• captions - also includes description of other sounds
• closed - text is stored separately from the video, and can turn on and off while watching
• open - text is part of the video image itself

The biggest thing is probably non-destructive editing, so you can do stuff like apply filters without them changing the underlying image. Gtk3 should add better support for tablets and wayland. There’s also better layer tools and font support. A lot of it was on the backend, which should eventually allow for using other color spaces like cmyk natively.

It’s too bad that GLIMPSE fork never took off.

They’ve been working on porting it since back in 2012, and didn’t want to redo a bunch of the porting work before they even released it.

https://github.com/dessant/buster

None of the options are that great right now. I still mostly use Jerboa, and go to the PWA for things that don’t work. Other android apps you can check out are thunder that has an alpha out, memmy which only has an iOS beta so far, but plans to be cross-platform, and lemmur which is outdated and is incompatible with current lemmy, although there’s a fork with more recent development so it could possibly come back at some point.