openletter

You, sir, are a liar.

sounds good

It is of some concern that you don’t seem to know how your own plugin works:

Password Policies

Length How long must passwords be? Must be >= 10. Default: 10.

Complexity Exemption How long must passwords be to be exempt from the complexity requirements? Must be >= 20. Default: 20.

The >= means it will not accept smaller numbers. Putting a smaller number in the fields of the above two settings resets back to the >= number gives the following warning:

‘Length’ must be >= ’10’, so we used the default value instead.
‘Complexity Exemption’ must be >= ’20’, so we used the default value instead.

It is of some concern that you don’t seem to know how your own plugin works:

Password Policies

Length How long must passwords be? Must be >= 10. Default: 10.

Complexity Exemption How long must passwords be to be exempt from the complexity requirements? Must be >= 20. Default: 20.

The >= means it will not accept smaller numbers. Putting a smaller number in the fields of the above two settings resets back to the >= number gives the following warning:

‘Length’ must be >= ’10’, so we used the default value instead.
‘Complexity Exemption’ must be >= ’20’, so we used the default value instead.

Thank you! That’s a great plugin and saves me the time of checking for updates or use an SVN client. I chose not to activate the plugin because it requires me to run WordPress Stats on my page, and I’m happy with Piwik. However, even deactivated I can just copy the Minileven theme to my themes folder and it works just fine, and I’ll still receive notifications of changes to deactivated plugins, IIRC.

I use the plugin called Device Theme Switcher.

I meant to include what I did to replace WordPress Mobile Pack:

I use the plugin Device Theme switcher. I grab the WordPress Mobile theme from the WordPress Mobile Pack. You can then use this plugin to automatically select which theme is served to different devices.

Unfortunately, I think this plugin is dead. It hasn’t been updated in almost a year, and the developers haven’t contributed to anything in nearly as long. It’s a shame, because this is the best mobile theme manager I’ve found.

“There are 57 signals that Google looks at.”

https://panopticlick.eff.org/

Google stores information about everyone’s search habits and Internet usage for eternity. I do not submit to this policy, especially on behalf of anyone who visits my site, and I feel it is unethical for WordPress to install these things without first asking permission, or at the very least, informing users.

Again, this is a default setting. If this were an option, as incorporation of Google Gears was for admin panel back in the day, that would be fine, but it is not presented as an option.

Certainly I can figure out how to use a different font, but, again, I believe it is unethical and disingenuous to include outside services, especially considering that most users have no idea how to even identify these sorts of things.

There are additional issues with Google services. They can go away at any time and without warning, a policy Google has practiced many times in the past. Google may change its privacy policies at any time and without warning. Google gets hacked and user info leaked. Google even gets hacked and its users subsequently hacked as a result.

Additionally, some feel it the Google is an evil corporation, part of a leviathan of corporations working largely against the interests of small parties. Forcing these users to use a product without informing them, clearly, unethical.

This greatly changed my opinion of WordPress.

A default theme or setup should not be using outside services, most especially closed source, private services, and in particular not anything from Google.

I am still quite unhappy to be calling any outside site’s service as part of the default setup in WordPress.

Are you sure? Have you looked at line 139 of /wp-content/themes/twentytwelve/functions.php?

wp_enqueue_style( 'twentytwelve-fonts', add_query_arg( $query_args, "$protocol://fonts.googleapis.com/css" ), array(), null );

That’s all I’ve found so far.

NoScript in Firefox reports blocking objects from googleusercontent.

Thanks, allyngibson, that is very helpful. I did a variation on what you suggested and used the Device Theme Switcher instead of messing with the php files. This way users on older devices can still use the page by my selecting a more basic theme for them to use.

I tried disabling any other plugin that affected comments and it still didn’t work.