3 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Based on the reasons given, it sounds like a reasonable step to remove WordPress as a standard selection option (although with a less than optimal short notice!).

However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "My Favorite OpenID Provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the login page?What OpenID providers should we feature on the login page? much less of an issue because it would more or less only affect people using OpenID the very first time. This will benefit all non-default selection OpenID users, not just WordPress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favorite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}

Based on the reasons given, it sounds like a reasonable step to remove WordPress as a standard selection option (although with a less than optimal short notice!).

However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "My Favorite OpenID Provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the login page? much less of an issue because it would more or less only affect people using OpenID the very first time. This will benefit all non-default selection OpenID users, not just WordPress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favorite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}

Based on the reasons given, it sounds like a reasonable step to remove WordPress as a standard selection option (although with a less than optimal short notice!).

However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "My Favorite OpenID Provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the login page? much less of an issue because it would more or less only affect people using OpenID the very first time. This will benefit all non-default selection OpenID users, not just WordPress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favorite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}
2 fixed grammar
source | link

Based on the reasons given, it sounds like a reasonable step to remove wordpressWordPress as a standard selection option (although with a less than optimal short notice!).

However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "my favourite openid provider""My Favorite OpenID Provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the /loginlogin page? much less of an issue because it would more or less only would affect people using openidOpenID the very first time. This will benefit all non-default-selection openid selection OpenID users, not just wordpressWordPress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favouritefavorite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}

Based on the reasons given it sounds like a reasonable step to remove wordpress as a standard selection option (although with a less than optimal short notice!).

However having to type in something manually each time will be a pain so I would suggest that you replace the button with a "my favourite openid provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the /login page? much less of an issue because it more or less only would affect people using openid the very first time. This will benefit all non-default-selection openid users, not just wordpress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favourite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}

Based on the reasons given, it sounds like a reasonable step to remove WordPress as a standard selection option (although with a less than optimal short notice!).

However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "My Favorite OpenID Provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the login page? much less of an issue because it would more or less only affect people using OpenID the very first time. This will benefit all non-default selection OpenID users, not just WordPress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favorite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}
1
source | link

Based on the reasons given it sounds like a reasonable step to remove wordpress as a standard selection option (although with a less than optimal short notice!).

However having to type in something manually each time will be a pain so I would suggest that you replace the button with a "my favourite openid provider" button, which then fills in a user configurable setting.

This will make the issue of What OpenID providers should we feature on the /login page? much less of an issue because it more or less only would affect people using openid the very first time. This will benefit all non-default-selection openid users, not just wordpress.

Logic something like the following:

if (login_method == openid && !user_settings.contains(favourite_openid_provider)
{
   answer = ask("Do you want to save " + sanitize(url) + " as your favourite...")
   if (answer == yes)
   {
       user_settings.save(favourite_openid_provider, url)
   }
}