Conversation

Notices

1. Embed this notice
   FeralRobots (feralrobots@mastodon.social)'s status on Tuesday, 24-Sep-2024 21:53:52 JST FeralRobots

   It would be interesting to see #WordPress fork hard in response to Automattic's clear desire to have their open source cake & copyright-restrict it, too.

   I'd find it fascinating if someone did a database-compatible fork with a wholly new front end. That basically happened w/*Nuke in the early aughts. (Hell, when I first looked at the WP database schema I was like 'holy crap this is PostNuke!' I still think they basically took a *Nuke schema as a starting point & wrote a new front end.)

   • Embed this notice
     Eaton (eaton@phire.place)'s status on Tuesday, 24-Sep-2024 21:53:52 JST Eaton

     in reply to

     @FeralRobots so, amusingly enough WP actually *is* a fork of the early aughts GPL CMS b2/cafelog… https://github.com/leogopal/b2

   • Embed this notice
     Eaton (eaton@phire.place)'s status on Tuesday, 24-Sep-2024 23:25:21 JST Eaton

     in reply to

     @FeralRobots nope, not AFAICT. Just took a spin through the code and it definitely looks like its own thing. That said, the general “users/posts/meta dumping ground for unanticipated data so nobody has to figure out schema management” approach is a SUPER early aughts vibe

   • Embed this notice
     FeralRobots (feralrobots@mastodon.social)'s status on Tuesday, 24-Sep-2024 23:25:22 JST FeralRobots

     in reply to

     • Eaton

     @eaton Do you happen to recall if it was a Nuke derivative?

   • Embed this notice
     Eaton (eaton@phire.place)'s status on Tuesday, 24-Sep-2024 23:53:37 JST Eaton

     in reply to

     @FeralRobots tbf, that impulse eventually shifted a lot of young projects to “ehhhhhh, just toss it in mongodb” lol