Welcome to #Berlin (& #Brrrlin) fellow #Mozillians! Be sure to check out the Berlin Victory Column, AKA the Siegessäule. Photographed from a bus, got a face-on view of the bronze sculpture of #Victoria, #goddess of #victory.
#Siegessaeule #VictoryColumn #busRide #busView #noFilter
https://en.wikipedia.org/wiki/Berlin_Victory_Column
https://en.wikipedia.org/wiki/Victoria_(mythology)
@slightlylate @torgo @Google never? really asking me to do your #LMGTFY homework?
Like https://www.w3.org/TR/contacts-manager-api/
Everything B2G was standards-track.
& @W3C @ContactsAPI variants like:
https://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/contacts.html
https://www.w3.org/TR/2010/WD-contacts-api-20100121/
https://www.w3.org/TR/2014/NOTE-contacts-api-20140114/
@slightlylate @torgo no straw-people there. Statements Dan outlines, argues against, are made by many webdevs.
Also, Alex, WTF Contacts API explainer has no history? Can you please ask @Google folk who write specs to Google spec names first and document?
Very well-written @torgo; quite timely for those of us at #Brrrlin.
The arguments you’re fighting are often made, whether by @slightlylate or others.
Aside: WTF another ContactsAPI? & ZERO mention of past attempts e.g.
https://wiki.mozilla.org/WebAPI/ContactsAPI and https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/API/Contacts_API
https://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/contacts.html
https://www.w3.org/TR/2010/WD-contacts-api-20100121/
https://www.w3.org/TR/2014/NOTE-contacts-api-20140114/
https://www.w3.org/TR/2015/NOTE-contacts-manager-api-20150602/
A simple Google search of W3C Contacts API revealed the above in a matter of minutes.
The "Explainer":
* https://web.archive.org/web/20200126204921/https://github.com/WICG/contact-api
has no mention of "prior / previous attempts", prior W3C Notes, etc.
Do Google engineers even bother to Google something before making shit up?
I’m assuming no because the alternative is worse (that they did and willfully omitted history from the Explainer).
If anything, including references to these past attempts (and reasons why they failed) would’ve been a great way to make a new proposal look better.
Preparing for #Brrrlin All Hands, reflecting on a web strategy & vision aligned with @Mozilla mission, asked #webstandards co-workers to do so too.
Some thoughts:
* people over tech (it’s not neutral)
* empower those more vulnerable, less privileged
* simple, minimal, secure, private by default
* accessible to view, author, *and* code
Previously:
* https://tantek.com/2020/009/t1/technology-force-multiplier-not-neutral
* https://tantek.com/2019/353/t1/tech-plumbing-framing-dweb-problematic
* https://tantek.com/2020/010/t2/indieweb-community-inclusive-anarchistic-punk
* https://tantek.com/2018/133/t1/mozilla-manifesto-addendum
Re-reading:
* https://www.mozilla.org/en-US/mission/
* https://www.mozilla.org/en-US/about/manifesto/
* https://www.mozilla.org/en-US/about/manifesto/details/
* https://www.w3.org/2001/tag/doc/ethical-web-principles/
And considering the problems with the "Contract for the Web" (https://contractfortheweb.org/) such as numerous signatories that actively violate its own principles, and profit from doing so.