UASF is just any random node throwing a comment into the useragent but still waiting for weeks after 'activation' to actually get an implementation that does anything more than the tier network.
Wrong. You don't even understand it, yet you are attempting to spread "knowledge" to others. 
lol i know your cencentration span is only 2 paragraphs. but please try reading more.
here.. even from the docs of your overlord
http://www.uasf.co/
Quote
A new SegWit UASF deployment would require all nodes to upgrade again which will take considerable time. For this reason, the shortened route to SegWit activation is to require blocks to signal for SegWit activation.
translation. instead of waiting for nodes to upgrade, they just need to signal desire (hence: UASF is just any random node throwing a comment)
Quote
BIP148 was created to avoid having to force most users to upgrade their software. BIP148 is designed to motivate miners to signal for SegWit so that it is activated in a way that even users who are not running BIP148 will get the benefits
again. its about just signalling by any random implementation throwing a comment.the real end user ability to actually move funds to segwit keys and disarm themselves will come later. weeks/month after 'activation'
https://bitcoincore.org/en/segwit_wallet_dev/
Quote
Upgrade Safety
End users MUST NOT be allowed to generate any P2SH-P2WPKH or other segwit addresses before segwit is fully activated on the network. Before activation, using P2SH-P2WPKH or other segwit addresses may lead to permanent fund loss
Similarly, change MUST NOT be sent to a segwit output before activation
Activation of segwit is defined by BIP9. After 15 Nov 2016 and before 15 Nov 2017 UTC, if in a full retarget cycle at least 1916 out of 2016 blocks is signaling readiness, segwit will be activated in the retarget cycle after the next one
If a wallet does not have the ability to follow the BIP9 signal, the upgraded version should not be released to end users until it is activated
https://bitcoincore.org/en/2016/10/27/segwit-upgrade-guide/End users MUST NOT be allowed to generate any P2SH-P2WPKH or other segwit addresses before segwit is fully activated on the network. Before activation, using P2SH-P2WPKH or other segwit addresses may lead to permanent fund loss
Similarly, change MUST NOT be sent to a segwit output before activation
Activation of segwit is defined by BIP9. After 15 Nov 2016 and before 15 Nov 2017 UTC, if in a full retarget cycle at least 1916 out of 2016 blocks is signaling readiness, segwit will be activated in the retarget cycle after the next one
If a wallet does not have the ability to follow the BIP9 signal, the upgraded version should not be released to end users until it is activated
Quote
The wallet provided with Bitcoin Core 0.13.1 will continue to only generate non-segwit P2PKH addresses for receiving payment by default. Later releases are expected to allow users to choose to receive payments to segwit addresses.
Stop subversively promoting BU. If you care about decentralization, you'd be running away from BU not towards it.
by thinking its just core vs BU. shows your lack of understanding of BITCOIN NETWORK
things you dont realise.
many people have a bitcoin-core node but have set the consensus.h much higher than 1mb. they just dont advertise it to avoid DDoS by your clan
many people running bitcoin-core are not actually advocating for segwit.