scripting
feedBase needs HTTPS support
Browsers are beginning to show unsecured sites as “insecure” rather than showing secure sites as “secure”. This is going to put some users off from using feedBase.
Google is also pushing unsecured sites down lower in search results. This will make it harder to find feedBase.
HTTPS by default looks like it is the future. feedBase should support it.
I have strong feelings about that -- but I'm not saying no.
http://this.how/googleAndHttp
On Thu, Apr 4, 2019 at 12:35 PM Maurice Parker [email protected] wrote:
Browsers are beginning to show unsecured sites as “insecure” rather than showing secure sites as “secure”. This is going to put some users off from using feedBase.
Google is also pushing unsecured sites down lower in search results. This will make it harder to find feedBase.
HTTPS by default looks like it is the future. feedBase should support it.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/scripting/feedBase/issues/45, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O7z-NPdUZd2b8tXCmPH7kSlkImehks5vdinRgaJpZM4cdOwz .
You make some good points there that I had not thought about. I hadn't realized Google was being so pushy about sites using HTTP.
Anyway, I was trying to juggle too many things today and bungled this enhancement request. I only managed to get to issues that I thought might convince you and forgot talk about why I wanted HTTPS. My apologies.
I would like to enable users to directly upload OPML files from Feed Compass to feedBase. To do that I would have to authenticate the user against Twitter and pass their credentials to feedBase. So I need to pass the credentials over HTTPS as to not leak them.
There may be other ways to do that. I want to give it some thought.
On Thu, Apr 4, 2019 at 4:11 PM Maurice Parker [email protected] wrote:
You make some good points there that I had not thought about. I hadn't realized Google was being so pushy about sites using HTTP.
Anyway, I was trying to juggle too many things today and bungled this enhancement request. I only managed to get to issues that I thought might convince you and forgot talk about why I wanted HTTPS. My apologies.
I would like to enable users to directly upload OPML files from Feed Compass to feedBase. To do that I would have to authenticate the user against Twitter and pass their credentials to feedBase. So I need to pass the credentials over HTTPS as to not leak them.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/scripting/feedBase/issues/45#issuecomment-480045662, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O-594MhJLGl2QqDEiti6x7Zpl137ks5vdlxvgaJpZM4cdOwz .