The comments were :-
To my view this is very very misdirected anger. The error lies with Apple, not me. And I wonder what would happen if the sequence that crashed browsers was something like "flubble" or even something simpler like "hello" - would posting such, even knowing it crashed people, be unacceptable. What if it was someone's name (even if in Arabic)? Saying that everyone should avoid posting that person's name, even knowing that some people with broken software have some inconvenience, would be crazy. The fact it is a more obscure sequence of characters does not really change the fact that it is a valid UTF-8 sequence and there is no reason I should not post it.
He went on:-
This gets rather interesting. I is being suggested that technically, an act as to impairing operation of a computer is a crime. But if this Act was applied to this sort of thing, then I'll tell you now that I will be using a browser which crashes (is impaired) when it sees the word Cameron (as a made up example), so anyone tweeting or posting that on any forum is being reckless as to the impairment of my computer and breaking the law so must not do it. The scale is not a factor in breaking the law - intending to impair one computer is enough. Bingo, I now have a new troll hammer. It clearly makes no sense. In practice the legislation talks of unauthorised acts. For a start neither I, not the web server, did any "act" at all, the person choosing to navigate to my blog did the act, but even if you consider the server somehow complicit in an act, the act of "displaying text in a broswer" in such a context is clearly authorised bt the browser user, so IMHO(IANAL) it is not covered by the CMA anyway, so tough!
Yes, there is a risk that my blog caused some annoyance, or rather Apple's incompetence has caused some annoyance, not my blog post. Some people using rss feeds have suffered, apparently. The fact the blog post itself did not crash the browsers I tested meant I believed that it was not an issue, and so was not in fact reckless.
The annoyance needs to be directed at the party that has made the error, Apple.
My particular annoyance is not directly at the making of the error - I write software, I know the issues. The concern is the time taken to fix it. I am quite shocked that 24 hours after I knew about it Apple have not taken the current stable code on iPhone, iPad and Mac and patched it and released a patch with no other changes. They have the update mechanisms in place. Even with serious change control procedures, a patch like this that has such major impact should have been released.
What is worse is that one web site suggested Apple knew 6 months ago. Expecting 24 hours is probably optimistic for a large company, but not unrealistic for something major, but 6 months delay is totally unacceptable.
So, as it says at the top of my blog, "If you find any words or pictures menacing or offensive, stop reading now." Maybe I need to add "or likely to impair your computer".. I'll do that.