Notices by SKC (skc@scottodon.com)

@chris @briancoords @ivory I would pay more than I pay Ivory now for a feature like that!

@briancoords I’m using @ivory too, it shows replies the same as they were with Tweetbot but the only difference I’ve seen is that depending on your Mastodon instance, you may not be seeing all of the same replies the OP’s server has. That’s a Mastodon thing though :(

@scribe pre or post ACF takeover and the big stink?

@chris depressing that this will be my last release with props :(

It comes in waves as I deal with acceptance of what I cannot control.

So yeah that ACF/SCF security issue really was bogus. When the PoC gets published on November 7th, I am "going scorched earth" 🤭 on Matt's reasoning behind necessitating the SCF fork.

Just remember the first line of Matt's post:

"On behalf of the WordPress security team, I am announcing that we are invoking [...] of the plugin directory guidelines and are forking Advanced Custom Fields (ACF) into a new plugin [...] SCF has been updated to remove commercial upsells and fix a security problem."

Nothing is safe here, unsure if his account will be locked or if Pods will be closed.

#WordPress

This was an attack not just on me but also on the Pods project as it means we can't do releases. I have suspected this could happen since the WPE team was locked out of .org so I've already gotten consent from a long time Pods contributor for them to take over the .org listing.

Now that I have been locked out of .org officially, I made a formal request to transfer ownership of the Pods plugins into their control so that we can continue our normal release processes.

#WordPress

Today my WordPress.org account was disabled unexpectedly. I did not request that and I have received no communications with reasoning ahead of time or at the time of that being disabled (like most people who were deactivated on Slack or .org disabled).

This puts the @pods project at risk on .org since we've used the security best-practice of having release confirmations enabled on the Pods plugins on .org since they added that feature. To confirm a release, you must log into .org

#WordPress

@acarson @chris from Post Status:

“This is Monday, we have surprises for you all on Tuesday, Wednesday, Thursday... It's never been more exciting to be in WordPress. 🙂 We're fighting for the future of open source against evil private equity.“

Like it’s just all a scheduled plan for him. It’s not every day but it’s exhausting and it’s breaking down the remaining barriers people have to leaving for good.

@Josh412 🚨this is not a drill! Josh said Pods!

One of the things that makes all of the WP stuff harder for me personally is that I’ve given many thousands of hours of time into @pods and donated* over $100k personally to help get it to where it’s at today. To see the “state of the word” as it is today really stings deeply. I put all my eggs into this basket 🫠

*covering costs of extra devs, support, docs, and other things sponsors+donors alone couldn’t cover (my own time isn’t included in that $)

@chris How many people will leave the WP space entirely? Maybe even leaving tech?

Sitting here writing my “Interview with MM” blog post as I eat pie from Tippins. It really takes the edge off!

2500 words, first draft done!

Hey what’s a casual 1,758 NPM packages matter in the big picture, we’re all friends here - no big deal.

This part of the post I’m working on was pretty cool to dig into.

lol never mind about that post, I have to rework the whole thing and it won’t be an interview at this point.

@eaton 👋

@alda @chris @ramsey I know someone you can reach out to about this if your company says you can’t work on core stuff. They will cover your salary if you get in trouble for talking to them. /s

@ramsey @chris I don’t think that first one counts 😅