Skip to main content

Google did it again - Not found error in Windows Live Writer and Open Live Writer

In the summer of 2015, Google turned off there old authentication system and made the switch to OAuth 2.0. Although better security can only be encouraged in this case it had the unfortunate side effect to break Windows Live Writer, the blog writer I used for years. Luckily, thanks to the effort of Scott Hanselman, Google was kind enough to re-enable the old security mechanism for a little bit longer. In the meanwhile Scott started the effort to make Windows Live Writer Open Source.
Last week this story came to an end with the announcement of Open Live Writer, an open source fork of Windows Live Writer. Although some features are still missing, this is great news as it will give Windows Open Live Writer a new future...



Inside the announcement, the support for OAuth 2.0 was mentioned as to be added 'VERY SOON':

ADDING VERY SOON: Google runs the excellent Blogger blog service. We've worked with the Blogger Team within Google on this project, and they've been kind enough to keep an older authentication endpoint running for many months while we work on Open Live Writer. Soon, Google and Blogger will finally shut down this older authentication system. Blogger will use the more modern OAuth 2 and Open Live Writer will be updated to support OAuth 2. Windows Live Writer will never support this new OAuth 2 authentication system, so if you use Blogger, you'll need to use Open Live Writer.
Unfortunately the Blogger guys didn't read the announcement very well I think, as they disabled the old authentication endpoint immediatelly :-( So if you try to connect to Blogger using either Windows Live Writer or Open Live Writer, you'll get a 'Not Found' exception.
I hope a fix will be available soon as typing in the online editor ain't fun!

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more