#wordpress 2021-12-27

2021-12-27 UTC
#
GWG
[tw2113_Slack_]: What do you think of pfefferle's comment?
#
[tw2113_Slack_]
hmm
[pfefferle] joined the channel
#
[pfefferle]
Sorry, but it still feels a bit hacky
#
[pfefferle]
I understand your ideas, but it still does not feel like a taxonomy… at least semantically…
#
GWG
[pfefferle]: That's the part I'm wondering about. I figured you weren't awake this late in your timezone) and wanted to try to talk it out
#
GWG
But, I'm attaching it to posts
#
[pfefferle]
Christmas holidays 🎄
#
[pfefferle]
Yes, but only to have an attribution
#
GWG
[pfefferle]: And an archive.
#
[tw2113_Slack_]
it's probably best as meta of some sort
#
[tw2113_Slack_]
whether it be post -> term -> term meta
#
[tw2113_Slack_]
or post -> post meta
#
[pfefferle]
And it sounds very Micropub specific
#
[pfefferle]
Hey [tw2113_Slack_] 👋
#
[pfefferle]
Happy Christmas btw.
#
[tw2113_Slack_]
good day sir
#
[tw2113_Slack_]
and to you
#
GWG
Isn't it the same thing as storing menus in the post table? Or storing blocks in the content field?
#
[tw2113_Slack_]
core abuses post types way more than this is abusing potential post types
#
[pfefferle]
Yes, but post types
#
GWG
I understand the concern.
#
[pfefferle]
It can make sense in the Micropub case, but is that the classic one? What about other API requests? Does it still work that way?
#
[tw2113_Slack_]
this is risking...what? a handful of meta keys per post?
#
[tw2113_Slack_]
every ecommerce solution should be using their own tables, and many have been moving that direction which is great. but they're still leaving previous content behind thus far for legacy reasons
#
GWG
Well, if you were using IndieAuth to access the REST API, it could be added to attach there.
#
GWG
As for Microsub, the other most common IndieAuth use case, not as much. There would still be client data stored though in this format.
#
GWG
So, publishing is the biggest use case for a taxonomy over something else.
#
[tw2113_Slack_]
I'm still fine with this being a taxonomy term status
#
[tw2113_Slack_]
we're haggling over microoptimizations
#
[pfefferle]
It is all about migration… this change breaks backwards compatibility and the next change may do it again…
#
GWG
[pfefferle]: You may also recognize I repurposed the sideloading code from the webmention PR.
#
GWG
[pfefferle]: Well, actually it doesn't, because it doesn't retroactively change old tokens or posts.
#
GWG
Only new ones
#
[pfefferle]
But what about the UI to invalidate tokens?
#
[tw2113_Slack_]
do those invalidate on their own with time?
#
[pfefferle]
You are very pragmatic ☺
#
[pfefferle]
How will Micropub add the taxonomy?
#
GWG
[pfefferle]: Nothing changed in that UI.
#
GWG
[pfefferle]: Code is already written for that. It looks for the client_uid in the auth response, and if it is there, sets the post to it.
#
GWG
Since that didn't exist before this...
#
[pfefferle]
Using WordPress taxonomy features?
#
GWG
[pfefferle]: wp_set_object_terms
#
[pfefferle]
Or to ask more concrete: what about a user that does not use indieauth will Micropub still work?
#
GWG
[pfefferle]: No, but only because IndieAuth is required for Micropub.
#
[pfefferle]
No, oauth is ☺
#
[chrisaldrich]
(not having looked at code), but is there also facility for micropub clients with edit capability being able to change it? That is, I make a post with OmniBear, but later re-edit it with Quill as an example? This is probably an edge case down the line as I don't think there are many client with editing capability and it's not a common pattern (yet). Does this have any bearing on the form/structure/storage?
#
[pfefferle]
It would work with the tax idea
#
[pfefferle]
You can add both then
#
GWG
[pfefferle]: Good point. The Indieauth plugin is a dependency of the Micropub plugin, to be more precise. Either way, if a new OAuth alternative was introduced, I'd adjust to support it.
#
GWG
I only set it to work for creation, not updating, but it could be expanded.
#
[pfefferle]
Is it directly a dependency? Doesn‘t it work with indielogin.org any more?
#
GWG
[pfefferle]: You are thinking of Indieauth.com
#
GWG
Not indielogin, which is web-sign-in, not OAuth
#
[tw2113_Slack_]
good day [chrisaldrich]
[arush] joined the channel
#
[arush]
hi all, and merry Christmas to all who are celebrating!
#
[tw2113_Slack_]
welcome to the taxonomy party [arush]
#
GWG
[pfefferle]: But no, not for several versions. The code for supporting indieauth.com is still in the IndieAuth plugin, but behind a hidden flag and unsupported.
#
GWG
aaronpk really wants to deprecate indieauth.com
#
GWG
[pfefferle]: You reviewed the moving of the code from Micropub to IndieAuth behind the flag
#
[pfefferle]
Feels like a Micropub feature then
#
GWG
[pfefferle]: The display and setting of it is. But the tracking of clients is related to the bearer token, which is handled by Indieauth.
#
[pfefferle]
But the taxonomy only makes sense in the MP case
#
[chrisaldrich]
Happy taxonomy day. Happy boxing day. 🎁
#
[arush]
yay taxonomies! i just spent a huge chunk of time working on a site with a ton of custom taxonomies with Advanced Custom Fields as a dependency. And speaking of, i have some additions to the post kinds plugin i should probably submit. Will do so once i get them cleaned up because they're a result of experiments.
#
GWG
[pfefferle]: Yes, but if it is implemented as a taxonomy in Micropub, then I would have to store it a second time in IndieAuth.
#
Loqi
woot
#
GWG
[arush]: Would love that
#
[tw2113_Slack_]
[chrisaldrich] what taxonomy would "boxing" relate to? 😄
#
[tw2113_Slack_]
celebration types?
#
[chrisaldrich]
don't muddy the holiday waters [tw2113_Slack_] 😁
#
[tw2113_Slack_]
holidays?
#
[tw2113_Slack_]
zing
#
[pfefferle]
I am chalking that, because I still am a friend of keeping the plug-ins independent…
#
[pfefferle]
Not chalking… challenging
#
GWG
[pfefferle]: So am I. But as a dependency, anything token handling related I keep in IndieAuth and call from Micropub. Such as the function to get the scopes and such.
#
[tw2113_Slack_]
background noise for non-Auth discussion: anyone else use Custom Post Type UI for their content types? cause I'm the main dev there and open to feedback
#
GWG
[tw2113_Slack_]: I do not.
#
[pfefferle]
And that is why it feels wrong in my eyes… the taxonomy only makes sense for MP and not to store general post/page independent client infos
#
GWG
[pfefferle]: Where would you store them then in IndieAuth? I was storing them individually inside each token before this. That seemed like too much.
#
[pfefferle]
↩️ I do not have custom post types yet ☺
#
[chrisaldrich]
[tw2113_Slack_] Are there any broad canonical CPT set ups for reviews or recipes (maybe books) (for proper h- level microformats) the way that Jetpack has portfolios?
#
GWG
The other option might be the option table.
#
GWG
There aren't that many clients.
#
GWG
Of course, option table isn't as scalable.
#
[pfefferle]
If you use a custom post type to store the access token it could make sense again 😂
#
[tw2113_Slack_]
not that I'm aware of [chrisaldrich] other than genericly named types. CPTUi doesn't delete content at all, so it'd be pretty easy to migrate between.
#
GWG
[pfefferle]: I considered that at one point. Migrating the tokens to the post table.
#
GWG
[pfefferle]: There are advantages over using user meta.
#
[tw2113_Slack_]
given that this topic is registered on the fly and at runtime, last one registered, only one used
#
[pfefferle]
I hate WP for not having an extensible DB system
#
GWG
[pfefferle]: I'll consider moving all tokens into custom post types again. It was something I considered, but that seemed to be an even bigger migration. That would likely be a major version shift.
#
[tw2113_Slack_]
↩️ well i hope you consider us in the future. All support goes through me, so you know you're in good company 🙂
#
[arush]
I've used CpTuI on a couple projects, but prefer to organize CpTs and related stuff in their own plugins. Makes it all easier to find if i need to reuse.
#
[pfefferle]
Using given tables feels hacky so often
#
[arush]
i like the plugin though for quick and dirty CpTs that i know i'm never going to touch again.
#
[tw2113_Slack_]
i fully accept that for some users, we are code generators for quick copy/paste [arush] 🙂
#
[arush]
CPTUI stupid keyboard is acting up again.
#
[pfefferle]
So maybe I have to sleep over it… it is getting really late…
#
GWG
I've been working on using a custom post type for the rewrite of Yarns Microsub. Sources(feeds) as a custom post type, as are entries in a feed. Entries have sources as their post parent. And channels are taxonomies attached to the sources.
#
GWG
[pfefferle]: I'll contemplate doing custom post types, as it was something I was thinking of anyway.
#
GWG
[pfefferle]: Sleep well. And don't be a stranger. We don't talk enough
#
GWG
[arush]: Post Kinds development has slowed due to my failure to decide ona way forward.
#
[tw2113_Slack_]
sweats
#
[pfefferle]
Yea, not that much time/motivation lately
#
[pfefferle]
Sorry 😢
#
[pfefferle]
I hope it comes back
#
[tw2113_Slack_]
No pressure on me, only 9,568,310 total all time downloads, and 1,000,000+ active isntalls for CPTUI
#
[tw2113_Slack_]
I'm no Yoast SEO, but that's still a lot of pressure for a mostly singular developer for a plugin 😄
#
[pfefferle]
I plan an IndieAuth slot at the CloudFest Hackathon… I maybe need some feedback from you folks…
#
[pfefferle]
Not indieauth… indieweb…
#
GWG
I always love to talk Indieweb.
#
[tw2113_Slack_]
whatever helps the independent web!
#
[pfefferle]
I hope to motivate some contributors
#
GWG
[pfefferle]: I'd love to find more contributors.
#
[pfefferle]
Or find someone to pay me to do it full time 😂
#
GWG
[pfefferle]: If you do that, try to get the budget for a full time assistant?
#
[tw2113_Slack_]
[pfefferle] if i ever win the lottery, specifically multi-million, i'm on it
#
[tw2113_Slack_]
70k/year minimum
#
[tw2113_Slack_]
USD
#
[pfefferle]
Could you think about quitting your day job for that [dshanske] ?
#
GWG
[pfefferle]: I'm not sure if making your hobby your job is the best thing, but I'd seriously consider it
#
[tw2113_Slack_]
i often postulate if I won the lottery, I'd pay myself to work full time on the products area of my current dayjob with minimal paycheck from employer
#
[tw2113_Slack_]
not really a $1/year salary, still something 4-5 digit but you know
#
[pfefferle]
My problem is, that I have so little time for Open Source atm. so I see no other chance 😢
#
[pfefferle]
And then there is also Home Automation and WordPress contribution and …
#
[tw2113_Slack_]
given the log4j? debacle, there's definitely some sectors of open source that should probably have a payment basis
#
GWG
[pfefferle]: I love those too.
#
[pfefferle]
Oh don‘t mention log4j!
#
[pfefferle]
That burned a lot of time in my Dayton!
#
[tw2113_Slack_]
all my personal sites are on nginx, yet at times i wonder if i'm still not doing enough
#
GWG
Fortunately, I missed log4j at work...though I saw we handled it. I just have to deal with acronyms like GDPR, and DOT, and AJB
#
[pfefferle]
I am German… we invested GDPR 😂
#
[pfefferle]
„Datenschutzgrundverordnung“
#
[tw2113_Slack_]
thank you for all the extra noise popups that everyone blindly clicks okay on
#
GWG
[pfefferle]: I know. I just get to talk about it
#
[tw2113_Slack_]
the second worst thing about the internet: cookies. the first worst thing about the internet: having to authorize them
#
[pfefferle]
Time to sleep now… nice to read you all after along time
#
[tw2113_Slack_]
night night
#
[tw2113_Slack_]
reviewing
#
[arush]
@gwg I totally hear you on indecision on how to move forward. Somethings I noticed on the custom tax project, since it also involved a ton of custom fields, was that custom tax and custom field are two features that seem to be getting the short end in this new block world. And that's going to turn out badly for even moderately complex sites, to say nothing of plugins that rely on these two things, which is tons of them.
#
GWG
[arush]: So are comments.
#
[arush]
@gwg I was reading a post the other day on the Tavern about post formats with the new editor by Justin Tadlock which essentially landed on "give users as much control as possible over the templating of post formats,' which is great, except mF2 is a lot like accessibility in that the markup has to remain correct in order for things to work properly, so iMHO not a great idea to turn it all over. And yeah, comments too but I didn't
#
[arush]
work with those much.
#
GWG
Maybe I'll go back to Microsub for a bit
#
[tw2113_Slack_]
oh post formats, when Tumblr was thought to be a threat
#
[tw2113_Slack_]
at least they pushed all the way through with Wix threats and page builders *COUGH COUGH GUTENBERG COUGH COUGH COUGH COUGH*
#
[tw2113_Slack_]
sorry, coughing fit
#
[arush]
lol [tw2113_Slack_]
#
GWG
I still fear being left behind on the blocks
#
[arush]
[tw2113_Slack_] GB is at the same point where all the other drag-drop solutions are in terms of they've got 80% really good and they're stuck on the last 2%, and we keep being told it's super awesome/better than all the rest but it keeps not living up to the hype.
#
[tw2113_Slack_]
yay marketing!
#
Loqi
does a happy dance!
#
[tw2113_Slack_]
calm yoself loqi
#
[arush]
twenty percent not two. WTF is wrong with these Jaws Slack scripts.
#
[tw2113_Slack_]
but what's the latest "powered by the internet" status from the most recent State of the Word?
#
[tw2113_Slack_]
40%+ ?
#
[arush]
Yeah but that's according to one source, and now I want to find that post where someone dared to question the stats which immediately resulted in a leadership melt-down because i think that questioner may have been correct to question. Because given recent experience with clients, its these little details that are going to screw up business operations and trust me, they do not care about Wordpress being high on its own supply.
#
[tw2113_Slack_]
i'm all for validation
#
[tw2113_Slack_]
dare I say, the cult of ma.tt ?
#
[arush]
Re; moving forward though, I think indieweb folks might want to start considering taking our ball and moving over to Classicpress. Still researching because I'd like to be reasonably sure it's going to survive, but am seriously looking for at least my personal site.
#
GWG
[arush]: I've looked, but there are some things I'd like them to port over
#
[tw2113_Slack_]
oh yes, classic press exists
#
[arush]
Yeah. That cult. I mean I'm not trying to go all WpTavern comments section here, but I have to admit, all the philosophizing with very little practicality really isn't solving any problems.
#
[arush]
@gwg which things specifically?
#
[tw2113_Slack_]
not to toot my own horn THAT much, but i heard on a recent enough podcast that Matt still likes the blogroll, and i created a block around the blog roll...i'm helping him bridge his legacy with his current, and i hope he's making good use out of my block
#
GWG
[arush]: A lot of little improvements, such as improved filters and such.
#
GWG
I suppose I could do some commits to try and bring them over
#
GWG
I was looking at the fact that taxonomies can be hooked to users and comments. Wondering interesting things I can do with that
[asuh] joined the channel
#
[asuh]
GWG, do you consider Post Kinds one of the last minor compatibilities for WordPress + Indieweb because of Gutenberg?
#
[asuh]
*compatibility issues, since it’s not really there yet?
#
[asuh]
It seems like many of the other plugins can work as it
#
[asuh]
*as is
#
[arush]
[tw2113_Slack_] you should totally toot your own horn re; that block, because if you don't no one else will.
#
[tw2113_Slack_]
definitely a hurdle for post kinds
#
[tw2113_Slack_]
I'm up to 20+ installs 😄
#
[tw2113_Slack_]
that's at least 20+ people on modern WP that still care about blogrolls
#
[arush]
yeah for post kinds and i think to a lesser extent webmentions in general because Wordpress currently eats those as comments and see above re; comments and the short end of the stick.
#
GWG
[asuh]: The other plugins could be updated to work with blocks. Simple Location, Syndication, and such
#
[asuh]
[tw2113_Slack_] were you previously playing with Post Kinds for blocks recently?
#
[tw2113_Slack_]
not recently in any context
#
[asuh]
GWG I’m thinking of the bare minimum too. What would it take to have a Gen 3 or Gen 4 site with WordPress + blocks.
#
[arush]
[tw2113_Slack_] 20 is way more than I thought would have cared about the blogroll, I think that's awesome. Sometimes I wonder if people would care more about blogging features in general if platforms cared, but I suppose that could also be me being nestalgic.
#
GWG
Not sure...still haven't wrapped my mind around how to implement
#
[arush]
like, what if micro.blog had the same kind of funding WordPress does/
#
[tw2113_Slack_]
i legit wonder what discovery looks like in 2021/2022 without the source of the flighty social media. Like seriously, how do you promote yourself in this modern age?
#
[tw2113_Slack_]
and perhaps subsconsciously, I started a blog/website to try and discover just that this year, where i do non-serious reviews of campy/bad movies
#
[asuh]
I think discovery is a nice long-term goal and it would be amazing if we figured that out. But short term, WordPress + Gutenberg (et al) would benefit from some of the basic functionality of being able to publish, syndicate and consume similar to any other silo out there
#
[chrisaldrich]
[tw2113_Slack_] he didn't reply to this thread about blogrolls: https://twitter.com/rboren/status/1019275363522895874
#
@rboren
@photomatt I recall the jokes made about crusty blogrolls when we deprecated the links manager. Now, folks are exhuming it for use as their canonical OPML source to feed OPML subscriptions. https://boffosocko.com/2017/11/10/a-following-page/
(twitter.com/_/status/1019275363522895874)
#
[tw2113_Slack_]
i auto-publish to Twitter and have my RSS prominently featured on the site itself, but it's still a struggle so to speak
#
GWG
Well, if I get Microsub working again...
#
[arush]
problem with syndication at least is that it's getting harder to syndicate to silos and the ones you can syndicate to are becoming fewer. And yeah i remember that thread re; blogrolls.
#
[tw2113_Slack_]
[chrisaldrich] definitely an interesting point
#
[tw2113_Slack_]
at the same time, i've devtools modified to push some parts down a little bit for this screenshot
#
[arush]
yeah i gotta get microsub working again too.
#
@tw2113
@photomatt listening to you on the Open Minds by Creative Commons podcast from this summer and I think you’ll like this block I made https://wordpress.org/plugins/blogroll-block/
(twitter.com/_/status/1469723266864586757)
#
GWG
[arush]: I'm rewriting the Yarns plugin
#
[tw2113_Slack_]
yay permalinks
#
Loqi
does a happy dance!
#
[tw2113_Slack_]
do your dance of happy, loqi
#
[arush]
i think this year's project is going to be figuring out how to detach myself from Goodreads. Starting with putting book challenges on hold so i create less content lol.
#
[asuh]
Did anyone link to the article about Matt on Protocol’s website?
#
[asuh]
No matter the spin on where he is today, I hope it remains sincere about his belief about WordPress remaining autonomous and not to go with fads. I just wish someone like Matt or other core contributors would learn about being even better about independent or federated publishing
#
[tw2113_Slack_]
coincidentally i'm somewhat eying abstracting out my goodreads-fork on apiratelifefor.me work [arush]
#
[tw2113_Slack_]
which is mostly CMB2 and post types and template overrides. Need to figure out how to best make things not template-based
#
[arush]
yeah it's in my reads; https://arush.io/156858-2/
#
[tw2113_Slack_]
koolaid of matt
#
[arush]
@gwg I will totally add that to the calendar because it very much interests me.
#
[tw2113_Slack_]
i'll give him credit for not going for the blockchain or whatever angle of "web 3.0" but at the same time...
#
[asuh]
[tw2113_Slack_] totally agree, and I hope he’ll keep his eye on the ball overall
#
[tw2113_Slack_]
we're barely Web 1.0 compliiant, in the long scheme of things, "web 3.0" feels very gatekept"
#
[arush]
Yeah that stuff about saving the internet was a bit much, and I don't agree with him re: web3 I agree with Jack that it is absolutely just another form of centralization.
#
[tw2113_Slack_]
yeah, these blockchain things are open source, but the people who could proverbially benefit most are too busy with trying to survive to bother
#
[tw2113_Slack_]
Web3 is very techbro
#
[tw2113_Slack_]
and forgive me ahead of time if i mix web3 with web3.0. web3 is what i am criticizing
#
[asuh]
The major point that stuck with me at the beginning is that WP is 43% of the internet right now. This means Gutenberg compatibility with Indieweb is a big deal
#
[tw2113_Slack_]
and also very much not WordPress, sorry for that 😄
#
[arush]
WP may be 43%, at least according to w3tecs, but what we don't know is how much of that is GB and how much of that is old editor
#
[chrisaldrich]
We've also got to remember that Ma.tt/Automattic has taken VC money now and there will be an expectation of return on investment there. This fact makes me wary as they're usually the one's driving the direction of WordPress.
#
[arush]
Yeah what Chris said.
#
[tw2113_Slack_]
i'm still convinced that the WP REST API came to be because Matt insisted on the ability to push Gutenberg through, which ironically heavily relies on the REST API
#
[asuh]
[arush] it’s a valid point, and maybe classic editor is still widely used, but that’ll change in short time
#
[chrisaldrich]
[tw2113_Slack_] re: your screenshot of your blocks tweet showing the Ma.tt like -- I thought I was the only one who modified pages with dev tools to get nice screenshots like that. 🙂
#
[tw2113_Slack_]
it has a dark side...did someone really say such things?
#
[arush]
I don't think that's going to change as quickly as Matt wishes it would. There are a lot of sites depending on things like custom tax and custom fields and that stuff is getting the short end in GB. Matt saying Ok GB is perfect we're going to turn off classic editor isn't going to fix all that.
#
[arush]
And I haven't even touched on the creeping of accessibility issues, which i know most don't care about but still continues apace.
#
GWG
I think the fair thing to do is to say that the Classic Editor will continue to work as long as people want it to.
#
[arush]
yeah I modify pages through dev tools to fix things all the time.
#
[asuh]
Despite what happens because of VC money and Matt’s ambitions, we’re still in a world where a huge chunk of the internet is using WordPress. To be able to provide a solid alternative to major silos is, while difficult and ambitious, a noble goal for Indieweb’s community.
#
[asuh]
And, unfortunately, I think that’ll increasingly mean Gutenberg compatibility
#
[tw2113_Slack_]
I don't foresee "classic editor" leaving the core codebase any time soon
#
[arush]
Oh you have this really awesome caracel that's getting in my way and won't shut up because you used ARIA incorrectly again? display:none on the whole thing when possible.
#
[tw2113_Slack_]
much like the links menu item still has not left
#
[tw2113_Slack_]
@chi
#
[asuh]
I agree, WordPress will probably maintain backwards compatibility for the foreseeable future.
#
[tw2113_Slack_]
proper props to Meagan who is an unknowing demonstration 😄
#
[tw2113_Slack_]
[arush] champion ARIA and a11y as loud a you can for as long as you can, in my humble opinion
#
[arush]
i hope it does, but it's not something we can really bank on.
#
[arush]
FSE took a way bigger leap than i thought it would, which is concerning.
#
[tw2113_Slack_]
obsoleteling the idea of a theme. yay
#
Loqi
😃
#
GWG
I have plenty of issues with the way themes are set up. But there are better ways to address
#
[arush]
For new sites that's not a big deal, but for sites that need to be redone, say, because their content needs to be remediated for accessibility and their theme needs it and plugins are creating problems, those are the ones where it's not so smooth a transition.
#
[tw2113_Slack_]
i'm a really odd mix of "yay! gutenberg" and "FUCK GUTENBERG!"
#
[tw2113_Slack_]
i recently had a mostly smooth transition from a lot of classic content to gutenerg, but it wasn't seamless
#
[arush]
There are some things i really like about it, like the way themes are going and some of the things you can do with blocks. But at the same time, it makes me want to pull my hair out. So yeah my thoughts are kind of mixed on it.
#
[asuh]
I like half of what Gutenberg provides, and some of the ideas, but I agree that it’s lacking in too many ways all this time later
#
[asuh]
at work, we’re too invested in ACF api for work to even consider Gutenberg, but I want to actually see a future where it’s possible to introduce some of Gutenberg ideas into what we’re doing
#
[tw2113_Slack_]
with the exception of some posts that have a column layout of links and a poll, and then also a grid of 4 for youtube videos, most of my gutes posts are pretty heading/paragraph/image based
#
[tw2113_Slack_]
WebDevStudios, my employer, is decently heavy in ACF + blocks last i checked
#
[asuh]
If I ever get time, I’d look into using ACF + blocks to see what it looks like, but it’d probably be a messy upgrade at the very least
#
[arush]
Yeah but the thing about ACF and blocks is that if you're dealing with new fields/groups it's easy. If dealing with old stuff that's already there stick a fork in it because you're done. No blocks for you. And it can get really weird when a site's heavily depending on ACF so you have to have classic editor for parts of it to work, but then there are parts that are all blocks. Creates a very disjointed experience.
[tantek], fef, Rodhicks and neceve joined the channel
#
[tw2113_Slack_]
Hmmm 🤔
balupton[d], Agnessa[d], fef, Seb[d], MarkJR84[d] and Eddy04[d] joined the channel
#
[arush]
Early Christmas present?
#
[tw2113_Slack_]
it's suspect after I used browser dev tools to fake a different tweet to mention Chris 😄
#
[tw2113_Slack_]
[arush] Chris posted a screenshot claiming Matt Mullenweg praising my blogroll block plugin
#
[tw2113_Slack_]
over on twitter
#
[arush]
Oh now it makes sense.
[jeremycherfas] and [manton] joined the channel
#
GWG
I don't do Christmas presents, but I'll go for a Chris present
#
[tw2113_Slack_]
Chris Mass Present
#
[tw2113_Slack_]
a really big, massive gift
Darius_Dunlap[d] joined the channel
#
[chrisaldrich]
Apologies for the lack of alt on that screenshot. Slack could do better and I intended to come back after Michael saw the original, I didn't expect it to be while I was still sleeping the holiday away. It was a visually realistic screenshot (made with browser dev tools) of a modified Mullenweg tweet from December 24 so that it read "I'm desperately in love with the new Gutenberg blogroll block from [tw2113_Slack_]."
#
[tw2113_Slack_]
😄
#
[chrisaldrich]
My birthday is in July, so we celebrate Chrismas in July.
IntriguedWow[d] joined the channel