Chrome's console reports:
Failed to install the extension Installs can only be initiated by one
of the Chrome Web Store item's verified sites
Failed to obtain the stream to switch to Installs can only be
initiated by one of the Chrome Web Store item's verified sites
getSwitchStreamFailed
(anonymous function)
Installer.onInstallResponse

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one
of the Chrome Web Store item's verified sites
Failed to obtain the stream to switch to Installs can only be
initiated by one of the Chrome Web Store item's verified sites
getSwitchStreamFailed
(anonymous function)
Installer.onInstallResponse

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

that way you can tweak your local Chrome extension to probably interwork with your self-hosted jitsi.
However, your video chat counterparts would have to download and install manually the Jitsi desktop streamer Chrome extension and they would have to make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you would have to provide your own Chrome web store desktop streamer whatever source code this is based upon. What you have found in your Chrome extension directory is not the source code, there is somewhere an executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to assume that it is not made available (yet). I think it is fair as it is up to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

3. In the copy folder, delete the folder "_metadata", the folder is generated by chrome browser, delete it.

4. Edit the js file "manifest.json", and change Line --------"matches": [xxxx]------- , in my laptop, I changed the line to ----------"matches": [ "*://jitsi.example.com/*", "*://jitsi.example.com/*/*"]-----------
Please note that I have setup an DNS server and point " jitsi.example.com " to my jitsi -meet server.

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

I agree with that Video Bridge is great OpenSouce SW and Jistsi is a great project.

As to the source code of the Chrome extension, I believe that it's the source code. Basically, Desktop streamer is not complex, It just invoke Chrome API to get the desktop stream. The "Binary" you said may be done by the Chrome.

that way you can tweak your local Chrome extension to probably interwork with your self-hosted jitsi.
However, your video chat counterparts would have to download and install manually the Jitsi desktop streamer Chrome extension and they would have to make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you would have to provide your own Chrome web store desktop streamer whatever source code this is based upon. What you have found in your Chrome extension directory is not the source code, there is somewhere an executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to assume that it is not made available (yet). I think it is fair as it is up to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

I believe Thomas is correct.
I have done the same thing Feng mentions months ago (search the list).

The manifest file, etc, is not the sourcecode (someone please correct me if
I'm wrong). Yes you can change it to work with your self-hosted
installation, like I did months ago.
But you still don't have the source and so all your clients would have to
do those some changes to get it to work.

Realistically, I see 2 choices here:

1) Jitsi releases the source and we each create our own extension and put
it in Chrome's web store
2) We write our own. As Feng points out, it shouldn't be too diificult.

I agree with that Video Bridge is great OpenSouce SW and Jistsi is a great
project.

As to the source code of the Chrome extension, I believe that it's the
source code. Basically, Desktop streamer is not complex, It just invoke
Chrome API to get the desktop stream. The "Binary" you said may be done by
the Chrome.

that way you can tweak your local Chrome extension to probably interwork
with your self-hosted jitsi.
However, your video chat counterparts would have to download and install
manually the Jitsi desktop streamer Chrome extension and they would have to
make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you
would have to provide your own Chrome web store desktop streamer whatever
source code this is based upon. What you have found in your Chrome
extension directory is not the source code, there is somewhere an
executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to
assume that it is not made available (yet). I think it is fair as it is up
to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and
conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its
own version of a desktop streamer into the Chrome Web store (as verified
site owner).
The question is whether to develop your own variant of a desktop streamer
or whether the Jitsi code for desktop streamer could be reused for that
purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of
the Chrome Web Store item's verified sites Failed to obtain the stream to
switch to Installs can only be initiated by one of the Chrome Web Store
item's verified sites getSwitchStreamFailed (anonymous function)
Installer.onInstallResponse

We are using a desktop extension here because obtaining desktop access
from a web page is only possible that way currently. No other options
are allowed for security reasons. The problem is with having a malicious
JS control the content of a page (and the ability to load sensitive
stuff there, like your bank account) and also having the possibility to
screen scrape and stream it.

There are plans of addressing the issue in a generic way so hopefully
extensions may not be needed soon.

However, this is not yet the case and it is difficult to know exactly
when it would happen.

We are currently thinking about the best way to make this work as
painlessly as possible. Asking everyone to pay for a developer account
and configure an extension of their own and then update it is not
particularly optimal ... however, if we don't find a way to do things in
a better way then we'll fall back to that.

Emil

···

On 21.07.14, 10:08, Feng Jinjun ���� wrote:

Thomas,

I agree with that Video Bridge is great OpenSouce SW and Jistsi is a great project.

As to the source code of the Chrome extension, I believe that it's the source code. Basically, Desktop streamer is not complex, It just invoke Chrome API to get the desktop stream. The "Binary" you said may be done by the Chrome.

that way you can tweak your local Chrome extension to probably interwork with your self-hosted jitsi.
However, your video chat counterparts would have to download and install manually the Jitsi desktop streamer Chrome extension and they would have to make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you would have to provide your own Chrome web store desktop streamer whatever source code this is based upon. What you have found in your Chrome extension directory is not the source code, there is somewhere an executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to assume that it is not made available (yet). I think it is fair as it is up to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of the Chrome Web Store item's verified sites Failed to obtain the stream to switch to Installs can only be initiated by one of the Chrome Web Store item's verified sites getSwitchStreamFailed (anonymous function) Installer.onInstallResponse

I know that silence means you and your team are aware of the emails and are
not ignoring us users.

We are using a desktop extension here because obtaining desktop access
from a web page is only possible that way currently. No other options
are allowed for security reasons. The problem is with having a malicious
JS control the content of a page (and the ability to load sensitive
stuff there, like your bank account) and also having the possibility to
screen scrape and stream it.

There are plans of addressing the issue in a generic way so hopefully
extensions may not be needed soon.

Very cool! Hopefully we'll see something before the end of next year!

However, this is not yet the case and it is difficult to know exactly
when it would happen.

We are currently thinking about the best way to make this work as
painlessly as possible. Asking everyone to pay for a developer account
and configure an extension of their own and then update it is not
particularly optimal ... however, if we don't find a way to do things in
a better way then we'll fall back to that.

Emil

All the best,
Jungle

On 21.07.14, 10:08, Feng Jinjun 冯金军 wrote:

Thomas,

I agree with that Video Bridge is great OpenSouce SW and Jistsi is a great project.

As to the source code of the Chrome extension, I believe that it's the source code. Basically, Desktop streamer is not complex, It just invoke Chrome API to get the desktop stream. The "Binary" you said may be done by the Chrome.

that way you can tweak your local Chrome extension to probably interwork with your self-hosted jitsi.
However, your video chat counterparts would have to download and install manually the Jitsi desktop streamer Chrome extension and they would have to make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you would have to provide your own Chrome web store desktop streamer whatever source code this is based upon. What you have found in your Chrome extension directory is not the source code, there is somewhere an executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to assume that it is not made available (yet). I think it is fair as it is up to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one of
the Chrome Web Store item's verified sites Failed to obtain the stream to
switch to Installs can only be initiated by one of the Chrome Web Store item's
verified sites getSwitchStreamFailed (anonymous function)
Installer.onInstallResponse

Peter,
In my opinion, the "Source Code" is the extension's source code, instead of the desktop streamer's source code. I know there is some binary to capture the screen or the window and convert it to a video stream. I don't think this part is done by jitisi guys, it is done by the Chrome Native API.

Please correct me if I am wrong, also point me the which binary is not opensource.

We are using a desktop extension here because obtaining desktop access from a web page is only possible that way currently. No other options are allowed for security reasons. The problem is with having a malicious JS control the content of a page (and the ability to load sensitive stuff there, like your bank account) and also having the possibility to screen scrape and stream it.

There are plans of addressing the issue in a generic way so hopefully extensions may not be needed soon.

However, this is not yet the case and it is difficult to know exactly when it would happen.

We are currently thinking about the best way to make this work as painlessly as possible. Asking everyone to pay for a developer account and configure an extension of their own and then update it is not particularly optimal ... however, if we don't find a way to do things in a better way then we'll fall back to that.

Emil

On 21.07.14, 10:08, Feng Jinjun 冯金军 wrote:

Thomas,

I agree with that Video Bridge is great OpenSouce SW and Jistsi is a great project.

As to the source code of the Chrome extension, I believe that it's the source code. Basically, Desktop streamer is not complex, It just invoke Chrome API to get the desktop stream. The "Binary" you said may be done by the Chrome.

that way you can tweak your local Chrome extension to probably interwork with your self-hosted jitsi.
However, your video chat counterparts would have to download and install manually the Jitsi desktop streamer Chrome extension and they would have to make the same manual changes once they would like to show their own screens.
Not sure whether this is the purpose of your self-hosted Jitsi installment.

So - for a proper and user friendly setup similar to jitsi.org - you would have to provide your own Chrome web store desktop streamer whatever source code this is based upon. What you have found in your Chrome extension directory is not the source code, there is somewhere an executable Jitsi desktop streamer in binary.

As there is no answer concerning the desktop streamer source we have to assume that it is not made available (yet). I think it is fair as it is up to the developers which piece of SW they make public and how.
I would like to thank them anyway for the fantastic video bridge and conferencing software here - great job!

that is correct. With a self hosted Jitsi one would have to provide its own version of a desktop streamer into the Chrome Web store (as verified site owner).
The question is whether to develop your own variant of a desktop streamer or whether the Jitsi code for desktop streamer could be reused for that purpose.
So my question was concerning the Jitsi desktop streamer source code.
Thanks
Thomas

Chrome's console reports:
Failed to install the extension Installs can only be initiated by one
of the Chrome Web Store item's verified sites Failed to obtain the
stream to switch to Installs can only be initiated by one of the
Chrome Web Store item's verified sites getSwitchStreamFailed
(anonymous function) Installer.onInstallResponse

Peter,
In my opinion, the "Source Code" is the extension's source code, instead
of the desktop streamer's source code. I know there is some binary to
capture the screen or the window and convert it to a video stream. I don't
think this part is done by jitisi guys, it is done by the Chrome Native API.

Please correct me if I am wrong, also point me the which binary is not
opensource.

We are using a desktop extension here because obtaining desktop access
from a web page is only possible that way currently. No other options are
allowed for security reasons. The problem is with having a malicious JS
control the content of a page (and the ability to load sensitive stuff
there, like your bank account) and also having the possibility to screen
scrape and stream it.

There are plans of addressing the issue in a generic way so hopefully
extensions may not be needed soon.

However, this is not yet the case and it is difficult to know exactly when
it would happen.

We are currently thinking about the best way to make this work as
painlessly as possible. Asking everyone to pay for a developer account and
configure an extension of their own and then update it is not particularly
optimal ... however, if we don't find a way to do things in a better way
then we'll fall back to that.

Emil

On 21.07.14, 10:08, Feng Jinjun 冯金军 wrote:
> Thomas,
>
> I agree with that Video Bridge is great OpenSouce SW and Jistsi is a
great project.
>
> As to the source code of the Chrome extension, I believe that it's the
source code. Basically, Desktop streamer is not complex, It just invoke
Chrome API to get the desktop stream. The "Binary" you said may be done by
the Chrome.
>
> You can check the chrome API here:
> https://developer.chrome.com/extensions/desktopCapture
>
> I guess the reason Jitsi guys use the extension is that desktop streamer
is global resource , the tab can not access the global resource, So the tab
access the global resource via the extension.
>
> Thanks
> jinjun
>
> -----邮件原件-----
> 发件人: dev-bounces@jitsi.org [mailto:dev-bounces@jitsi.org] 代表 Thomas
> Odorfer
> 发送时间: Monday, July 21, 2014 6:12 PM
> 收件人: Jitsi Developers
> 主题: [jitsi-dev] 答复: self hosted Jitsi meet desktop streamer
>
> Hi Jinjun,
>
> that way you can tweak your local Chrome extension to probably interwork
with your self-hosted jitsi.
> However, your video chat counterparts would have to download and install
manually the Jitsi desktop streamer Chrome extension and they would have to
make the same manual changes once they would like to show their own screens.
> Not sure whether this is the purpose of your self-hosted Jitsi
installment.
>
> So - for a proper and user friendly setup similar to jitsi.org - you
would have to provide your own Chrome web store desktop streamer whatever
source code this is based upon. What you have found in your Chrome
extension directory is not the source code, there is somewhere an
executable Jitsi desktop streamer in binary.
>
> As there is no answer concerning the desktop streamer source we have to
assume that it is not made available (yet). I think it is fair as it is up
to the developers which piece of SW they make public and how.
> I would like to thank them anyway for the fantastic video bridge and
conferencing software here - great job!
>
> BR, Thomas
>
>
>
> Am 21.07.2014 um 05:43 schrieb Feng Jinjun 冯金军 <jinjun.feng@polylink.net > >:
>
> Hi all,
>
> I also encountered this issue, the desktop sharing does not work.
>
> As Thomas said, we have to create our own chrome extension, Can Jitsi
guys opensource the extension code?
>
>
> Thanks
> Jinjun
>
> -----邮件原件-----
> 发件人: dev-bounces@jitsi.org [mailto:dev-bounces@jitsi.org] 代表 Thomas
> Odorfer
> 发送时间: Saturday, July 19, 2014 3:13 PM
> 收件人: Jitsi Developers
> 主题: Re: [jitsi-dev] self hosted Jitsi meet desktop streamer
>
> Hi Jungle,
>
> that is correct. With a self hosted Jitsi one would have to provide its
own version of a desktop streamer into the Chrome Web store (as verified
site owner).
> The question is whether to develop your own variant of a desktop
streamer or whether the Jitsi code for desktop streamer could be reused for
that purpose.
> So my question was concerning the Jitsi desktop streamer source code.
> Thanks
> Thomas
>
> Am 19.07.2014 um 01:22 schrieb Jungle Boogie <jungleboogie0@gmail.com>:
>
> Dear Thomas,
> --------------------------------------------
> From: Jungle Boogie
> Sent: Fri, 18 Jul 2014 14:43:56 -0700
> To: Jitsi Developers
> Subject: Re: [jitsi-dev] self hosted Jitsi meet desktop streamer
>>
>> Dear Thomas,
>> --------------------------------------------
>> From: Thomas Odorfer <odotom@gmail.com>
>> Sent: Fri, 18 Jul 2014 22:55:54 +0200
>> To: Jitsi Developers
>> Subject: Re: [jitsi-dev] self hosted Jitsi meet desktop streamer
>>>
>>> Hi,
>>>
>>> is the Jitsi desktop streamer extension for Chrome available under
>>> open source license (MIT)? Haven’t found any source yet.
>>
>> I don't think it is and I remember Emil saying you have to pay money
>> to google to add an extension to the extension market thing for Chrome.
>>
>>> - Thomas
>>
>> _jungle_
>>
>
>
> I found my thread:
> http://lists.jitsi.org/pipermail/dev/2014-May/020880.html
>
> Chrome's console reports:
> Failed to install the extension Installs can only be initiated by one
> of the Chrome Web Store item's verified sites Failed to obtain the
> stream to switch to Installs can only be initiated by one of the
> Chrome Web Store item's verified sites getSwitchStreamFailed
> (anonymous function) Installer.onInstallResponse
>
>
>
>>
>>>
>>> Am 18.07.2014 um 20:11 schrieb Jungle Boogie <jungleboogie0@gmail.com > >:
>>>
>>> Dear Phillip, -------------------------------------------- From:
>>> Phillip Kenney <pkenney@KBHMAINE.ORG> Sent: Fri, 18 Jul 2014
13:19:11 +0000 To:
>>> Jitsi Developers Subject: [jitsi-dev] self hosted Jitsi meet desktop
>>> streamer
>>>>
>>>> Is it possible to use the Jitsi desktop streamer on a self hosted
>>>> Jitsi Meet? I have it set to 'ext' but when I click the button in
>>>> the session, nothing happens.
>>>
>>> This is because you can't just use the jitsi's google chrome
>>> extension, google doesn't allow you to just take the key and use it.
>>> I reported this a few months ago.
>>>
>>>>
>>>> Thanks Phillip Kenney
>>>>
>>>>
>>>
>>> -Jungle
>>>
>>>
>>
>>
>>
>>
>
>
>
> --
> inum: 883510009027723
> sip: jungleboogie@sip2sip.info
> xmpp: jungle-boogie@jit.si
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>