Actually, no! I would be a bit more lenient if this appeared to the case, although the response is still not great. As I mentioned in a comment further down the in the thread, it seems like the trigger for this was not Cellebrite doing its thing against Signal users (which is nothing new) but rather Cellebrite writing a blog post where they claimed that they could target Signal users (which Signal took to mean a claim that Cellebrite had broken their encryption): https://news.ycombinator.com/item?id=27172104