I've mocked up a fork of jrouter to make it an AURP access concentrator to see if it would be possible to simplify the setup and maintenance of a GlobalTalk type setup. Instead of every user needing to know and configure every other user's IP address, they only need to configure a single cloud endpoint. In theory users could be added and removed instantly without any human involvement.
Since anonymous & automated is a recipe for chaos I've tied it into Discord's OpenID Connect interface to limit access to people with valid accounts on the TD Discord server, and by requiring a Discord identity there is an as-yet-unimplemented way to block naughty accounts. I only ask Discord for an ID number, a name to display, and avatar image and it prompts to user to approve sharing information. Right now the ID number used to register any endpoints and the registered IP addresses are visible to anybody logged in, but that will be trivial to hide once I know traffic is routing properly. Nothing is saved at this point, so if the service crashes or gets restarted for any reason, like any code change, all users and endpoints are forgotten.
#TODO: save state
Bandwidth in The Cloud is so cheap and amount of AppleTalk traffic that can realistically be used is so small by modern standards that I don't expect that relaying all traffic to get close to the included traffic budget of my cheap cloud VM let alone cost me anything.
Since anonymous & automated is a recipe for chaos I've tied it into Discord's OpenID Connect interface to limit access to people with valid accounts on the TD Discord server, and by requiring a Discord identity there is an as-yet-unimplemented way to block naughty accounts. I only ask Discord for an ID number, a name to display, and avatar image and it prompts to user to approve sharing information. Right now the ID number used to register any endpoints and the registered IP addresses are visible to anybody logged in, but that will be trivial to hide once I know traffic is routing properly. Nothing is saved at this point, so if the service crashes or gets restarted for any reason, like any code change, all users and endpoints are forgotten.
#TODO: save state
Bandwidth in The Cloud is so cheap and amount of AppleTalk traffic that can realistically be used is so small by modern standards that I don't expect that relaying all traffic to get close to the included traffic budget of my cheap cloud VM let alone cost me anything.