Repository navigation
Use alternative server for finding nodes #683
Description
tox.chat domain name recently expired, and a few days passed since then, which likely means people responsible for it are no longer active. Because of this issue, Toxic can no longer find nodes and remains "offline" unless user uses /connect command or have nodes cached from when tox.chat still worked. There must be an alternative way of finding nodes, like relying on qTox server. I don't know how long that server will remain functional, since if it is affiliated with qTox client, the latter is already abandoned.
Activity
Green-Sky commentedon Jun 30, 2026
couple of things:
We are aware and will probably make the node list available in other places.
This "qtox server" is not affiliated with the curently maintained qtox, so be careful.
Oh and we technically still maintain toktok/qTox, so calling it abandoned is a bit harsh.
mistermakbeklll commentedon Jun 30, 2026
Original qTox seems to be abandoned, though I didn't notice there is fork.
Green-Sky commentedon Jun 30, 2026
Explicitly archived, with a link to the fork, yes.
basingwhisk commentedon Jul 1, 2026
Hi, I have created a third-party independent bootstrap node listing service at https://nodes.tox.st I have inherited all the DHT node data from nodes.tox.chat and am currently accepting new node submissions. Additionally, I strongly recommend implementing an option to allow users to switch between different bootstrap sources, preventing any single points of failure.
JFreegman commentedon Jul 2, 2026
As a temporary solution you can use the most recent list from the web archive.
@basingwhisk
This has always been possible in Toxic by replacing the nodes list with your alternative list and disabling nodes list updates in toxic's config.
basingwhisk commentedon Jul 2, 2026
#685 make a pull request to let user change their nodes update url
dartraiden commentedon Jul 10, 2026
btw tox.chat is back