rmrk
I find the ideas of fixing healthcare, reinvesting in our economy and infrastructure, and shoring up our social programs highly convincing. And I'm pretty sure the polls show those ideas resonate across the political spectrum. And I only hear those ideas coming from one party.
I suppose these historians would also object to me watching star trek tng on streaming in HD since it was clearly meant to be only ever be seen transmitted over radio waves to a cathode ray tube.
I think real solutions are gonna require us to break out of our tech-focused approaches and find ways to get Google, Facebook, Twitter to really start to care about fixing this stuff. Unfortunately I think that means it'll have to start costing them.
We as a society have decided that rampant mis-information and propaganda is only worth solving if we can automate it. If we actually have to pay real people real money to fix it on an ongoing basis, that's just too expensive.
Sure there are problems having Humans doing this work too, but they are still way ahead of AI in this problem space.
How long do we wait for automated solutions while these problems impose real costs to society?
and
"Facebook will also begin to down-rank news in its algorithm that doesn't have bylines, or present information about the company's editorial staff on the publishers' website."
Okay those are the new requirements for content mills and fake propaganda outlets. How long before they adapt?
Actually vetting reporters, reportage and news outlets is really hard for a team of smart humans editors to do. Even the premiere organizations like the NYT and Washington Post with their armies of editors has failed at this from time to time. Algorithms are not ready for this task yet.
MTV can break a lot of plugins that filter front-end output. But it depends on how you use it. It doesn't have to.
We like having function exports be hard-coded. Making all functions available to the templating engine is unnecessary. It's pretty trivial to declare new functions to use in the templates, and it doesn't have to be done in the MTV plugin, you can declare those in your theme or plugin.
We are always involved with our end users and we design the templates. Our users can't install plugins or themes and we typically lock down lots of settings. So we don't mind if we break template tags because we have complete control over how our sites are used.
MTV has it's own template structure and supports all sorts of template inheritance. That all comes from Twig. It also supports child theme inheritance, if you're using MTV to build your themes all of your themes.
We've tried to get around the future-update-breaking-shit issue by making the core of MTV sit on top of WordPress. It's totally possible to build an app with MTV and no WordPress.
Again - MTV works for us, but won't work for everyone. And it's really only useful if you're gonna build a site from scratch.
Replicating WordPress functionality in Rails or Django would be an enormous job. Making WordPress more like Django was much less work.