Context
I've been building Torialink, an open-source Polytoria verification bot for Discord written in Rust. It's inspired by Bloxlink's model and supports per-guild verification, role binds, and a few other features on top of the standard bio verification flow.
I also opened a support ticket (ticket-00146) on March 27 to discuss API access for the project, but haven't gotten a response yet, so hopefully this is a better place to have the conversation.
The proposal
VerifyBot looks like it hasn't been actively maintained for a while, and I'd love to take that on if the team is open to it. What I'm specifically asking is whether I could open a PR replacing the current codebase with Torialink, effectively making it the new official implementation.
I think this is worth considering for a few reasons. The current bot uses discord.js directly, which is a library rather than a framework, and while that's a valid choice it tends to add a lot of overhead for a bot of this scope. Things like command registration, event handling and error boundaries all have to be wired up manually, which makes the codebase harder to maintain and extend over time. There are also quite a few spots where the typing falls back to any, which loses most of the benefit of using TypeScript in the first place.
Torialink is written in Rust, so it sidesteps all of these issues by nature. It's also fully open source, and given that Polytoria itself is heading in that direction, having a transparent and community-auditable verification bot feels like a natural fit. I also think there's a real path for something like this to become an officially recognized solution, similar to how Bloxlink eventually became the standard for Roblox.
I'm also completely fine renaming it to VerifyBot if the proposal is accepted. Torialink was just the name I gave it in case this didn't work out and it had to remain a separate project, which would only bring more segmentation into the ecosystem, something I'd rather avoid.
I'm not looking to just drop a PR and disappear either, I'd genuinely like to maintain it long term.
Happy to discuss architecture, answer any questions, or adjust scope based on what the team actually needs. Just wanted to ask before doing anything.
Torialink repo: https://git.exefer.xyz/exefer/torialink
Context
I've been building Torialink, an open-source Polytoria verification bot for Discord written in Rust. It's inspired by Bloxlink's model and supports per-guild verification, role binds, and a few other features on top of the standard bio verification flow.
I also opened a support ticket (ticket-00146) on March 27 to discuss API access for the project, but haven't gotten a response yet, so hopefully this is a better place to have the conversation.
The proposal
VerifyBot looks like it hasn't been actively maintained for a while, and I'd love to take that on if the team is open to it. What I'm specifically asking is whether I could open a PR replacing the current codebase with Torialink, effectively making it the new official implementation.
I think this is worth considering for a few reasons. The current bot uses discord.js directly, which is a library rather than a framework, and while that's a valid choice it tends to add a lot of overhead for a bot of this scope. Things like command registration, event handling and error boundaries all have to be wired up manually, which makes the codebase harder to maintain and extend over time. There are also quite a few spots where the typing falls back to
any, which loses most of the benefit of using TypeScript in the first place.Torialink is written in Rust, so it sidesteps all of these issues by nature. It's also fully open source, and given that Polytoria itself is heading in that direction, having a transparent and community-auditable verification bot feels like a natural fit. I also think there's a real path for something like this to become an officially recognized solution, similar to how Bloxlink eventually became the standard for Roblox.
I'm also completely fine renaming it to VerifyBot if the proposal is accepted. Torialink was just the name I gave it in case this didn't work out and it had to remain a separate project, which would only bring more segmentation into the ecosystem, something I'd rather avoid.
I'm not looking to just drop a PR and disappear either, I'd genuinely like to maintain it long term.
Happy to discuss architecture, answer any questions, or adjust scope based on what the team actually needs. Just wanted to ask before doing anything.
Torialink repo: https://git.exefer.xyz/exefer/torialink