What hallened to @MannaAero? They announced expansion and then disappeared without saying a thing.
17
Jimbo 🏴☠️ retweeted
The future of #ArtificialIntelligence is not pre-determined. As a technology developed by human beings, its future depends on the choices we make. We therefore have the responsibility to guide, change and, when necessary, reject its applications. A reliable system that serves the human person is of greater value than one that is exceptionally powerful but whose consequences cannot be adequately foreseen or controlled.
Jimbo 🏴☠️ retweeted
Unpopular opinion: the people getting the most out of AI are the ones who could do the work without it.
Jimbo 🏴☠️ retweeted
If you haven’t watched this yet please do.
I don’t care if you are Republican or Democrat, if this doesn’t move you to vote against the current state of affairs nothing will.
Our grandchildren will watch this clip in history class, to better understand the political climate during Trumpism.
Jimbo 🏴☠️ retweeted
EmDash 1.3 is out 🚀
🕓 Readable revision history: who changed what, right in the editor ✍️ The admin's toolbar and image picker when editing on the page 🤖 One switch to ask AI crawlers not to train on your site ⚡ Fewer D1 round trips #EmDash @EmDashCMS theweeklydash.com/emdash-1-3
My new favorite thing from @Calude is when it tells me they created a task to check later. That shit is fire!
18
Wait until you all realize why we switched to CMSs like WordPress. It wasn’t because we couldn’t code. It’s because it benefited our customers. Of course now these platforms are too difficult for our customers to use so I guess do whatever. We did this before.
2
35
Remember the CAN-SPAM Act? Whoever is teaching this stupid outreach tactic obviously doesn't know. I'm going to start going after these for $53,088 per email.
34
Jimbo 🏴☠️ retweeted
WP rocket did badly here. But the official @wordpress account needs to stop shitting on individual parts of its ecosystem.
Terrible look, and deeply unprofessional behavior.
Ouch, telling people not to update... this wasn't a bug in 7.1. Perhaps consider your usage of @wp_rocket. This is also part of the risk of using plugins outside the official plugin directory, which has many alternatives that seemed fine on the 7.1 release day.
















