The browser somehow switched its selected search engine from Duckduckgo to Google, and then tried to protect me by redirecting me to some weird 9oo91e.qjz9zk pseudo-domain which displayed a “blocked by Chromium” error. I honestly significantly freaked out, thinking this was the result of some malware infection, then found out via a web search on my PC that this seemed to be simply a normal trick from the ungoogled-chromium project. Not sure why the setting was set on Google on its own though. Setting it back to another engine fixed this behavior.
Apart from this (and the good old clock-slash-accessibility visual glitch from Feedback for v1.21 - #223 by alice_m), still happy. I charged my years-old FP3+ to about 95 % eight days ago and still have 32 % left. 