Everyone will already know about the blocker as soon as it happens. Reasserting it again at a regularly scheduled meeting would be even sillier than regurgitating the commit log. At least there is a slim chance someone hasn't kept up with the commit log. There is no chance of someone not being aware of blockers by the time the standup comes around.

> freshly detected requirements that need a decision

Oh, in that case one should definitely wait 23 hours to bring that to anyone's attention, and for sure an (allegedly) 15 minute meeting is a great place to get requirements

> absences

Uh-huh, go ahead and include births and puppy adoptions, too; I can see that you and the Certified Scrum Master™ have obviously attended the same workshops on Team Health