how are people able to freeze your time?

What you're describing is a disconnect from the live server process. Your opponents can't impact your connection.
Some things you can do to minimize connection issues.
https://support.chess.com/en/articles/8584209-how-do-i-fix-my-disconnect-lag-issues
https://support.chess.com/en/articles/8652402-how-can-i-optimize-my-online-chess-performance

There's no such animal as "giga internet". Perhaps you mean you have 1 gig of bandwidth. This does not guarantee your connection has 100% uptime in any way. Just admit you have no idea what you are talking about.

This has been an exploit for years. Chess.com will never acknowledge that it is in fact an exploit but try to blame it on user connection.

This has been an exploit for years. Chess.com will never acknowledge that it is in fact an exploit but try to blame it on user connection.
...and another one. You should play each other, problem solved.

Imagine someone derailing a post intentionally so it's gets locked. Typical, seeing the stance this site has taking on political issues in the past. Whatever it takes to silence the few, so the multitude continues to prosper.

can I guess you were playing some game like 3+2, 5+5, 10+5?
The only time lag felt really unfair on this site was in these time formats, where opponent's clock may run to 00.00 then suddenly again he has 7 seconds your like how?
( maybe because this site is slow sometimes, and either or both parties may have connection issues and maybe the site tries to compensate for lag or some bug, and quick time formats with increment are especailly prone to having harsh freezes etc in time scrambles...?).
it can really destroy games which are relatively fast but with incriment and it's somehow always in the scrambles.. I don't play those on chess.com because it happens...
Somehow i've never had issues on this site at all with +0 time formats, clock always seems perfect... or with the longer ones like 15+10 or 30+0.

...and another one.
Bah Bah, Sheep. You ought not be so gullible.
Gullible would be believing that you are being hacked when your internet service provider fails you.

There's a lot of equipment between you and the site's servers. Problems on your device, local network, ISP, between you and the site, and including the site could cause problems. Problems in the last part are going to cause issues with a lot of members at the same time.
I suggested those articles as a way to minimize issues on your end. If there's an issue between you and the site, there's not much that can be done.

This has been an exploit for years. Chess.com will never acknowledge that it is in fact an exploit but try to blame it on user connection.
It not an exploit but the fact that the Internet is a combination of a lot of different pieces of equipment and software, any of which can cause connection problems.
There simply isn't an exploit.
No shame in admitting your app may have flaws, dude.

No shame in admitting your app may have flaws, dude.
You think the back end for live play is JavaScript? I would have guessed Java with JDBC based on the timeframe the core architecture was developed and some familiarities in how the backend seems to work indirectly. In any case, do you actually have a real background in large scale client server architecture, or are you just some script kiddie?
It would take the worst coders around to allow UI Mickey Mouse stuff like not confirming a transaction to affect clocks on the back end, so unless you have some kind of evidence...

> how are people able to freeze your time?
They use pure HTML to hack your device over Internet adding a float top-order DIV-block with steady time right over your clock ticking down...

You're a special snowflake if you consider my posts in this thread "bullying".
I will repeat my perfectly acceptable question...do you have any evidence whatsoever?

> how are people able to freeze your time?
They use pure HTML to hack your device over Internet adding a float top-order DIV-block with steady time right over your clock ticking down...
Go ahead and explain how your opponent identifies your device when there's no direct connection (the server is the sole clock intermediary) and then tell us how they "hack your device with HTML" to hide your clock (which does not match the behavior the OP brought up, by the way) when they are not the ones passing anything to your browser.