Multitool.org- Into the Fediverse!
-
Does that mean that the theme will be totally different ? Will we have like buttons and the ability to tag members, multi quote and such ?
-
The theme will change but we will do our best to make it pretty enough.
My hope is that we will be able to tag and stuff.
Def
-
Sounds interesting - And hopefully good and for the best ....
And we have to keep up with the times, and securities, and usability, and ease of use, importance of images/videos etc etc - This I think is a big reason we lose out to Zuckercrap.But you know what I am gonna ask - dont you? .... What happens to SAKWiki? ???
As well as incorporating all the recent Vic/Wenger developments; Delemonts, merge of 111mm families, new models, limited editions etc etc
I think you know I have spend the last 10 years or so making SAKWiki a lot more accessible and user friendly - A lot of that has been the formatting and presentation of the Wiki pages, and re-organising all the menus and image galleries etc etc
To give you some idea roughly 600 of the 800 Wiki pages have been updated in the last ~5 years !!I hope all that work will survive the move!!
-
There's a huge amount of work to move forward with this plan, as always.
Ideally we won't lose anything, but I do think we will need to recruit some minions to move certain things from one system to another. There's a whole lot of custom solutions to fix problems we've implemented over the years that most of us have long forgotten how and where they are...
Tikiwiki should survive, but to fully integrate we'll need to do even more work on the wikis, especially as you are already aware on the image galleries, to be able to keep upgrading to more current versions. Staying with Tikiwiki isn't likely to be less work than trying to migrate to mediawiki, either way we go, it's going to be a long ordeal.
Also a hosting move will likely be part of this new direction, as we pay a premium amount for limited services at our current host, and it's not flexible enough to implement all the things we want to use.
How all this will happen while I keep burning myself out on my day job is a topic of ongoing discussion.
-
The hope is to keep everything as intact as possible. We know some things will be lost and/or damaged, but overall it is the right decision to make. We are operating on software that is over two decades old, and if that doesn't scare the crap out of you, think about it this way:
Who still has and uses an original iPhone?
Or Android?
We predate both.
In fact, if you don't count Blackberry, we predate smartphones entirely.
This site has been around and operating on SMF since the days when people were still refusing to jump from 98ME to Windows XP because it was too new and their printer wouldn't work with XP.
I think we have had a good run on SMF, but the world is a very different place now and we are going to have to move on.
Def
-
I like the idea of upgrades
but also know that they can be a pain and scary :ahhh :ahhh :ahhhPlus all the complaints from people that don't like change

-
Yeah, I am already cringing at all the "it's not the same" and "it's not MTO anymore" that are inevitable.
Like I said, there's not much else we can do. It's either change or ride the software into the ground.
Def
-
I suspect that there is allways someone who doesnt like changes and those who dont like much current platform. I just hope plans goes well without big hiccups.
-

-
This needs to happen to keep this place up and running

-
Bringing this one back because I have been working on the plans again lately and I think it's a good time to start sharing where we are at. Here is the migration plan I have developed so far, translated into English by our friendly neighborhood AI, and subject to change as necessary:
Goal: Move all Multitool.org properties to a new, modern, Fediverseâcapable hosting environment wit\h minimal downtime, maximum safety, and a clean, staged rollout.
1. Hosting Providers We Selected
You were choosing between Hetzner and Elestio. We ended up with a hybrid recommendation:Primary Hosting (Main Sites, High Performance):
Hetzner (Germany/Finland)
Best price/performance ratio in Europe-Excellent for WordPress, MediaWiki, PrestaShop, NodeBB
-Bare metal or cloud instances
-Very stable, very fast, very inexpensiveFediverse + Managed Services:
Elestio (Luxembourg)
Fully managed deployments-Excellent for PixelFed, NodeBB, Mastodon, Lemmy, etc.
-Hardened security, automatic updates, backups
-Tailorâmade for the kind of Fediverseânative stack youâre buildingYour final leaning:
You were strongly leaning toward Elestio for the Fediverse components and possibly for the forum, because of the managed security and the fact that they specialize in exactly this kind of setup.2. Old â New Software Stack
Hereâs the exact mapping we discussed:Current Site Old Software New Software
Multitool.org (main site) Joomla WordPress
Forum.Multitool.org SMF NodeBB
SAKWiki.com TikiWiki MediaWiki
MTO Gallery Custom / legacy PixelFed
EDCâTV WordPress (stays WP) WordPress (migrated)You also mentioned possibly making everything Fediverseâcompliant, but we agreed:
-PixelFed is perfect for the gallery
-NodeBB has ActivityPub support
-MediaWiki has partial ActivityPub support (but not perfect)
-WordPress can be ActivityPubâenabled via pluginSo the plan is Fediverseâenhanced, not Fediverseâexclusive.
3. Build Order (Development Order)
You clarified this yourself â and it was the right call:Build the Forum FIRST (NodeBB)
-Most complex
-Needs the longest testing period
-Your moderators need 3 months to learn, tweak, and debugThis becomes the âmodelâ for the rest of the migration
Build PixelFed
-Easy to deploy
-Lets you start populating media early
-Helps unify branding and social presenceBuild the new Multitool.org (WordPress)
-Lowâinteraction site â lowârisk migration
-Good candidate for early content import testingBuild EDCâTV (WordPress)
-Straightforward
-Lets you test video embeds, podcast feeds, etc.Build SAKWiki (MediaWiki)
-Large content import
-Needs careful template/module migration
-Should be done after the team has experience from earlier migrations4. Release Order (Public Rollout Order)
This is different from the build order â exactly as you said.Multitool.org (main site)
Low interaction â safest to cut over first.EDCâTV
Also lowârisk, mostly contentâdriven.PixelFed
Once the main sites are stable, you introduce the Fediverse component.SAKWiki
Highâtraffic, highâimportance, but stable once migrated.Forum (NodeBB)
The final and most sensitive migration.
By this point, moderators have had 3 months of training and testing.5. Migration Method
This was the backbone of your plan:
Run the new server in parallel with the old one
No downtime, no surprises.
Build everything on the new server first
Nothing touches the live sites until fully tested.
Import content one site at a time
Starting with lowâinteraction sites.
Shadow Production Phase
Before each cutover:-DNS still points to old site
-New site runs in parallel
-You and your team test everything
-Only when approved â switch DNS
Full rollback plan
Because the old server stays online until the entire migration is complete.6. Estimated Timeline
You said: âAll going well, this should take less than three months.âHereâs the breakdown we built:
Month 1
-Deploy servers (Hetzner + Elestio)
-Build NodeBB forum
-Begin moderator training
-Begin PixelFed deploymentMonth 2
-Build Multitool.org (WordPress)
-Build EDCâTV (WordPress)
-Begin content imports
-Continue forum testingMonth 3
-Build SAKWiki and Multitool Encyclopedia (MediaWiki)
-Finalize PixelFed
-Build new MTO Store (WooCommerce)
-Finalize all content imports
-Begin staged DNS cutovers
-Forum goes last after full moderator approval7. Why This Plan Works
Because itâs:-Incremental
-Lowârisk
-Fully reversible
-Compatible with your workflow
-Designed for your cohostsâ technical comfort level
-Optimized for Fediverse integration
-Built around your real traffic patternsItâs the right plan for the size and complexity of your ecosystem.
I've selected NodeBB as the replacement for SMF as it will provide the closest to our current configuration as change = BAD. If we can keep the interface as close as possible, it should minimize user complaints, although with the errors and downtime we have been experiencing lately I think members will be glad to see something done about it, and recognize that we have had 20 years out of SMF and that's pretty damned good IMHO.
Def
-
Oh, and I expect to do much of the heavy lifting behind the scenes since its a fresh build, only calling on Micah when I need to or when there's serious stuff to do. He's busy with work and since it's a fresh, clean install on a new server, and I have various AI's to back me up I should be able to handle much of the build myself.
When it comes to content migration, I'll probably leave that to Micah because we don't want me to smurf up 20 years of content.
We will also be changing software for some sites, either because of convenience, updating or that it's just a good idea.
The main site at MTO is currently running on Joomla, and that will be migrated to Wordpress.
The Wikis will go to MediaWiki, which (I believe) is what Wikipedia is running on, so it will be supported better/longer than TikiWiki.
The MTO Gallery, which is running on Gallery 3 hasn't been supported in many years and was barely useable when we created it, and we will replace it with PixelFed, which we experimented with last year. This not only allows us to have a photo hosting website like Photobucket or Imagur that can be linked to on the forum, but also it provides an IG like platform capable of operating independently.
The MTO Store is currently running on Prestashop, which wasn't cheap and has been largely dysfunctional the entire time we have had it. WooCommerce is free, open source (like most of what we use here) and integrates better with WordPress, so it makes more sense to change over.
As mentioned, the forum goes to NodeBB, not because it's the best but because it resembles SMF the closest... and it's pretty damned good. As per the AI:
NodeBB is honestly one of the smartest moves you can make for Multitool.org â especially given the size of your community, your moderators, and the longâterm Fediverseâenhanced ecosystem youâre building. Since youâre seriously considering it as the SMF replacement, hereâs the deepâdive you actually need: what NodeBB is, why itâs so different from SMF/PhpBB-era forums, what it excels at, and what to expect when you run it on your new servers.
Iâll keep this tailored to your use case, not generic marketing fluff.
What NodeBB Actually Is
NodeBB is a modern, realâtime, JavaScriptâbased forum platform built on:
- Node.js (server)
- MongoDB or Redis (database)
- WebSockets (live updates, no page reloads)
- A modular plugin/theme system
- A fully responsive, mobileâfirst UI
Itâs not a âforum scriptâ like SMF â itâs a web application.
This is why it feels fast, smooth, and modern compared to the old PHP forum engines.
Why NodeBB Is a Massive Upgrade from SMF
Hereâs the stuff that matters to you and your community:
1. Realâtime everything
- Replies appear instantly
- Notifications are live
- Typing indicators
- No page refreshes
It feels like Discord + a forum had a baby.
2. Mobile experience is actually good
SMF on mobile is⌠well, SMF on mobile.
NodeBB is:
- Touchâfriendly
- Fast
- Clean
- No zooming
- No broken layouts
Your users will feel like the forum finally entered the 2020s.
3. Plugin ecosystem is strong
You get:
- Polls
- Reactions
- Chat
- Awards
- Uploads
- Social login
- SSO
- ActivityPub (Fediverse integration)
- SEO tools
- Spam protection
- Analytics
And unlike SMF, plugins donât break your forum every update.
4. Themes are modern and customizable
Persona (default)
Harmony (newer, cleaner)
Plus dozens of community themes.You can also fully customize CSS without hacking core files.
5. Performance is insane
NodeBB is lightweight and fast even on modest hardware.
On Hetzner:
- A CX32 or CPX31 instance will handle your entire community easily
- Redis is extremely fast for realâtime workloads
- Caching is builtâin
Your forum will feel instant.
6. Moderator tools are excellent
Your mod team will love:
- Live flagging
- Realâtime chat with users
- Post queues
- IP tools
- User notes
- Categoryâlevel permissions
- Bulk moderation
And because itâs modern, itâs intuitive â no more SMFâstyle âwhere the hell is that setting?â
7. ActivityPub support
This is huge for your ecosystem.
NodeBB can:
- Publish posts to the Fediverse
- Receive replies from Mastodon/Pleroma/etc.
- Let users follow categories or threads from their Fediverse accounts
This fits perfectly with your PixelFed + WordPress ActivityPub + MediaWiki plan.
What Running NodeBB Is Like (Admin Experience)
The Admin Panel
Clean, modern, and organized.
Everything is in:- General
- Users
- Plugins
- Themes
- Appearance
- Settings
- Advanced
No more digging through 20 pages of SMF settings.
Updates
- One command updates the whole forum
- Plugins update cleanly
- No template conflicts
- No âwhite screen of deathâ
Itâs the opposite of SMFâs fragile mod system.
Backups
Because it uses Redis or MongoDB:
- Backups are fast
- Restores are easy
- No 500MB SQL dumps
Elestio even automates this if you host there.
What You Need to Run It
Server Requirements
- Node.js
- Redis or MongoDB
- Nginx reverse proxy
- Letâs Encrypt SSL
On Hetzner, this is trivial.
On Elestio, itâs oneâclick.
Your Expected Cost
If hosted on Hetzner:
- âŹ18ââŹ26 CAD/month for a CPX31
- Redis included
- Plenty of power for your traffic
If hosted on Elestio:
- $45â$70 CAD/month
- Fully managed
- Automatic updates
- Automatic backups
- Hardened security
You were leaning toward Elestio for the forum because of the security and maintenance benefits.
Migration from SMF
NodeBB has an official SMF importer.
It brings over:
- Users
- Passwords (converted)
- Categories
- Boards
- Topics
- Posts
- Attachments (optional)
You will need:
- A staging server
- A test import
- Moderator training (you planned 3 months)
- A final import before cutover
This fits perfectly into your migration timeline.
What Your Community Will Notice
Instant improvements
- Faster
- Cleaner
- Easier to use
- Better mobile
- Better notifications
- Better search
- Better moderation
- Better media handling
What They Might Resist
- The UI is different
- Some old SMF workflows disappear
- Some users will miss the âclassic forum lookâ
But after a week, most people prefer NodeBB.
Bottom Line
NodeBB is:
- Modern
- Fast
- Realâtime
- Fediverseâready
- Easy to maintain
- Perfect for your ecosystem
- A massive upgrade from SMF
- Futureâproof
And it fits exactly into the migration plan we built.
The higher use sites (like the forum) will end up going on a managed plan so we have better resources when there are issues. Since I'll be doing some of the building I am hoping I will have a better understanding of how all of the magical gremlins work, and either fix stuff or be able to better pinpoint issues for Micah, or better yet, release the automatic server monkeys to deal with issues for us.
Micah is an extremely valuable resource and we have used him very heavily over the years, but the man deserves to have a life, and his day job is already overworking him, so the less pressure that we can put on him, the more likely it is he will start to enjoy his life again.

This should future proof us (hopefully) until our 30th Anniversary.
Def
-
I'm happy to hear that things are moving towards the upgrade

-
Honestly, it should have been done before now, but due to a lack of competence on my part, a lack of time on Micah's and the difficulties involved in finding a server company I can trust, it just hasn't been possible until now.
It also won't be cheap running two servers (technically three) for at least three months, but in the end it will be worth it.
Def
-
-
So we are going to migrate SAKWiki from running in Tikiwiki to Mediawiki - Is that correct?
Is Tikiwik content compatible with Mediawiki? ie
All the format commands such as highlights, bolding, italics, numbered lists, bulleted lists, divider panels, columns, page layout etc?
Are the image galleries organised in the same way?
Are all the image display commands compatible? ie Display, descriptions, positioning on the screen, display on screen vs link to image etc?
Will all the hyperlinks work internal and external?Or is there some migration tool?
And basically the comments from my post above -
The usability, user-friendliness of the Wiki has been massively transformed over the last 10 years
I hope that work was not all in vain! -
There is a migration tool.
I'll tell you now, these are never 100% and there will be some formatting issues and some straightening up to do, but it should get us most of the way there. All of the info and pictures should make it, and we will have everything backed up just in case.
It's a risk but the alternative is to potentially lose it all by running a lesser platform.
MediaWiki should be a good step up and insure the future of SAKWiki a lot better than TikWiki.
Def
-
The biggest issue we have both with upgrading and migrating the wikis is the way it stored images in the past, since discontinued even in the tikiwiki software, which is why we are not able to even upgrade it further than we have currently.
None of the automated migration tools have worked when I tried them, which means we need to do it manually.
there's a lot of things to consider on all the sites/platforms that we'll have to look closely on a case by case basis, and hope for the best...
Time is not our friend, but hopefully we can have some sort of interim dual platform to fully test.
-
Hmmmm
We have about 5000 images, 240 galleries (in a hierarchy tree with 5 roots) and about 800 Wiki pages
Average links on a Wiki page to other pages or images is probably around 25 - The tools page has 60
Could be a long night!
-
We have about 5000 images, 240 galleries (in a hierarchy tree with 5 roots) and about 800 Wiki pages
Average links on a Wiki page to other pages or images is probably around 25 - The tools page has 60
Could be a long night!
I am well aware. Perhaps as Grant suggested we may have to look at several smaller server options (to better control requirements, and limit the load of one setup taking them all down etc)
@Grant Lamontagne said:
On Hetzner:- A CX32 or CPX31 instance will handle your entire community easily
I have a Hetzner account and don't see those suggested package options available, but google does show some other results on other pages that reference them, so maybe those are legacy names.
We do have node.js on current setup, but I am not seeing a clear setup path for nodebb on our current package without a lot of command line stuff I am not 100% comfortable with doing myself without a lot more reading...
I fear this is going to be the entire Fediverse experience, lots of manual commandline stuff to get it all setup and working, without mentioning the migrations from other environments.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đ
Register Login