not working in Chrome about starter-kit

[michielbdejong]

it's because of the ssl cert. so let's forget about ssl! also has the advantage which @skddc mentioned, that people don't have to click through cert warnings in Firefox. although it will still require running as root to open port 80, and it requires us to keep http support in the library, which violates the first sentence of https://tools.ietf.org/html/rfc7033. so by that time we might as well define that we'll use port 8123 instead of port 80, because it will not be proper webfinger anymore anyway, it will be just a hack in our library to make the dev-kit work.

anyway, let's start with port 80 because it's what the library supports now

[michielbdejong]

hm, https://github.com/remotestorage/dev-kit/tree/f948e56e3bece5406a760bc654f63241d77b9d43 fixes this but breaks it in FF again for some reason. investigating...

[raucao]

by that time we might as well define that we'll use port 8123 instead of port 80

I thought the port 80 was so that you can have clean user addresses in the example.

[michielbdejong]

there is not even a way to specify port numbers in user addresses, it always needs to be 443. in previous versions of WebFinger you could choose 443 or 80, that's why our lib still supports port 80.

[raucao]

So might not just as well use 8123, or am I missing something?

[raucao]

that's why our lib still supports port 80

It's not a "still", it's "yet again". We actually re-introduced it to circumvent an ugly development situation, that's even bugging us core people, not only newbies.

[michielbdejong]

i mean remotestorage.js will support port 80 for another six months, because remotestorage-00 still allowed it. let's do it on port 80 for now, seems to be the fastest way forward at this point.