Danish Arora

**Weekly Update** - _achieved_: PR ready and currently in review-iteration phase ( #1697 ) - _next_: to be merged

> Note that Status is contemplating using named shard so I don't think we can fully deprecate. Moving this back to triage. Once we have confirmation in either direction, we...

Thanks for the clarification! Sounds great. > Named sharding can be deprecated across the clients. This does remain blocked on js-waku until we allow js-waku to connect/work with The Waku...

> Moving to TODO for now. @weboko What is the acceptance criteria?

Another working item from this issue: https://github.com/waku-org/js-waku/issues/2018

- republish/move the size-limit script to a more accessible location - remove the fields that are not as useful (running time, etc) - look at coverage

@fbarbu15 I'm not sure I fully understand this issue. `clusterId` is indeed taken into account with `ApplicationInfo`. What am I missing? https://github.com/waku-org/js-waku/blob/4db508b962736426f4897995a2b525c82fe0ba37/packages/utils/src/common/sharding.ts#L63-L70 cc @waku-org/js-waku-developers

This seems to now be resolved with https://github.com/waku-org/js-waku/pull/2021 cc @fbarbu15

a rating of A can be part of iterative PRs

> These points are identified as blocker because usage of some STUN/TURN servers kills the purpose of Waku usage and creates censorship risks if it is done not in an...