The licensing fee you mention is purposely fuzzy

I mean, depending on what you mean by “purposely”, I just think there’s no good way in general to determine the exact worth of the use of a trademark.

The restricted assets remain the same as last year: a “tax reserve fund” established in 2005 for a portion of the revenue the Mozilla Foundation received that year from the search engine providers. As noted last year, the IRS has opened an audit of the Mozilla Foundation.

Since the Corporation was founded on August 3, 2005 - this might’ve been the reason? Before the Corporation existed, the Foundation had to receive the money from the search engine providers directly (and the “tax reserve fund” sounds like creative accounting to hold on to that money, potentially leading to the audit), whereas later, the Corporation could hold on to it and pay taxes over it like a regular corporation does.

I’m a Mozilla fan, but I’m not a fan of income inequality, and Mozilla is contributing to it.

I’m with you here, and I’m not saying that the ratio CEO pay:employee pay is a good one. All I’m saying is that the money used to fund the CEO pay could not have been used to fund Foundation projects like Common Voice, as far as I’m aware.

AFAIK the only way money flows from the Corporation to the Foundation is by the Co paying royalties to the Foundation for the use of the Firefox trademark. Obviously exactly how that number is determined is a little fuzzy, but I don’t think it (legally) can be just any number - it has to be justified somewhat. In any case, the Corporation is not short of money, so if the Foundation wanted more money to flow from it to the Foundation, a shortage of money due to CEO pay is not the reason.

(You are definitely right in the sense that Co money could be used to fund more Co projects. Those are not the same initiatives that would be funded by donations to the Foundation though, as money doesn’t flow from it to the Co. Think Common Voice, MozFest, lobbying, Privacy Not Included…)

They wouldn’t. The Corporation is a separate entity, I believe for tax reasons, allowing them to hold more money. I don’t think that it’s allowed to use it as a loophole to avoid regulations that apply to foundations, while still using that money to fund Foundation projects.

Of note is that the Corporation CEO is paid from Corporation revenues, i.e. primarily the Google search deal. Firefox development very likely could not be supported by donations alone, and the Corporation can’t take donations for it.

Donations to the Foundation go to the Foundation’s advocacy work, and projects like Common Voice.

Well, yes, except that those X11 developers agree that Wayland is better.

Notably absent: X11 developer saying Wayland is bad, not X11.

I think it’s just because some things have country-specific formats. For example, if you want to prefill credit card details, you have to figure out how the credit card fields are labelled.

It’s a website rather than an app, but if you open it fullscreen, it’s just as much fun: https://hackertyper.com

I’m assuming you’ve already found it, but just in case you didn’t: Framework has setup guides for Fedora, which presumably should make everything work as intended. Find your device on this page, then click “Fedora 39 Setup Guide” on the right-hand side: https://frame.work/linux

I wouldn’t worry about it too much; there’s not really anything you need to do as a user anyway.

Well, then I’d highly suggest you just use Xfce and not worry about GNOME so much. Xfce hasn’t changed much in years.

they try to reinvent the desktop experience every 2 or 3 years

GNOME 3 was released 12 years ago, and hasn’t changed that much (unless you consider horizontal virtual workspaces are a major paradigm shift somehow).

Just use something else if you don’t like it; no one’s “pushing” anything on to you. Clearly, other people do like it.

“The browser chrome” is the name historically given to the parts of the browser that are not the website. Then Google created a web browser and decided to name it after it - but userChrome.css existed before the browser Chrome did :)

Good to hear, I hope that plays out!

Yeah, that’s fair enough. It’s not just working overtime though - endless toil on never-ending projects, especially when at a certain point, you’re not really making visible progress but rather are just working on a seemingly endless list of bugs and papercuts, is also terrible for motivation. The good news, of course, is that the Pop!_OS GNOME extension also got delivered, which, though a lot smaller than COSMIC DE, I’m sure also wasn’t a small undertaking.

I mean, I don’t really mind - I’m pretty happy with GNOME. All I’m saying is that if I were the project manager, I’d worry about delivering something and not burning people out (“focus is choosing what not to do” and all that, and the last 20% of the work taking 80% of the time). But in the end I’m just a random person ranting on the internet, of course - I do actually hope that I’m wrong.

But a diff viewer in the text editor… It just sounds like folks are eager to jump on shiny new things rather than finishing something, from the outside 🤷 Looking forward to be proven wrong!

No one would want to build applications for a platform that lacks widgets capable of properly displaying, formatting, and editing text.

Is the idea that people are only going to be running Iced applications in COSMIC? It feels to me like the realistic option would be that, if COSMIC ever becomes daily-drivable, people would still be using GTK applications with it, at least at first. Might as well use a GTK text editor then? Then System76 could focus on building a text editor after COSMIC is a thing, and COSMIC would hopefully arrive sooner (or even at all - this looks like the path to burnout).

Note that this is a link to a Mastodon post - commenting here doesn’t necessarily reach @sonny.

Find the original post here: https://floss.social/@sonny/111533945050274953

You mean the ones for a closed and unhealthy web? :P

Maybe they could recommend Windows as well, while they’re at it, haha.

So you’re saying: don’t release the GTK 3 port until colour spaces are also complete? Why not give people what’s ready, and then when colour spaces are ready, cut another release? No need to make people wait who don’t need colour spaces.

(Additionally, it’s easier to verify that bugs reported before the release of colour spaces are more likely to be related to the GTK3 port.)