"Enshittification" isn't just a way of describing the symptoms of platform decay: it's also a theory of the mechanism of decay - the means by which platforms get shittier and shittier until they are a giant pile of shit.
--
If you'd like an essay-formatted version of this thread to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:
@kgoldsholl@pluralistic Also, the way that companies have converted their sites to platforms. E.g. B&Q, a chain of UK DIY shops, used to have a website that sold their stuff. It was fine. You could buy the things that they also sold in their shops. Now it's a PLATFORM and it lists products sold by loads of random other firms. There's no guarantee of quality, no idea who you're dealing with if things go wrong.
What's a good use case for creating a custom entity in #Drupal?
It seems to me that in terms of creating regular content, there are exceedingly few cases where you wouldn't be better served just by creating a new node bundle and then making your own custom field types, widgets, and formatters to extend the good ol' Node entity.
I thought that a custom entity might be warranted for performance reasons if you need to squeeze every bit of speed you can, but I read a couple of blog posts from someone who said he found the difference to be minimal.
In his estimation if you need squeeze as much speed as you can and have a highly structured data schema that's not likely to need changes, you should just create custom DB tables and write direct queries to retrieve the data.
@mrdalesmith@sysop408 I'd add:
4. Do you need base fields, i.e. fields defined in code? (Bundle fields still have only partial support in core.)
5. Do you want custom indexes on the DB table?
@mrdalesmith@sysop408 That works if you want your custom base field to be on all node types. In cases where you want N bundles to have a base field, but not on existing node types, I'd say make an entity type.
New release of #Drupal Code Builder adds selecting of events to subscribe to. And new release of Module Builder has the autocomplete tweaked to treat '.' and '_' as interchangeable, so you no longer need to remember if it's 'entity.type.manager' or 'entity_type.manager' - either will work.
Are you lazy about writing a README file for your #Drupal module? The new release of Drupal Code Builder writes some of it for you - module dependencies and instructions for navigating to the module's settings form are now automatically generated!
@organicmaps has been HUGELY useful for both planning and while away on holiday. I've downloaded maps of where we were going for offline use, so I can navigate without data or wifi. I've used it to find shops, playparks, restaurants, ice cream, and drinking water. With the bookmark feature I can make lists of useful spots ahead of time. I've filed LOTS of bugs in their issue queue because I'm a nitpicker and a magnet for bugs, but it's because I think it's a fantastic app with huge potential!
@ekes@rachel@phlash@revk@falken@sangu I'm suddenly struck by the responsibility of my work! I was just faffing about with SearchAPI and recurring dates, and now it's got a direct impact on people's daily lives!
@ultimike I don't see how this can get better. It's just probabilistic guesswork. And it's fucking the planet while it's doing it. Using AI is immoral.