Thanks Simon. However, that doesn't permit the use cases described above. The CIDR algo of
upstream-user-ipcould be a contrib/ script for a general-purpose
Let the outgoing IP/hostname ("localAddr") for upstream connections be determined from user info at dial time.
Example implementation: https://git.sr.ht/~mooff/soju/commit/42dcf362
Alternatively, a script could be run, passing e.g. username as arg 1
This lets an admin setup "vanity" hostnames, split users into e.g. staff.foo.bar; plebs.foo.bar, or even e.g. username.foo.bar (possible with reverse DNS delegation)
Fwiw a scenario is described herei
On Mon, Apr 4 2022 at 20:28:05 -0000, ~emersion email@example.com wrote:
Hm, can this really happen? If so we should clarify it in modern-irc. A timeout would be good to have regardless.
-- View on the web: https://todo.sr.ht/~emersion/soju/193#event-169079
I wondered if there's a timeout for the queuing mechanism - it's not guaranteed that a WHOIS command will generate a response, e.g. when the upstream queries remote servers
Also, it's just cool.
With no account, we connect you to our IRCd as ~firstname.lastname@example.org.
Registered, you're email@example.com, and can use BOUNCER to connect to other networks.
Motivation is to explore federation / identity based around that.
But, I thought appearing as firstname.lastname@example.org to other networks would be useful for your service, too.
For access lists, bans, knowing who you're talking to, etc.
The current version was tagged was last year, making it hard to tell if distro packages include more recent fixes like:
commit 60c5a82a76a639137a15a1446bc71434e432d8cd Author: Reto Brunner <email@example.com> Date: Sat Apr 17 18:50:35 2021 +0200 load config: do not overwrite the config upon error