Re: HBLink: Adhoc clients with routing rules, conferences etc

Cort N0MJS <n0mjs@...>

That would be in my part of the project, most likely.

I’d like to have the whole thing worked out first though… whitelists imply someone else will want a blacklist. For the whole system (most of you would call that a “master”)? Or based on a per-client connection? Do we just whitelist destination TGIDs? What about source subscriber IDs?

When we have general consensus, and it doesn’t extend too far (it was intended to be a protocol stack, not a full-blown application), I’ll add it.

0x49 DE N0MJS

On Jan 24, 2018, at 3:08 PM, Nicola IT9FXF via Groups.Io <onetechct@...> wrote:

Hi Steve,
I read in this post that you were thinking of integrating a whitelist when using hblink as a simple master. It would be interesting.
Have you planned something?


Cort Buffington

Join to automatically receive all group messages.