> I never had any problem to say "nothing to report on my side, working on X like yesterday".
If daily scrum is essentially a status meeting by-any-other-name and nobody is much bothered by what your status is....then maybe you don't need to be giving a status to begin with? Seems like functionally you are more of an observer than a participant and you just throw in a status as a "when in Rome" token.
For the managers in the room, "uhhhh, lots of meetings yesterday" is a fine status to give day after day.
Watch what happens to a programmer who gives an honest status of "uhhhh lots of meetings yesterday, not a lot of progress on X" though. They're inviting attention. There's an added onus on devs that they need to come up with a way to describe what they did the day before (no matter how small) such that non-dev listeners can hear some epsilon of progress was made. Because if it doesn't sound like progress, it sounds like no-progress. And then people who don't understand how any of it works want to start trying to understand. And now you've got two problems.