There is a serious problem when a profit--making company provides Operating System software:

Deliberately giving limits to a present version allows the company to charge a lot for a new version, even if the new version provides few important benefits.

We need a book that explains how AI technology functions.

There is a huge amount of news and comments, but apparently nothing that helps people understand how AI is developed, and functions.

Talk shows have been exempt from the equal time law right up until 2026. We didn't vote on it. Congress didn't change anything. Trump just decided they can only interview candidates that are nice to him.

I don't think that's how the law is actually supposed to work.

Matt Mullenweg has done a lot for free and open source software as a communication platform, so it has been sad to see all this play out (crossing my fingers not as badly as with Ian Murdock of Debian though). Here are some health-related suggestions I've collected that may be useful for him or anyone else who can be hyper-focused and spend too much time indoors and on the computer and not emphasize good nutrition and exercise and face-to-face community so on:
https://github.com/pdfernhout/...

That said, and with all due respect for Matt's past accomplishments in forging a community and a company to support it, I think Automattic (and so Matt) made a terrible choice around 2015 by deciding to use Slack for internal and even external communications instead of just using WordPress with the 02/Oxygen plugin previously used.

I wrote about that at length when I was applying for a job at Automattic circa 2015.The gist of that concern is on the main page of my website and says:
        "And here is a link to a no-doubt overly-long and overly-enthusiastic job application document as essentially a programming and FOSS autobiography intermixed with ideas about how what I had learned over the years could help Automattic (the main developers of WordPress) -- or, to some lesser extent, any other large FOSS effort, including Drupal/Acquia. After waiting a couple of months in the Automattic interview queue, that application fizzled over whether I was willing to use Slack for the job interview at Automattic. My reason for concern over Slack use at Automattic was that, as good as Slack is, the proprietary venture-funded Slack is disrupting the open-source communications ecosystem which WordPress is a big part of. I enjoyed writing that application document overall, and I still hope some of the ideas in it can still help Automattic grow even more in a FOSS direction (or other similar companies like Acquia with Drupal). That document is at least something for my kid to perhaps read someday many years from now. Of course, my kid may just read it and then say, not without significant justification, that I probably should have put the principle of family ahead of other principles in turning down any significant chance for a six-figure salary work-from-home job on FOSS. :-( We always have many principles to choose from, and it can indeed be hard sometimes to get the priorities right. As Scott Berkun (who left Automattic after a year to go back to writing full-time) wrote, even in a metrics-driver organization like Automattic, there is no metric for picking metrics or deciding how to weigh a variety of metrics (beyond perhaps survival itself).
        Here is a version of Twirlip I started as a proof-of-concept Thunderbird Server webapp to handle email, chat, and other real-time communications as another step towards a social semantic desktop. It is the beginning of the embodiment of the "ThunderbirdS Are Grow! Manifesto". But if you are looking for something good now that is FOSS, check out Mattermost, Matrix.org, Mailpile, Kolab, and similar things."

An archive page of that job application and Slack comments from back then is here, includign with the section on transcending polling in WordPress:
"Automattic JavaScript Engineer application by Paul D. Fernhout"
https://web.archive.org/web/20...
      "But there is an alternative to trying to shoehorn WebSocket-related changes into the WordPress core PHP somehow. Such an update notification service to reduce polling could instead be hosted at WordPress.com in parallel to a WordPress server for a fee for those who don't want to run Node.js (or whatever) locally to supply that service. ... Such a WordPress feature to reduce polling needs might then be used to add near-real-time chat to WordPress. This might reduce the otherwise increasing desire for Automatticians to use Slack to communicate with each other about WordPress. That is a movement that seems problematical to me concerning WordPress's future. It would also be like Automattic moving to Pusher instead of improving WordPress to be low-latency and near-real-time. Even if Slack (by all reports) is a great product (as proprietary products go) that can monitor and log and search all of your communications stored on their servers, in theory using Slack widely within Automattic makes Automattic's internal communications available to the same proprietary competitor (if even just rogue employees) for business intelligence purposes. It also seems strange to me for Automattic to cede the area of near-real-time communications to a proprietary company without at least trying (really hard) to come up with an alternative built into WordPress, especially because such things have already been shown to be workable. I feel Automattic could (and should) be innovating in this area to help the WordPress community move in new directions. ..."

A fundamental issue is that people at Automattic at the time saw WordPress' competitors as things like Wix, not things like Slack. I was reminded of when in the 1990s ParcPlace (a Smalltallk vendor) thought Digittalk (another Smalltalk vendor) was their main competitor and disastrously bought them while ignoring that Visual Basic and Delphi and similar products were really their big competitors (which I had warned someone in sales there about about). WordPress could have become the premier chat platform for companies (including using ideas for a near-real-time message updates relay server leveraging technology someone at Automattic has written). But instead Automattic and the WordPress community it shepherds moved to Slack. Just a very sad way to see a great FOSS community focused on communications destroy itself by embracing proprietary software. And it seems like Matt played a big part in that short-sighted decision somehow (maybe having friends who worked at and.or funded Slack judging from some of his bloig posts long ago)?

Here is a more general essay I wrote in 2016 on why not to use Slack for free software development (in part trying to explain to Richard Stallman of the FSF why Slack was such a threat to the free software movement):
"Reasons Not to Use Slack for Free Software Development"
https://pdfernhout.net/reasons...
====
Contents
* Introduction and summary
* What is Slack? (A proprietary centralized communications hub web service )
* Free alternatives exist to the proprietary Slack
* Automattic/WordPress is sending the wrong message about free communications software
* Slack can change its TOS at any time
* Slack can cut you or your community off at any time
* You need to be online to use Slack
* Slack copies the contents of secret URLs
* Slack makes government surveillance easier
* Slack is a single point of failure for your community
* Slack's privacy policy guarantees very little
* A democratic government is a special case of a free and open source community
* Slack is focused on teams, not communities
* Slack limits are not advertised (like 5000 users maximum per "team")
* It costs a lot to search or delete older messages
* Your Slack discussions for free software projects are not public or findable
* Slack private messages may not be very private
* Slack may change ownership at any time
* What if Slack went free/libre and open source?
* Standards unify; incompatible services fragment
* The cost of changing later can be high
* Matrix.org is a better way forward
* Would I ever use Slack? Sadly, yes. :-(
====

Tangentially, I also tried to get Automattic/WordPress to use Mithril instead of React back when React has problematical licensing relating to patents... In the end though Automattic and Matt had enough clout to get Facebook to change the React licensing terms (even though I still feel Mithril has a better conceptual design with better developer ergonomics than React).
https://github.com/Automattic/...

Anyway, I'll never know if WordPress and Automattic might have gone in very different directions if I had gone to work there -- or if I just would have become frustrated and bitter from still seeing it all play out the way it did despite my best efforts there (given social momentum and power structures)?

For example, it took five years to get this memory exhaustion and crashing bug I reported in WordPress fixed for when you edit a long page too many times (which I discovered while writing that job application). That is a bug which may have cost the entire WordPress community many millions of dollars a year paying for bigger servers with more memory than they really needed to avoid the problem, compared to if the bug had been fixed sooner:
"High memory usage ( and possible server error) editing post with many/large revisions"
https://core.trac.wordpress.or...

P.S. Sad anniversary of September 11 today and the destruction of technology used for social advancement in Chili in 1973 (as another example of politics and personality disrupting humane tech progress as with WordPress):
https://en.wikipedia.org/wiki/...
        "Project Cybersyn was a Chilean economic project developed from 1971 to 1973 during the presidency of Salvador Allende (1970-1973), with the purpose of constructing a distributed decision-support system to aid in the management of the national economy. The project consisted of four modules: an economic simulator, custom software to check factory performance, an operations room, and a national network of telex machines that linked to a single mainframe computer. ... The principal architect of the system was British operations research scientist Stafford Beer (1926-2002), and the system embodied his notions of management cybernetics in industrial management. One of its main objectives was to devolve decision-making power within industrial enterprises to their workforce to develop self-regulation of factories. ... Project Cybersyn ended following Allende's removal and death during the coup detat of 11 September 1973. After the coup, the Chilean military abandoned Cybersyn and destroyed the operations room.

https://en.wikipedia.org/wiki/...
        "According to historian Sebastian Hurtado Torres, there is no documentary evidence to support that the United States government acted actively in the coordination and execution of the coup actions by the Chilean Armed Forces from September 11, 1973 itself. However, Richard Nixon's interest from the beginning was that the Allende government would not be consolidated and intervened in the conditions prior to the Chilean coup of 1973. Historian Peter Winn found "extensive evidence" of United States complicity in events that helped in part to create the conditions that led to the coup. However, given the local political polarization and the performance of the Popular Unity government, there is no academic consensus on whether this intervention--which primarily took the form of financial support for the media, political parties, and opposition organizations--played a decisive role in the events of September 11, 1973."

https://en.wikipedia.org/wiki/... "The android officers are ordered by Central Command to cease pursuit, on the grounds that the expense of his capture exceeds their allocated budget for THX."

So maybe there is hope for humanity after all in token budget limits? :-)

Another source of hope is humans and Ais learning to laugh at the irony in my sig: "The biggest challenge of the 21st century is the irony of technologies of abundance in the hands of those still thinking in terms of scarcity."

Hows this for more serious job market stats?
"Nearly 25% of U.S. workers are "functionally unemployed," economic analysis finds"
https://www.cbsnews.com/news/f...
        "The U.S. job market is less robust than it looks, according to a new analysis.
        The nation's unemployment rate fell to 4.1% in July, well within the range economists consider healthy. Yet that measure, which reflects the percentage of people 16 and older who don't have a job and who are looking for work, is an imprecise metric that fails to offer a full picture of the health of the job sector, according to Gene Ludwig, chairman of the Ludwig Institute for Shared Economic Prosperity (LISEP).
        The economic research firm's "True Rate of Unemployment" (TRU) seeks to capture the share of workers that the group defines as "functionally unemployed." This includes not only people who are unemployed and looking for a job, but also those who are involuntarily working part-time and who are earning poverty-level wages, or less than $26,000 annually before taxes.
        Functional unemployment across the U.S. has climbed four straight months and stood at 24.9% as of July, although that's down from 25.2% in December, according to the Ludwig Institute. ..."

Shadowstats has some similar unemployment numbers:
https://www.shadowstats.com/al...

To me, these sorts of huge (but often ignored) unemployment numbers reflect the continued playing out of larger trends like I outlined in 2010:
"Beyond a Jobless Recovery: A heterodox perspective on 21st century economics"
https://pdfernhout.net/beyond-...
        "This article explores the issue of a "Jobless Recovery" mainly from a heterodox economic perspective. It emphasizes the implications of ideas by Marshall Brain and others that improvements in robotics, automation, design, and voluntary social networks are fundamentally changing the structure of the economic landscape. It outlines towards the end four major alternatives to mainstream economic practice (a basic income, a gift economy, stronger local subsistence economies, and resource-based planning). These alternatives could be used in combination to address what, even as far back as 1964, has been described as a breaking "income-through-jobs link". This link between jobs and income is breaking because of the declining value of most paid human labor relative to capital investments in automation and better design. Or, as is now the case, the value of paid human labor like at some newspapers or universities is also declining relative to the output of voluntary social networks such as for digital content production (like represented by this document). It is suggested that we will need to fundamentally reevaluate our economic theories and practices to adjust to these new realities emerging from exponential trends in technology and society. ..."