Quoting Enrico Zini (2016-04-10 11:20:51)
> On Sun, Apr 10, 2016 at 11:20:07AM +0200, Jonas Smedegaard wrote:
>>> If WebID has a workable plan for what to do after
>>> disappears, I haven't seen it. If you have, please send me precise
>>> details[1]: I haven't seen any in
>>> https://www.w3.org
On Sun, Apr 10, 2016 at 11:20:07AM +0200, Jonas Smedegaard wrote:
> > If WebID has a workable plan for what to do after disappears,
> > I haven't seen it. If you have, please send me precise details[1]: I
> > haven't seen any in https://www.w3.org/mid/20150730174424.GA7779@c
>
> I am unaware o
Quoting Enrico Zini (2016-04-10 10:44:02)
> On Sat, Apr 09, 2016 at 11:25:34PM +0200, Jonas Smedegaard wrote:
>>> I have seen no sign that Chrome or Firefox developers have much
>>> interest in supporting WebID either, and given how I've seen one of
>>> the WebID people argue their case[1] with t
On Sat, Apr 09, 2016 at 11:25:34PM +0200, Jonas Smedegaard wrote:
> > I have seen no sign that Chrome or Firefox developers have much
> > interest in supporting WebID either, and given how I've seen one of
> > the WebID people argue their case[1] with the Chrome and Firefox
> > developers, the
Quoting Enrico Zini (2016-04-09 22:11:54)
> On Fri, Apr 08, 2016 at 09:06:33PM +0200, Jonas Smedegaard wrote:
>>> Which is fine, I guess, for someone living in an ecosystem where
>>> «authentication via "log in with your Google or Facebook account"»
>>> is all your users would ever need.
>>>
>>>
On Fri, Apr 08, 2016 at 09:06:33PM +0200, Jonas Smedegaard wrote:
> > Which is fine, I guess, for someone living in an ecosystem where
> > «authentication via "log in with your Google or Facebook account"» is
> > all your users would ever need.
> >
> > I guess I should stop writing here, as at th
Quoting Jonas Smedegaard (2016-04-08 21:06:33)
> Quoting Enrico Zini (2016-04-08 11:22:53)
>> So, chrome just went and removed support for it.
[...]
> The W3C public-rww list has some possibly interesting references
> related to this issue:
> https://www.w3.org/mid/https://www.w3.org/mid/20150730
Quoting Enrico Zini (2016-04-08 11:22:53)
> On Fri, Apr 08, 2016 at 10:14:15AM +0200, Enrico Zini wrote:
>
> > The error is reproducible while running a checkout of debsso locally on
> > a ./manage.py runserver. See README for dependencies, and
> > django-oauth-toolkit and django-cors-headers are
On Fri, Apr 08, 2016 at 11:22:53AM +0200, Enrico Zini wrote:
> So, chrome just went and removed support for it. It now just silently
> fails. It can be reenabled somehow, but then the key is not pushed into
> the browser keystore, but only downloaded. No viable alternative
> suggested to what they
On Fri, Apr 08, 2016 at 10:14:15AM +0200, Enrico Zini wrote:
> The error is reproducible while running a checkout of debsso locally on
> a ./manage.py runserver. See README for dependencies, and
> django-oauth-toolkit and django-cors-headers are now at least in Debian
> testing.
>
> I ran it loca
On Thu, Apr 07, 2016 at 08:05:17PM +0200, Enrico Zini wrote:
> some people have reported getting a "/usr/bin/openssl failed" error when
> enrolling their browser on sso.debian.org, and I am not able to deal
> with it. Help?
The error is reproducible while running a checkout of debsso locally on
a
11 matches
Mail list logo
