@stux@pfefferle I'm thinking about deleting the blog from Mastodon.Uno, keeping it up and running just into #ActivityPub and this account is my personal one. So, I can get rid of #JetPack for autopost on Mastodon at least, keeping me all slots for letting me keep social autoposting free feature's limitations sufficient.
Can anyone personally recommend a self-hosted stats package which works with WordPress and doesn't require JavaScript? All I need is per-post counts. I don't care about anything else.
Looks like the only things I use #Jetpack for are:
🔒 Firewall. Can be dropped. Protected elsewhere.
🔝 Uptime monitoring. Ditto
📈 Stats. Now paid. But the API is still free.
📨 Newsletter. Can't be arsed to find a plugin for that. Still free (for now).
🔄 Related posts. Still free. Widget is garbage so just using the API.
📝 Markdown editor. I can probably get a plugin for that.
I'll slowly wean myself away from Jetpack. Bit of a shame, but probably about time for me.
To add to the furor of this week's skullduggery in "Nobody Catches A Break"--what's the substitute for the #Jetpack plugin? Only had it for the security whatchamacallit, and it would be nice to continue having it with some other plugin :P
So if anyone thought the entire #Automattic#AIPartnership shanda was going to reflect badly on Automattic's other products, after reading through dozens of Toots and blog posts, the answer is a resounding YES.
Can anyone from the WordPress Jetpack team comment on how the Enhanced Distrbution module, activated by default and feeds blog posts to the WordPress.com firehose, is affected by yesterday's WordPress.com new third-party sharing opt-in default setting?
Stripped out the Automattic plugins I had running on my wordpress site, and then pulled all the other bullshit plugins trying to tell me how to optimize ("The title "Horrors and Abominations" does not have enough emotional or surprising words in it."). My posting experience is already improved.
@miriamrobern Jumping back into this conversation about preventing the #Automattic#Jetpack plugin for self-hosted #WordPress sites from phoning home to power new AI bullshit.
Turns out the AI will get your information from what is called the "Firehose" and that's been enabled by default for years. 🤦♀️
But it's easy to disable once you know how to find the fucking option.
@acarson I've found the key to proper #Jetpack management is using as little of it as possible. For me, that's mostly Akismet and some of the other security features.
Plus, I get the whole thing for free from my ISP. So, I figure why not.
For the record (pun intended), what is called a "post" in #WordPress and is used in #Automattic's terms and conditions is what other frameworks would refer to as "objects" or "records".
"Custom post types" are "models" in the context of MVC patterns.
Blog posts and news articles are posts. Images are posts. Contact form submissions are posts. Customer purchases in #WooCommerce are posts.
Your WooCommerce customers are user records. Their personally identifiable information is stored in the wp_user_meta table.
All of this is uploaded to Automattic's infrastructure (which is largely located in the US) as "shadow site" data if you use #Jetpack and the #GDPR implications of that are worrying to me.
I can sorta understand the timeline outrage from people that feel like WordPress and Tumblr performed a bait and switch on them, selling them out to train AI models.
HOWEVER, are you going to stand there and tell me, with a straight face, that if someone offered you $50 million a year (likely more) you'd turn it down? That it would be an easy decision? That that amount of money wouldn't at least give you pause?
I'm not defending what they intend to do. But don't act like this is simple.
Yikes. It keeps getting worse. #Jetpack, if I remember correctly, was a brilliantly conceived backup service - self hosted #WordPress users got some piece of mind for a fair price. This is not what they signed up for. #AI
I’m holding off making snap decisions until I learn more, but if this comes to fruition as reported, I may have to migrate blogging software and quite probably hosts for the first time in over two decades.
Finally have a set of database queries that should convert my Markdown Block posts to Markdown in the Classic Editor posts, if I can solve one last hitch with how it’s working under a local install where #Jetpack is in “offline mode”. #WordPress
Quando stavo componendo il post di prima, sembrava tutto ok, eccetto che cliccando sull’ #immagine allegata (perfettamente visibile) nella schermata di composizione, non riuscivo a vederla a schermo intero, e invece appariva un dialogo che diceva (tipo) che il file non era stato caricato correttamente… e cliccare “riprova” non risolveva nulla… 🤐
Però l’ho pubblicato l’ho stesso, perché nella #galleria cloud di #WordPress la #foto risultava. Eeee ho potuto però constatare un attimo dopo che nella pagina l’immagine non caricava, appunto. Il bridge RSS per Telegram ha mostrato questo #errore al posto suo, poi: 🥱
I love how @wordpress just randomly decides to stop collecting stats. Then one day I'll open the #Jetpack dashboard and find it telling me to activate stats again. That invariably says it failed, but actually works (reloading the page shows it). But then there is a gap where it decided not to bother collecting information.
Like below where apparently at some point on January 8/9 it just deactivated itself.