I'm all for /local being the default setting. Obviously, it really would cut down on unnecessary system-comms spam, and seeing as most of the players I know of use local-comms about 90% of the time, it's easier for a lot of us.
Would we miss out on interesting RP? Possibly. But differentiating between system comms and local comms is something that a good role-player ought to know how to do.
I don't mean that in a simple "if you don't know server commands you're not a good RPer" kind of way. I mean that a good role-player knows which channel to use depending on what kind of role he/she is playing.
Some roles do better on system comms, like the kind of advertisers who like to let everyone know that they're in system and providing a service, or if they're spreading some sort of propaganda or something.
For just about everything else, a good role-player knows that local comms are more suited for private affairs between two or more ships within a certain radius. Or pirates, who want to keep a low profile and don't want to broadcast their activities to everyone in the system.
Both types of comms have their place, and when someone knows how to create an interesting role-play atmosphere, they'll know which one to use.
So a /local default gets a thumbs up from me.
Also, I didn't see it mentioned in here, but is that /shields command that was put to use in Dublin today a new feature? Or is that something that's been here a while and I just never knew about it?
And if the mining fields don't replenish after server restarts... then is it just based on how long they go untapped or something? Although I understand if you don't care to shed any more light on this than you already have. I'm just curious now.