LB: Yet another interesting, worrying and infuriating article about the state of the internet as it games Google search rankings.
"If Google keeps rewarding useless overly-optimized SEO content written by AI published on big media sites while punishing little sites because they wrote articles trying to answer a question readers have, then fuck Google."
I have jury duty next week, so I picked up an Aranet 4 CO2 monitor to see how good the air quality is in the courtroom and deliberation chambers.
With the windows open for the first time this spring today, our house got down into the low 400s for CO2 ppm, but Gypsy's panting brought it up into the 700s!
I recently created my first #Drupal@ViewsField plugin, which apparently is unique among plugins in that you also need to implement a hook (hook_views_data_alter) to tell Views about it and how to use it. The properties you define in the hook seem very similar to what other plugins take as annotation.
Is there something especially complex about this plugin type that regular annotation isn't enough, thus the hook? Or is this just a case of a plugin type that COULD be simplified but hasn't yet?
I tried searching the internet, and the Drupal Core issue queue, but I didn't find anything useful. So, I'm turning to the Federated Hive Brain to see if y'all have any better answers!
I just ran into a thread on toxic culture in social media, and a group of Very Smart People were agreeing with each other that the Fediverse is just as bad because "activits" who gate keep nazis and fascists out of their circles are just as bad as the nazis and fascists themselves.
I wondered why a new list I set up was still showing members' posts in my main timeline. When I went to configure the list, I saw a big white dot (the brightest thing in the UI) next to "Hide these posts from home" and figured that meant this was default and already ON. I presumed the "X" meant I should click to disable it.
Apparently if I had clicked on the control, it would have looked like this. Much more apparent now as clearly on. Since it was the only instance of this control on the screen, I had no others to compare to, and I'm not in the habit of clicking on every control that looks properly set to confirm it's not actually misleading me!
(At least not on a platform that I trust isn't trying to trick me with dark patterns.)
EVERY other control in the Mastodon UI that I can find is either a checkbox or a radio button. Why this sudden shift to an ambiguous toggle for this one control when checkboxes have served their purpose well everywhere else?
LB: I've long thought that #Drupal had great potential to be your personal (or institutional) POSSE hub: publish stuff on your own site, and use APIs or other tools to push out to other social media systems you're on. It's been on my to-do list, but never high enough for me to dabble in it.
CABOOM! encapsulates the reverse, which is also possible: pulling in (and archiving!) your activity elsewhere. Also potential for Drupal!
Especially with the ephemeral nature of Mastodon hosts and the inability to migrate between instances, building a central (and authoritative) repository of your own posts could be really handy.
One thing that continues to baffle me are the people who insist on building dumbed-down UIs with the argument that:
"Most of our users are simpleminded peasants, therefore we must build the UI for their simpleminded needs. We won't provide advanced tools at all for our more intelligent users because the mere presence of advanced tools would intimidate our simpleminded peasants, EVEN IF THE ADVANCED TOOLS ARE HIDDEN BY DEFAULT."
By the same logic, you could argue that MOST of our users don't use assistive devices online, so if we're designing for the most common user, we can ignore accessibility too.
@DaleTrexel
Yes, got it. And we all can help to improve that. It's great that you've identified the problem. Next, it needs to be reported and then fixed. That's what we all do thousands of times every day.
@DaleTrexel isn't this changing when issue queues are moved to GitLab? It's easy to reference issue in GiLab by including links, GitLab's process to truly relate issue requires saving the issue and adding the relation to UI elements that only exist after the initial save. Both of these are easy once you understand them, but neither are intuitive for new users.