Rather than going through the trouble of writing a system for reliably copying all of the data from the database of another imageboard system (for example, TinyBoard) for it to be "translated" into gochan's DB schema, it might be possible and less work to instead have a plugin do something like the reverse. So for example, a plugin might be registered in gochan.json to make gochan compatible with a TinyBoard database, handling things like staff, board, and post creation, editing, deletion, etc, via events.
This would still likely require a lot of work, but might be more feasible. It would also likely require all SQL queries to be moved to the gcsql package.
Rather than going through the trouble of writing a system for reliably copying all of the data from the database of another imageboard system (for example, TinyBoard) for it to be "translated" into gochan's DB schema, it might be possible and less work to instead have a plugin do something like the reverse. So for example, a plugin might be registered in gochan.json to make gochan compatible with a TinyBoard database, handling things like staff, board, and post creation, editing, deletion, etc, via events.
This would still likely require a lot of work, but might be more feasible. It would also likely require all SQL queries to be moved to the
gcsql
package.