Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Matt Mullenweg Profile picture
Matt Mullenweg
@photomatt
I can think. I can wait. I can fast.
2 subscribers
Apr 23, 2023 • 5 tweets • 2 min read
Why I just paid for Twitter Blue:

1. I think Twitter is great and want to see it succeed. I learn a ton on here.

2. I want to see subscription models work for social networks, we're also attempting this on @tumblr. 3. I believe in collegially supporting competitors. We're fellow travelers and it's not zero-sum.

4. I spend at least 30 min on this site a day, and I can afford $8/mo. That's like $0.50 an hour. It's a great deal.
Apr 17, 2022 • 4 tweets • 2 min read
This is why, for better and worse, @WordPress and other open source platforms are the only thing that give you true freedom. They can take away your ISP, but the code is public. Your data is perfectly portable. So freedom of speech understood as freedom to publish is there. Now freedom of speech understood as freedom of distribution will never truly exist as long as there are intermediaries where you don't control the code, including telecoms (bandwidth and phone numbers), Gmail, supply chains, etc.
Jan 9, 2022 • 6 tweets • 4 min read
People seem to be redefining Web 2.0 as Facebook, etc, that own data, but Web 2.0 at the time was platforms like WordPress, Odeo, Six Apart, Flickr, Technorati, and del.icio.us that had open data and interoperated. flickr.com/photos/ross/49… I don't disagree with anything else in @brianarmstrong's thread, it's just a trend that retcons web2 to be regressive when the same goals (interoperability, openness, decentralization) were there. To be fair, Web2 probably did the same thing to Web1 in 2005.
Aug 23, 2020 • 4 tweets • 1 min read
I am very grateful that folks at Apple re-reviewed @WordPressiOS and have let us know we do not need to implement in-app purchases to be able to continue to update the app. Bad news travels faster than good, usually, so please consider sharing that they reversed course. I did not expect the previous tweet to get attention outside the WP community. My understanding was the previous decision was final, and we had already made many of the arguments people suggested privately over the several weeks the app was locked.
Aug 21, 2020 • 6 tweets • 2 min read
Heads up on why @WordPressiOS updates have been absent... we were locked by App Store. To be able to ship updates and bug fixes again we had to commit to support in-app purchases for .com plans. I know why this is problematic, open to suggestions. Allow others IAP? New name? New name: The app has always done a ton of work to support WordPresses hosted anywhere, using the XML-RPC API included in core WP since WP 2.6 was released in 2008. That's why we called it "WordPress" and not "WordPress.com" or "Jetpack."