As I’ve said elsewhere: I wonder what controls Mozilla has in place to prevent gradual takeover of their board by those with an interest in removing Firefox as a competitor. We’ve watched the sleeper cell in the Supreme Court transform that body into an illegitimate partisan puppet. Mozilla’s actions over the last few years would make much more sense if it were being manipulated into self destruction.
19½ months. That’s how long Mozilla was prepared to listen to a small, unfiltered subset of their users, for a laughably meager maintenance cost.
Yep, which further highlights the problem: @mozilla@mozilla.social 🔗 https://mozilla.social/users/mozilla/statuses/113153943609185249
We’ve made the hard decision to end our experiment with Mozilla.social and will shut down the Mastodon instance on December 17, 2024. Thank you for being part of the Mozilla.social community and providing feedback during our closed beta. You can continue to use Mozilla.social until December 17. Before that date, you can download your data here (https://mozilla.social/settings/export), and migrate your account to another instance following these instructions (https://support.mozilla.org/en-US/kb/mozilla-social-faq).
This was also my recent experience on PopOs!
There’s a little historical baggage, but look at Windows: multiple letters for drives, and all of the paths can be modified, so you have to ask Windows where any important directory is physically mapped (like SystemRoot or Documents or Temp or Roaming AppData or many others), because it doesn’t have this nice consistent structure like Linux. Linux presents a logical layer and manages the physical location automatically. Windows makes you do the logical lookup yourself, but doesn’t enforce it, so inexperienced programmers make assumptions and put stuff where the path usually is.
That’s part of why logging in to Windows over a slow connection can take forever if you have a bunch of Electron apps installed: they’ve mismapped their temp/cache directory under the Roaming AppData, so it gets synched at every login, often GiB of data, and they refuse to fix it.
Touché.
Not a problem for the FRC, and 2023-W20 compares just fine with 2024-W20. Same part of the year, and the weekend is in the same spot.
If that were true, intercalary months shouldn’t have been necessary.
Months are the craziest, weirdest, stupidest measure humanity has used for this long. ISO8601 week dates make more sense, or even the French Revolutionary Calendar. Humans organize all of society by weeks, not by months. Compare last January to next January, or last February to next February for metrics. Do they have the same number of weekdays vs weekend days? Even if they do, do they happen at the same point in the month so you can compare the flow of the month? Now compare two weeks, and that’s apples to apples. Group by weeks instead of months and your irregular, bumpy graph smooths right out. We only hang on to Gregorian months out of inertia.
I wouldn’t even notice it as unusual, even though it isn’t my usual order. It could vary by region or profession, or maybe it’s just you that notices it this acutely. In plain English emails and other narrative text, I always use “Sat Aug 31” (adding the year only when ambiguous), which is short but complete, and includes the day of the week, which is much more important to humans than the month anyway.
While true, the growth of the economy has been wildly outpaced by the rate of hoarding at the top. After all that extra work, how much better off was your dad after everyone above him benefitted?
It’s the same argument I’ve heard about the “complexity” of Mastodon: too many choices, which is I guess why people largely stopped going to websites outside the major social networks. Monopoly over competition, it’s like everyone is pining for a monarchy.