In the forum post editor you can format code as code what makes it easy to read for people want to help:
Example:
I install a fair bit via Flatpak. Bazaar is a great flatpak store 
I also use AppImages and AUR where necessary. Although after the AUR malware in recent months, I tend to go more for the other two routes more recently…
I read it, so it will be patched. That means I’ll wait for it to be done before updating.
I’m still stuck on kernel version 7.0.14, so I’m in no rush.
You are missing the point.
If I do a “journalctl -b -p0..3” I am seeing just this one message:
kernel: virt/tdx: TDX not supported by the host platform
The journal command i use specifies -p0..3 which means I only want to see "emerg" (0), "alert" (1), "crit" (2), "err" (3) (please check man journalctl for more details)
The output of this journalctl command is supposed to be empty. I use it to frequently check if my system has an issue. Now I see this message which is not an error or an emergency or anything close. If it would be just information I would not see it and I would not care. But it is in the journal as an error (-p3). That is wrong and that is annoying.
You’re missing my point. If your system is still working as before after an update and not causing you issues, there is no need to “solve” anything. Yes if you are running into an actual issue after an update the system journal is useful.
This particular cause the message was caused by upstream as they introduced something into the kernel not meant for consumer hardware so that message appear but it could be safely ignore. If I remember correctly they fixed it with a later update.
Of course it can be ignored because it is not an error. But it shows up as an error. And my script that relies on an empty output of journalctl -b -p0..3 is reporting it as an error. That is annoying. Thats all I am saying.
Although I understand the issue and I suppose that this is a real bug (that is being addressed) I could argue that it is possible that other error messages appear, if just because of other bugs.
I think it would be a good idea to have some kind of filter system in the script that checks if there are specific error messages. In other words, don’t shuffle issues under the table (you may need to revisit them later) but do ignore them if they turn out not to be an issue.
A bit of a regex filter could help, maybe check now and then if they are still needed.