Replied to Proposal: Treat FLoC as a security concern (Make WordPress Core)

Google is rolling out Federated Learning of Cohorts (FLoC) for the Chrome browser. TL;DR: FLoC places people in groups based on their browsing habits to target advertising. Why is this bad? As the …

I’m responding to this on my own site because I can’t get the interface on the Make blog to do the click right when attempting to reply over there.

I 100% agree with this proposal. Users can only choose to opt in or out if they’re able to make an informed decision about this, and for better or worse, they can’t do that. I’m pretty sure Google will market this as some sort of user-beneficial feature, assuming they tell non-technical users anything at all about this. WordPress, according to its own “bragging”, (I’m using that loosely), powers something like 40% of the web. We can’t continue as a project to pretend we have no impact on it.

If you're playing along with those of us who are taking the Gutenberg Challenge, this is my post for week two. This time, I'm using the text editor. I decided to go with the text editor this time because it's slightly easier. Sorry WordPress, not even you can win the WYSIWYG VS. text editor war. 🙂 As with the first post, these are my not-so-edited thoughts.

First, a working analogy for blocks

I spent some time mulling over this throughout the weekend, and I've decided to settle on the following working analogy. Part of this is because I cheated and looked at some of the code, as well as the generated markup. This will probably also work for widgets. So let's say that you have a bunch of magnets in different shapes and sizes. With widgets, your shapes and sizes are pretty uniform, and widget areas in themes are like metal surfaces you can stick them to. I'm thinking of a toy I got as a kid that was a big metal board/frame/rectangular surface, with letters that had magnets on the back so you could make words on the board but with the letters raised. Yeah, it's incredibly simplistic, but it works. With the introduction of Gutenberg, WordPress is just going to magnetize everything, and the pile of magnets now includes letters, numbers, special characters, punctuation, and every other shape under the sun. OK. So far so good. I think though that this has the potential to make web pages/other web things pretty much fluid from a design perspective, protean even, and I hope there's an upper limit somewhere. Something like, let's try to educate people about design principles, because hamburger menus inside posts, and I would like to reserve some things for the CSS/HTML realm. I know we're democratizing publishing and everything, but democracies have rules. Not sure what I think of this wp:core/freeform tag, which basically means we're using a text widget to add text to a post. I'm keeping an open mind, but it seems to me as though WordPress wants to create its own
tag, and that we've definitely stepped into overengineering territory. After all, it's just text, HTML already has tags for this, (tons of them), and if this is for possible styling later, we're just trading div soup for non-standard WordPress self-created tag soup. So yeah Gutenberg, we're not friends yet, but I'm not kicking you out either. I'm missing my meta boxes though. My screen seems so lonely without them. So I'll be heading back over to my tried and true edit post screen to put the finishing touches on this, and you can hang out down here in your little submenu, well away from my other content types for now.

Last weekend, during WordCamp Europe, Matt Mullenweg announced that Gutenberg, (the upcoming WordPress editor that will replace TinyMCE as well as become integrated into the WordPress customization experience), is now available for downloading and testing. So of course people have started playing with it, and Aaron Jorbin issued the following challenge on Twitter today.

The Gutenberg Challenge

I broke my own cardinal rule and installed this on a live site, because I need content to play with. I'll start with the good first. I appear to be able to add blocks and move them around using the visual editor part and a screen reader. Now for the not so good.

I can type a post title, but I have to add a block just to start typing text. I can see myself switching to text when this goes live, because writing a post like this is turning out to be incredibly inefficient, cumbersome even, and I'm not sure if that's because I'm just used to writing HTML and can do that in my sleep and so I don't use WYSIWYG editors, or if it's because of the software, or both. I'm also not sure if paragraphs are supposed to be in their own separate blocks although I suppose if you're going to be moving them around, they probably should be each in their own block. I can see this increasing the cumbersomeness exponentially. Right now I'm thinking of what it would be like to write one of the WordPress with a Screen Reader posts in this and I want to just crawl under my desk and never write again. I've lived in the WordPress dashboard daily since 2005, and I'm finding this really frustrating. I can see someone new to WordPress who uses a screen reader just giving up on this. Admittedly, as I mentioned above, this could all just be I'm not used to using a visual editor like this. I also realize that this is only six months along, and that it's in its early stages. I'll also continue to play with it so I can get used to this, and then explain it to other screen reader users. But I think I'm going to end here for now because this is completely overwhelming, I'm unable to separate my own experience from what's supposed to be happening and be fair and objective about this, and, (I'm only half joking here), Gutenberg is causing me to question my life choices right now.