1435798 - (libdweb) [meta] APIs for p2p web applications

Status: NEW

(WebExtensions :: General, enhancement, P5)

Description

[Dietrich Ayala (:dietrich)]

Meta-bug for collecting the WebExtensions API features required for building p2p web applications.

Comment 1

[willem]

Why does the github mirror for libdweb have to be archived? Aren't issues raised on github the same as bus here if you use a templates on github?

Comment 2

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

(In reply to willem from comment #1)

Why does the github mirror for libdweb have to be archived? Aren't issues raised on github the same as bus here if you use a templates on github?

Because code on github isn't actually a mirror, code in gecko is more of re-implementation inspired by code github & trying to keep two code bases in sync takes more time than it's worth. It is also that most issues raised can't be addressed in libdweb code base itself, it usually requires changes either in web extension code base or further down the stack in platform code base. Given that corresponding teams operate in bugzilla it's a lot more effective to report issues directly here as that it leaves me with more time to work on integrating libdweb as opposed to relaying issues back and forth.

Comment 3

[willem]

Okay makes sense just feels weird posting a but when you just have a question.

Does Libdweb support mobile yet?

Comment 4

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

(In reply to willem from comment #3)

Okay makes sense just feels weird posting a but when you just have a question.

For general discussions we still have an #dweb IRC channel

Does Libdweb support mobile yet?

There had being no effort put into it, however sammacbeth who is frequently on that IRC channel made a version of beaker compatible dat browser with libdweb & https://github.com/mozilla-mobile/reference-browser

Comment 5

[Madushan]

Is the p2p protocol effort has been abandoned? I've been monitoring the work for some time now and got to know some of the people working on it were let go. Just curious as to what's the future of this project.

Comment 6

[roithnac.sourn]

Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

Describe any areas of concern to which you want the accessibility team to give special attention: