Mahmoud Mazouz

@yellowhatter Please change your pull request's base branch to main (new default branch). And rebase your branch against `main` as it is missing a status check necessary to merge this...

@YuanYuYuan Please change your pull request's base branch to main (new default branch). And rebase your branch against `main` as it is missing a status check necessary to merge this...

@milyin Please change your pull request's base branch to main (new default branch). And rebase your branch against `main` as it is missing a status check necessary to merge this...

@OlivierHecart Please change your pull request's base branch to main (new default branch). And rebase your branch against `main` as it is missing a status check necessary to merge this...

@OlivierHecart Please change your pull request's base branch to main (new default branch). And rebase your branch against `main` as it is missing a status check necessary to merge this...

> Self-reference in `[dev-dependencies]` created some problems in the past for release. @fuzzypixelz @OlivierHecart could you provide more insight on this? This has been extensively discussed in https://github.com/rust-lang/cargo/issues/2911. @YuanYuYuan's workaround...

What works now: 1. Liveliness declaration, w/o the interest protocol, in brokered scenarios 2. Liveliness get, w/o the interest protocol, in brokered scenarios I disabled unused_variables and dead_code lints to...

@OlivierHecart I've addressed your remarks in 303ba3f, 1ae0b4f, b27525d and faeb4a6. Next I'll be merging `interests` into the pull request branch. Then I'll finally move on implement queries using tokens.

I just merged `interests` into the pull request branch. By the time I finished my first merge conflict resolution, there were more merge conflicts waiting for me. These development branches...

The `interest_id` fields in the liveliness implementation now correctly mirror the subscriber implementation.