Correct! And that is
real Bitcoin, not this Core scam altcoin shit. Again I have no objection to Core making a fork of Bitcoin or even a soft fork as they have done, but the scam part is they do not disclose the true security risks and just herd the n00bs into default wallet settings wherein the n00bs think they are hodling real Bitcoin but they are instead hodling a soft fork altcoin that can in the future be hardforked off of the real Bitcoin.[/size]
I read through the rest of your post, and you are not really adding anything new.. just continued repetition, speculation and mischaracterization...including your characterization of the current bitcoin as an alt coin... pure nonsense. Our current bitcoin is operating as a product of consensus... so it is not an alt coin as you nonsensically assert.
i look at it this way: i am a long time holder. i have an amount of btc i wish to protect. there is a very small, but non zero, chance i could lose btc stored in a segwit address. and all i have to do to mitigate that risk is store my long term btc in a legacy address. well thats a no brainer to me. after all my long term coins rarely move and segwit has no real advantage for long term holders.
i do have segwit coins, those are the ones i move back and forth to exchanges, use to buy stuff etc, IOW the day to day coins. the bulk of my coins are legacy. i get the best of both worlds: cheap fees on the daily driver segwit coins, better security for the legacy hodl coins. so whats the problem?
EDIT: here is an interesting read.. its what happened to a bunch of segwit coins on a chain that does not support segwit coins. happened on the bcash side but does illustrate what can happen (well, kinda, i think. maybe its not).
https://np.reddit.com/r/Bitcoin/comments/7eixcu/recovering_bch_sent_to_segwit_addresses/EDIT 2: i don not do bcash, i sold that crap off.
There seems to be nothing wrong with what you are doing, but there still could be a bit of an issue to not support segwit for long term storage, merely based on very low odds of an attack (as you mentioned). I already mentioned to others that trolls seem to be striving to get you to NOT use segwit.. and you might play into their hands, perhaps?
Regarding sending bcash to a bitcoin segwit address.
1) Bcash does not use segwit and your link seems to describe some possible problems with bcash, not bitcoin, 2) bcash forked before segwit got implemented and activated into bitcoin 3) bcash continued to use the same addresses for preforked coins.. and then used addresses that look like bitcoin legacy addresses (which could cause confusion), but I don't see what the bcash problem is because they should not be able to use segwit addresses (since they did not implement segwit)... but yeah, there could be an issue with bcash getting sent to any bitcoin address, whether legacy address or a segwit address.