Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

10, etc: Consider repositioning Waku "resource-restricted" to "efficient" to be more positive #467

Closed
oskarth opened this issue Oct 25, 2021 · 4 comments

Comments

@oskarth
Copy link
Contributor

oskarth commented Oct 25, 2021

Problem

There have been cases where people, including protocol devs, take "resource restricted devices/environments" to mean that Waku only focuses on this. And that, therefore, there's a need for some other protocol that doesn't have this restriction.

This presents a false picture. One idea to focus it to be more positive, such as being efficient, running everywhere, and being modular. We are doing this to some extent in https://rfc.vac.dev/spec/10/ but could probably do it better.

Also Nimbus seems to have encountered a similar problem, cc @arnetheduck

Acceptance criteria

  • Consensus on, if, and how to re-phrase it
  • Updated main specs
@jm-clius
Copy link
Contributor

Yeah, I agree with the terminology change. "Efficient" could also more easily imply -> "to the extent required by the environment". Still catching up so I might have missed it, but was there a specific trigger for this?

@jm-clius
Copy link
Contributor

@oskarth not sure whether to move this "In Progress" or "Backlog", but "In Progress" seemed most reasonable. You may be waiting for more comments.

@oskarth
Copy link
Contributor Author

oskarth commented Nov 1, 2021

(trigger mention in chat)

Not actively working on it, I'd like to let it simmer a bit and see if we can make the reframing a bit more cohesive. For example, could we turn 5 goals here https://rfc.vac.dev/spec/10/#motivation-and-goals into something that everyone can enumerate easily and make it stand out from comparative solutions?

@jimstir
Copy link
Contributor

jimstir commented Jun 14, 2024

Issue moved here

@jimstir jimstir closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants