First: The purpose of the tariffs is to force on-shoring, create volatility, and push investors away from the stock market into the bond market. This will both give the fed room and pressure them to lower interest rates.
Well heres the kicker: Signalled by China's move to a SWIFT alternative, they now have less of a need for bitcoin. Who owns the majority of miners? Chinese companies, basically the chinese government.
I expect in the next few days they will realize they can squeeze the miners, or shut them down.
How does this cause them to blow up the tariffs situation right in the face of America?
When the hash rate lowers, because of fewer miners, a sufficiently large dip in bitcoin will occur, triggering a counter-surge in purchasing. The sentiment will be that because it fell so fast, it obviously has to come back up, or so the belief goes for many investors.
Right when the U.S. is trying to push all the dollars exiting the stock market into lower yield bonds that have less volatility.
A boatload of miners come online in the u.s. and money, which is already heavily institutionally invested in bitcoin, goes to btc instead of bonds, trying to make up their margin calls from the falling stock market.
Tariffs go boom, and the 'black monday' that wasn't, becomes real this following monday as the surge into bonds becomes a mirage that evaporates in the face of a wave of onshored dollars where we can't refinance our debt. Cue real hyperinflation.
And that 38 percent of ASEAN and 7 middle eastern nations that turned to the Chinese SWIFT alternative becomes 50-70% percent in a matter of a month.
Ding dong the dollars dead.
My prediction is this is exactly what they try to pull. It's exactly what I would do in their shoes.
I've hard coded in to auto block any IP with fragment packets, or over packet size. I sterilize every ip so header attacks and others aren't possible. Yes, the guy is correct, you can use fragment packets to trick firewalls to letting you pass, I'm not sure if it goes to the UDP layer, I think it would just pass as a corrupt ip that's allowed to transfer data.
When it comes to updaters for software you are correct, and this has proven troublesome because the isp and location data don't point to the specific service over half of the time. Like steam is all valve isp, so it labels it as such. But a generic amazon isp from nevada becomes the tricky ones. I've thought about how I'm going to solve this, because you do want those updaters to work, but only when you want them to, and for only the period they're updating.
My solution to this has been crude, where I manually label them after starting that updater and then I can see which ip starts transferring packets. I tried attaching the ips to the software using them and that messed up a bunch of stuff in my code, but is definitely possible and will eventually be how it functions. That way you could have a profile for each piece of software if you wanted to that blocks everything but that software and it's servers from your network. You'd just have to build the profiles.
I also have a "nuke" mode that when you click the button it keeps whatever you have white listed and then automatically blocks everything else connecting to your port.
I use that on a fresh system you boot it up when nothing is running and turn the nuke button on, it auto blocks all the shit you don't want, and then you can save that as a default profile. Turn the nuke button off and you got a base setting.
registered_bot 0 points 3 weeks ago
I've hard coded in to auto block any IP with fragment packets, or over packet size. I sterilize every ip so header attacks and others aren't possible. Yes, the guy is correct, you can use fragment packets to trick firewalls to letting you pass, I'm not sure if it goes to the UDP layer, I think it would just pass as a corrupt ip that's allowed to transfer data.
When it comes to updaters for software you are correct, and this has proven troublesome because the isp and location data don't point to the specific service over half of the time. Like steam is all valve isp, so it labels it as such. But a generic amazon isp from nevada becomes the tricky ones. I've thought about how I'm going to solve this, because you do want those updaters to work, but only when you want them to, and for only the period they're updating.
My solution to this has been crude, where I manually label them after starting that updater and then I can see which ip starts transferring packets. I tried attaching the ips to the software using them and that messed up a bunch of stuff in my code, but is definitely possible and will eventually be how it functions. That way you could have a profile for each piece of software if you wanted to that blocks everything but that software and it's servers from your network. You'd just have to build the profiles.
I also have a "nuke" mode that when you click the button it keeps whatever you have white listed and then automatically blocks everything else connecting to your port.
I use that on a fresh system you boot it up when nothing is running and turn the nuke button on, it auto blocks all the shit you don't want, and then you can save that as a default profile. Turn the nuke button off and you got a base setting.