Open Standards aren't about posting a publicly-readable spec. They're about getting critiques and and consensus from an open community of stakeholders (including multiple implementers).https://twitter.com/AmeliasBrain/status/1126235639270088704 …
-
-
There's a GitHub linked above with some feedback but little response. This is also shifting the goalpost, the *design* of the API doesn't appear to have been done in the open (again, GitHub with little comments), it was done in private meetings between FB and Google.
-
There is no immaculate conception for web APIs. The explainer is a request for collaboration and you can shape the future of the API by engaging on GH or OT. What is objectionable about that?
- 21 more replies
New conversation -
-
-
Nothing here is "shipped", it's in Origin Trials *specifically* to understand if it solves the problem. Won't be able to progress through the launch process without evidence that it does: https://developers.chrome.com/origintrials/#/view_trial/4544132024016830465 …
-
Other browsers don't have a low-risk experimentation system, so the situation is perhaps confusing. It's disappointing more browsers haven't built OT systems so that developer feedback can steer the conversation. Too much standards work gets done without customers in the loop.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.