openoms on Nostr: Fixed it seems by adding the bostr2 instance to General relays also: ...

Fixed it seems by adding the bostr2 instance to General relays also:

quoting nevent1q…hlua

Are you using torsocks to run bostr2?

I figured if the bouncer is not torified the outgoing websocket connections are leaking the public IP of the server to the connected relays. (The client is safe.)

My systemd service here in a #Raspiblitz PR: https://github.com/raspiblitz/raspiblitz/pull/4724/files#diff-0ffb074f869361719e03a7d89046a39b7890b10abe0895f60c0d8a50c3c3b520R136-R160

This amd the quoted post was broadcasted over Tor only from Amethyst to a bostr2 and a strfry instance.