Re: [battery] Are there new use cases for battery API? (#64)

@marcoscaceres you requested to discontinue this work in https://github.com/w3c/battery/issues/64#issue-2307258382 The WG did not support such a request and does not discontinue this specification per https://github.com/w3c/battery/issues/64#issuecomment-2125671911 I closed this issue in response to that. Then this discussion drifted to other topics.

Other topics are however better discussed in existing topic-specific issues:

- Use cases discussed in #25

- Permission model was discussed in #5, that led to #10 fixed by #13

However, before jumping on these issues, please note:
 
Issue #5 has a lot of helpful historical context. Before filing a new issue or chiming in, I ask people interested in making well-informed contributions to revisit the previous discussions open minded. Based on that specific discussion a mitigation was specified and it seems the intent to implement that mitigation was put on hold due to Akamai's feedback that such a change would break its open-source library. I believe a reasonable course of action here would be to revisit that intent given the mitigation was considered to be effective against unwanted use.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/battery/issues/64#issuecomment-2135318260 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 28 May 2024 14:11:01 UTC