I think that you need to consider confidentiality here as well. It might be
desirable to have the addressing information concealed. That implies a
mechanism like: http://tools.ietf.org/html/draft-rescorla-stateless-tokens
Now for a variation on a well-worn screed that I had to repeat many
I think that this fails one of the basic criterion that Andreas laid out.
Namely, that it can very easily be mistaken for a product name. I can imagine
taking this to a public announcement.
On 2014-02-20, at 00:57, Romain Testard rtest...@mozilla.com wrote:
Hi all,
Thanks for your input
On 2014-02-21, at 09:58, Romain Testard rtest...@mozilla.com wrote:
Guys, I want to clearly understand, will this prevent URL customisation
(mz.la/romain) as well as easy to remember generated URLs
(mz.la/two_driving_dolphins) ?
I'm not sure we want to do these things but I want to
On 2014-04-17, at 12:36, Randell Jesup rje...@mozilla.com wrote:
No event is fired when this happens which makes it very tricky to react to
in the UI.
Yes; this is a common issue. Right now there's no easy way to deal with it,
as you've seen.
Yes, common. We occasionally angry comments
On 2014-04-18, at 02:59, Jamie McDonnell jamie.mcdonn...@gmail.com wrote:
This is the current error but it seems to have gone quiet - any progress on
this:
https://bugzilla.mozilla.org/show_bug.cgi?id=895971#c24
As noted in the bug, that issue is invalid.
On 2014-04-19, at 00:38, Jamie McDonnell jamie.mcdonn...@gmail.com wrote:
what is the suggested approach for this scenario when a user alt-tabs away
from the browser, or it looses focus while a gUM request is in progress?
You can show an indicator in content that you are awaiting user input
On 2014-04-23, at 04:39, Marco Chen mc...@mozilla.com wrote:
2. Then there are multiple MediaStreamTrack to represent multiple audio/video
tracks in TV stream.
I don’t know if this is a problem here, or whether it’s just a
misunderstanding, but the structure of MediaStream is actually
On 23 April 2014 21:13, Robert O'Callahan rob...@ocallahan.org wrote:
I think it would be a good idea to align AudioTrack/VideoTrack and
MediaStreamTrack by changing their specs.
I think the best thing to do would be to change MediaStreamTrack to fit
AudioTrack/VideoTrack. E.g. we could
On 2014-05-14, at 08:39, Brent Gracey brentgra...@gmail.com wrote:
The setRemoteDescription callback is firing and pc.getRemoteStreams()[0] is
returning a stream, so I think I'll be able to use the work around
Note that there is an open bug regarding the onaddstream event firing too late
in
On 2014-05-27, at 09:16, congnguye...@gmail.com wrote:
Hi, could you please show me an example code of a MediaStream which contains
multiples MediaStreamTrack of multiple cameras. I have been trying to switch
the camera using MediaStream.getVideoTracks(), but there was only one video
track
On 14/07/14 11:22, Adam Roach wrote:
Heh. I guess I stand corrected on that point.
:) We've had this for ages. There might be some gotchas, but I've used
it successfully for some times (but it's failed me for some corner cases).
___
dev-media
Firefox nightly has patches for these constraints in the form described by the
editor’s draft. Though this is an area of the specification that is still in
flux.
http://dev.w3.org/2011/webrtc/editor/getusermedia.html
On 2014-07-21, at 08:54, matteo.brun...@gmail.com wrote:
Hi,
i've
I wouldn't have said that it's strictly bad. Did you plan to have a server
involved at all?
- Original Message -
From: Felix E. Klee felix.k...@inka.de
To: dev-media@lists.mozilla.org
Sent: Wednesday, October 22, 2014 4:43:17 PM
Subject: Re: Working solution for live-streaming to
On 2014-12-03, at 06:24, Balázs Sándor balazs.san...@virtual-call-center.eu
wrote:
Can I change the audio output device?
Currently, no. There is a plan to provide this capability. It was discussed
at the last W3C meeting. I don’t think that it has been prioritised (yet).
The MediaRecorder API enables something like this, though I'm not sure how
playable an in progress recording is.
I'm fairly certain that this will not achieve any performance gains though,
if that is your goal. It might be ok if you are able to tolerate delays,
possibly accumulating delays.
On
On Fri, Jun 19, 2015 at 2:30 AM, haefner.christ...@gmail.com wrote:
I'm trying to implement an identity provider and hitting a roadblock
My very minimalistic implementation (https://pastebin.mozilla.org/8837137)
makes the RTCPeerConnection unuseable, as the createOffer doesn't work
anymore
On Wed, Sep 30, 2015 at 1:15 PM, wrote:
> Where can i find information on how Firefox is selecting the cipher suite to
> be used from the list of cipher suites it receives in DTLS ClientHello ?
The only place that lives now is in the NSS code. You can see the
On Tue, Dec 15, 2015 at 9:14 PM, Balwant Bisht wrote:
> Any idea how to track this issue?
bugzilla.
Please open a bug here:
https://bugzilla.mozilla.org/enter_bug.cgi?component=Audio%2FVideo%3A%20MediaStreamGraph=Core
___
On Wed, Jan 6, 2016 at 9:17 PM, OrdinaryWorld
wrote:
> Is the listing of the video stream as recvonly correct? If so, how do I get
> FF to not receive or send video in the answer?
a=recvonly is correct. Offers and answers are expressed from the
perspective of
On Fri, Mar 18, 2016 at 4:24 AM, Byron Campen wrote:
>> (ice/WARNING) Error parsing attribute: candidate:1316968211 1 UDP
>> 2130706430 91.224.14.66 8001 typ srflx generation 0
>>
>>
>> What's wrong with this ICE candidate ? Firefox wants raddr & rport ?
>
> Yes, raddr
On Fri, Mar 11, 2016 at 7:28 PM, wrote:
> Martin, just to double-check: by 'client' you mean WebRTC client, and not the
> remote node which is sending the DTLS client hello towards FF, right?
Since we were talking DTLS, I mean the DTLS client. That is usually
the
On Fri, Mar 11, 2016 at 10:18 AM, Nils Ohlmeier wrote:
> Have you read this hack post already?
> https://hacks.mozilla.org/2015/02/webrtc-requires-perfect-forward-secrecy-pfs-starting-in-firefox-38/
That posting isn't quite relevant, this is:
> TLS_DHE_***RSA***_...
This is likely a retransmission. NSS has fairly aggressive timers for
retransmission of DTLS messages. If your ServerHello doesn't arrive
quickly, then you will see a second ClientHello after 50ms and a third
after another 100ms. As long as the handshake completes successfully,
I wouldn't worry
On Fri, Jul 29, 2016 at 5:47 AM, wrote:
> It was causing problems in our implementation when we received the second
> client key exchange sequence after the handshake was already completed. I
> fixed it by filtering out the retransmitted messages before they get
>
On Fri, Feb 3, 2017 at 2:51 AM, <ushunmu...@gmail.com> wrote:
> @Martin Thomson Thank you for the info. Do you know which version of
> Firefox this fix will land on?
Firefox 53. https://bugzilla.mozilla.org/show_bug.cgi?id=1317947
_
On Thu, Feb 2, 2017 at 11:37 AM, wrote:
> BTW, it seems to me that Firefox should be using a more widely used ECDH
> named curve, such as secp256r1, when the Client Hello does not list the
> supported named curves. This would make Firefox more compatible with older
>
No good info on the bug, which seems plausible. I do have an
observation though:
You can't rely on DTLS alerts arriving, since they are not
retransmitted. You should use signaling for session termination.
On Mon, Sep 19, 2016 at 6:44 PM, Lorenzo Miniero wrote:
> Hi,
>
>
Support for RTCP mux is now mandatory. Nils, do you have any plans
for trimming down the extra gathering? I appreciate that it might be
a low priority item.
On Fri, Sep 22, 2017 at 11:05 AM, Nils Ohlmeier wrote:
> Hi Prerak,
>
>> On Sep 21, 2017, at 02:27, prerak jain
That checkbox is not useless, to a user who doesn't want to be
assaulted by dialog boxes from malicious or annoying sites (assuming
they still have cause to visit those sites). I regularly have to fend
off advances that ask for notifications or geolocation permission on
sites that I have no
SSLKEYLOGFILE integration with SRTP might be a better long term solution
here.
On Sat, 2 Mar. 2019, 07:23 Nils Ohlmeier, wrote:
> Hi Alexander,
>
> > On 1Mar, 2019, at 09:00, Alexander Abagian wrote:
> > I know that Firefox does not have such a useful thing as
> -disable-webrtc-encryption.
Lossless video coding isn't really a thing on the internet. There are
lossless modes in some encoders (x264 has one that I'm aware of), but they
tend to inflate inputs rather than compress them. There are systems used
in video production that maintain all the source bits, but they use insane
31 matches
Mail list logo