I'm tired of arguing. Make a patch that keeps our functionality that allows what you want, or....set it up like we say.
I'm not arguing. I hear you and substantially agree with what you're saying. 'These are our design goals.' 'It works for the intent for which it was designed.' 'All contributions welcome that enhance. (And not break.)'
But, I'll add ... I'm tired of the attitude - in some aspects it's overwhelming. IF YOU MUST BE THE GATEWAY - BE THE GATEWAY. WITH ALL THE DYNAMIC SPECIFICATIONS (especially due to convergence) THAT THAT IMPLIES. OTHERWISE, STOP BEING THE GATEWAY. This is the crux of the noise - be a gateway, or don't be a gateway - pick one. As a design direction.
What you're really getting at, but is often overshadowed - hey, people, we've come this far. It's a good thing. Yes, we all recognize there's lots to do yet. We'll get there, some day, maybe. This stuff doesn't just spring in to being instantaneously.
And, also overshadowed - hey people, it's free. It's what it is. We'd all like to make it 'better'. But our hours are already tapped out. If you (the user) want it to be better, then we need you to contribute some of your own hours to help us make it better. It's 'free' only in $, it is what it is. If you want it to be different, and the community agrees with those differences, it's up to you (the user) to contribute them. If LinuxMCE works for you and satisfies all of your requirements, we're really happy for you, and quite gratified. But if it doesn't, well, only you can make it better.
Mr. User, please reference: http://wiki.linuxmce.com/index.php/LinuxMCE_wiki:Site_support
Now I get your perspective - forest and trees. And your fatigue - just how many times can you say the same thing over and over without getting at least a little testy. Particularly as they are repeated distractions from actually moving forward.
There's a basic constraint: (gateway) all or nothing. But the nature of the environment is most of the time you must integrate with, or seamlessly transition from, the current environment. The constraint means two states: 'broken', or 'working'. Broken = bad. Working takes some non-zero time to accomplish. And that's the rub. Unfortunately. But that's the way it is. Sorry 'bout that. So, the irritation is understandable, on every side. People want drop in, fire and forget, functionality. Unrealistically - that doesn't happen, for these type of applications, even in the pay world.
No doubt, on the list of things to do, is the be a gateway or not issue(s).
Let me iterate here ... thank you for being here.