SSL headache for my Indieweb logins

Adding an SSL to my domain has now presented me with a headache for my #indieweb logins.

One of the many great things about the Indieweb is that I can use my domain URL to log into and use different services. But now changing from http: to https: those services see that as a new URL.

Disabling the redirect in the .htaccess file only works for the root. Once I try to authenticate with the WordPress element we’re right back to using the secure URL.

Most of this problem is of my own creation. I don’t run WordPress for my whole site. Only the /blog part is WP as I wanted to retain a POSH homepage and be able to play around on the non-blog parts.

This means the URL I have to use is https://davidjohnmead.com/blog. Not great as most things are geared around the root.

I think I’m just going to have to discard my old URL login and start anew with the secure one.

Syndicated to: 

We’ll still have IE6

Rumour that Microsoft is ditching their Edge browser and building one based on Chrome. https://www.windowscentral.com/microsoft-building-chromium-powered-web-browser-windows-10.

Syndicated to: 

Really? I guess it’s what we get used to, as I’m the opposite. Been running Android for years and find my dips into iOS infuriating.

in reply to:

Syndicated to: 

Pintrest?

It’s been around 6 years and I still don’t “get” @Pinterest. Every so often I log in and it just seems a directionless mess that doesn’t click for me.

Syndicated to: 

Oh please. C’mon @code_punkt…

Oh please. C’mon @code_punkt. many companies don’t give…time and resources they’d need to learn is a weak excuse, up there with dogs eating homework. If you want to be a web developer it’s up to you to learn. If that’s on your own time then so be it. It’ll make you a better contributor and enable you to move from a junior position, or to a company that values you more.

As for your other comment, you’re right – You do only need a solution when there is a problem, but as a user if I have a problem I want the solution there and then. Not 3 sprints later when you’ve justified working on it. Part of developing anything people use is being proactive. Think about all the potential problems anyone could encounter and build in solutions. Again, it’s up to the individual.

I am by no means infallible, and I’m not saying I’m better than anyone else because I do this. I don’t always “win” these discussions internally either, but at least I fight for them.

in reply to:
https://mobile.twitter.com/code_punkt/status/1066414789189079040

Syndicated to: 

Web developers need to educate themselves

It’s up to “developers” to educate themselves. If they won’t, that’s shameful! I seem to bump into this more and more. If “sending work back” and pushing them to find a solution instead of a quick compromise is shaming, then so be it.

There’s never been a larger corpus of knowledge about web development than what’s out there today. If you can’t find a plugin/mixin/repo on the first SERP then the perception seems to be that it’s extra work and should be questioned wether we need it all – This is ridiculous!

I just don’t get the thinking behind it being ok not to know basic HTML, but focus on things like node.js and Bootstrap out of the gate.

Developing anything for the web must include accessibility, network resilience, responsiveness, and testing for all them as well. If you’re not thinking about all of that (and doing it) then start. It’s your responsibility.

in reply to:
https://mobile.twitter.com/code_punkt/status/1066251985735831552

Syndicated to: 

Cleaning up podcasts

There’s tiles in PocketCast that don’t drop any sounds anymore. Time to clean house a little, and remove these:

Syndicated to: