Wordpress supports activitypub tho, so that could be cool if they want it to be.
Comment on Tumblr to move its half a billion blogs to WordPress
jedibob5@lemmy.world 2 months ago
Not as drastic as the headline makes it out to be, or at least so they claim.
“We acquired Tumblr to benefit from its differences and strengths, not to water it down. We love Tumblr’s streamlined posting experience and its current product direction,” the post explained. “We’re not changing that. We’re talking about running Tumblr’s backend on WordPress. You won’t even notice a difference from the outside,” it noted.
We’ll see how that actually works out. Tumblr’s backend has always seemed rather… makeshift, so I’m curious to see how they manage to do that. Given Tumblr’s technical eccentricities, a backend migration could probably do a lot of good for the functionality of the site, if done properly. I have my doubts that WordPress’ engineers will be given the time and resources to do a full overhaul/refactor though, so I’m fully expecting even more janky, barely functional code stapling the two systems together.
unexposedhazard@discuss.tchncs.de 2 months ago
WhiskyTangoFoxtrot@lemmy.world 2 months ago
I read a couple of Tumblr blogs. If I could follow them from Mastodon instead I could delete that app entirely.
communism@lemmy.ml 2 months ago
Use rss feeds maybe? Adding
/rss
to a tumblr blog’s url (in the x.tumblr.com format) shows an rss feedVittelius@feddit.org 2 months ago
WhiskyTangoFoxtrot@lemmy.world 2 months ago
I’ll believe it when I see it.
catloaf@lemm.ee 2 months ago
WordPress is built on decades of hacky code, probably more so than Tumblr. I would be shocked if this is an improvement.
Goodie@lemmy.world 2 months ago
is it decades of hacky code, or decades of battle tested code?
I haven’t touched wordpress in… many years, but I’ve seen far too many developers look at old code and call it junk… only to break things horrifically when they attempt a rewrite.
catloaf@lemm.ee 2 months ago
Hacky.
Wordpress has a reputation for the most moronic security issues. Especially when it’s built on PHP, which has its own reputation for moronic security issues. And that’s saying nothing about the quality of plugin developers or plugin code.
I’ve worked on Wordpress sites, plugins, and themes. That was many years ago now, but I doubt it’s changed that much. If anything, it’s mostly benefited from improvements to PHP.
fake@sh.itjust.works 2 months ago
Has to rank as one of the most exploited pieces of software ever.
Definitely be not aided by the fact it’s targeting an audience without the skills or knowledge to adequately configure, maintain and monitor it. And the plugin community only makes the vulnerability exposure worse.
chilicheeselies@lemmy.world 2 months ago
Both honestly. Very spaghetti, but noone can deny that it just works from a user perspective. Would I want to maintain the code? Hell no! Do use it as an end user? Hell yeah!
sugar_in_your_tea@sh.itjust.works 2 months ago
Nah, not touching that with a 10’ pole. There have been far too many exploits for me to feel comfortable putting any of my important data on it. And it’s not just that it’s popular, the level of sophistication for these attacks are… alarmingly low.
eager_eagle@lemmy.world 2 months ago
my thoughts exactly. Who in their sane mind sees WordPress as a solid foundation for anything?
Peepolo@lemmy.world 2 months ago
Most large publishing companies, the white house and various government departments all use WordPress for their main sites. Its the third party integrations that cause security issues, not the core code.
sugar_in_your_tea@sh.itjust.works 2 months ago
Yet the third party integrations are pretty much the whole point of WordPress.
jedibob5@lemmy.world 2 months ago
Not as familiar with WordPress, but if that’s the case, yeah, I don’t have high hopes for this going well…
Woovie@lemmy.world 2 months ago
Every comment in this thread might as well be hearsay. I wouldn’t take it too seriously. I think I’ll trust the corporation that runs wordpress.com and maintains the open source WordPress project instead to know what they’re doing with WordPress.