Epic: arewedistributedyet.com browser test suite

[flyingzumwalt]

Set up an entry point Website (or github repo) for people to learn about and track this work.

This current github repo might be the right location, rather than setting up a proper website, but in that case we must at least make the landing page provide appropriate information.

[ghost]

I'm not sure we reached consensus in the other issue discussing the domain name, and I can't find it. I vaguely recall that we might have decided on arewebrowseryet.com and just had a better idea. The name should make sense from the perspective of a browser and its users, and from this perspective "are we browser yet" imho doesn't.

AreWeDistributedYet or AreWeP2PYet probably make more sense, and they're in line for example with the HTML5 Audio test suite that SoundCloud built back then, which is called AreWePlayingYet.

[flyingzumwalt]

That is a splendid idea. I didn't see much benefit to creating an actual website for "are we in web browsers yet" but I totally see value in creating arewedecentralizedyet or AreWeDistributedYet, which can evolve with us as we proceed along the path of upgrading the internet.

[olizilla]

I think this is important and I'm up for getting it started.

I see it as a brief intro to the goal of p2p web and that we need some additional apis in browsers to a make it happen... followed by a list of apis, ideally with a test for it’s existence, a short summary on what it would allow, and a list of projects that want it.

I'm keen to open this up. dat/beaker, scuttlebutt, ethereum/metamask all need some movement from the browsers to improve the ux of p2p in browsers... of note,

• scuttlefriends pushing PRs for custom protocol handlers in firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1428446
• pfrazee's wishlist: https://gist.github.com/pfrazee/cb29ce22b2ad7e4ffe418d7c673b1b4b via: https://twitter.com/pfrazee/status/935160704792973312

[olizilla]

ideally with a test for it’s existence

It's worth noting that I'm assuming this won't be possible in many cases. We're more likely to be pushing for WebExtension apis rather than changes to the BOM, so live, check-my-current- browser style tests may not be feasible.

[olizilla]

See https://github.com/ipfs/in-web-browsers/issues/35 for peoples initial thoughts on the list of apis needed.

[olizilla]

• http://www.areweplayingyet.org/
• http://arewewebextensionsyet.com/
• https://wiki.mozilla.org/Areweyet (incomplete but interesting index of areweXyet sites)

[olizilla]

Support the conversation with browser vendors by documenting what's needed and why.

TODO:

• [x] Agree name and register domain.
• [ ] Collate initial list of roadblocks and apis needed.
• [ ] Built as a static website published to ipfs, backed by a repo with a clear mechanism to add additional tests / features / roadblocks.
• [ ] Publish as a progress report with the list of apis, ideally with a test for it’s existence, a short summary on what it would allow, and a list of p2p projects that want it.

[lidel]

I marked the first TODO as done: a suitable domain seems to be in our hands already :)

• Registered Domain Name: AREWEDISTRIBUTEDYET.COM
• Creation Date: 2017-03-01T09:24:33Z

[victorb]

@lgierth do you know where this domain is located? Couldn't find it in dnsimple

[ghost]

The registration is in gandi. We haven't used it for anything yet so I didn't bother setting it up in dnsimple. You should be able to just create it there.

[victorb]

The website and Github repository has now been setup, the work described in the top-level issue description has been solved.

But what's described in the title of the issue is not, we don't have a test suite we can run.

Should we close this issue and track that somewhere else?

[lidel]

A basic test page was added in https://github.com/ipfs/in-web-browsers/pull/154: Preview: https://ipfs.github.io/in-web-browsers/ipfs-protocol-handler-support-tests.html

Making it easier to eyeball and moving to AWDY hostname would be next step.