Instead of just bitching and moaning somebody senior on the team needs to aggressively push back with productive feedback and compromise. You can't just say stop all of the process. You are invalidating the Scrum Master/TPM's existent and will just meet fierce resistance.
Ask them to let you run the the standup the way you want to run it one day as an experiment. Ask them what metrics and reports are being shared so you understand why this is a hill they will die on. Ask them to participate as peers during the ceremonies so they understand where you're coming from.
I've been pushing my org to open channel discussions using the thread feature and periodically will hear somebody say they found what they needed in an previous discussion. This is the way.
I empathize deeply with you. I have been dealing with a system of "infinite configurability" for the last couple years and it's playing out the same way. The best I've been able to do is slowly codify the most problematic corners and put guard rails as many places as possible.
Sometimes I want to put my hands up in defeat and leave but there is also a satisfaction and growth from simplifying the Rube Goldberg machine.
We started noticing issues around 10:03AM PT and are seeing a red "Internal server error" banner at the top of API Gateway dashboard. This is causing our API Gateway integrations to fail.
Adventure games are thriving. They may not be Twitch and YouTube headliners but there's still a huge audience.
A friend of mine is making a point & click adventure with Unity and has a playable demo on steam[1]. Unity and Steam (and their competitors) have truly made it possible for individuals and small teams to chase an idea to completion.
It's hard to have a charitable take on a huge majority of the cryptocurrency space when the web is drowning in all of the greedy bad actors that use the ideologies listed in this article as cover to push the grifts that inevitability harm my less technical friends and family.