MarcusPope

A WordPress plugin that converts all URL formats to root-relative URLs to enable seamless transitioning between staging/production host environments and debugging/testing from mobile devices, without the use of hackish tactics like textual find-replace strategies or risky hosts/NAT spoofing strategies.
With Root Relative URLs you can browse your development site from http://localhost/ or http://127.0.0.1/ or from a named network resource like http://mycomputername/ without worrying about links redirecting you back to your site’s URL.
This plugin also modifies the tinyMCE hooks so links and media embedded with built-in tools will only insert URLs from the first forward slash after the domain (i.e. the root of your site.) This means when you push content changes to a staging or production environment they are guaranteed to reference the correct target instead of accidentally referencing a production resource in development or, worse-yet, a development-exclusive resource in production.
It supports path-based MU Installations, but does not support domain-based MU sites due to architectural deficiencies in the WordPress core.
Version 1.5 fixes an infinite redirect problem that is a result of a core bug in WordPress. If you have problems with the <!–more–> tag or permalinks for custom post types, please read the FAQ or new Install Steps for support.
Version 2.2 allows for adding certain URL’s or partial URL’s to a blacklist, meaning I won’t use root relative urls, but dynamic absolute URLs instead for displaying content. This will fix problems with 3rd party plugins, and can be configured on the General Settings page.
<h3>Arbitrary section</h3>

Root Relative URLs

Converts all URLs to root-relative URLs for hosting the same site on multiple IPs, easier production migration and better mobile device testing.

Konstantin Obenland

This plugin replaces the author slug with a sanitized version of the user’s display name.
This plugin will not prevent hackers from finding out your login name but the login name won’t be visible 
in the author archive’s URL, which works towards your friendly URLs with using your display name.
DO NOT use this on a site with more than 1000 registered users, as updating all of their nicenames at once might break your site.

WP Author Slug

Easy way to add some obscurity to login guessing.

But please update as it's over 2 years now.

Excellent

This plugin would probably work OK if you have a small number of users (e.g. if your site doesn't allow public login). But if you have a large number of users (e.g. if you are running ecommerce or allow users to register for other reasons), this plugin will probably take down your site.

The reason is that there are hooks that run when you activate or delete the plugin. It runs database fetch and update queries on every user in your database, all in-line on the request (rather than background via a cron). So if you have a thousand or more users it attempts to do a thousand or more database writes when you click Activate or Delete from the plugins list. This will likely grind your website to a halt. 

It would be better/useable if you could either choose to only apply these scripts to specific user types (e.g. Author) or if you could run the update in batches in the background.

Don't use if you have a large user database

Add a layer of security and prevent your login name from being shown in the author archive's URL.

Root Relative URLs vs WP Author Slug