what's the reason for him showing us a screenshot though?
1) so search engines don't index and remember the text? I suppose search engines only read meta data from images and not OCR them when crawling?
2) if one grants him deeper technical knowledge of information security (I don't) then you could argue he has done the image/screenshot after creating the text in his WYSIWYG editor then after publishing the article, ... so that he could switch off any backend cgi or rdbms capability to reduce his attack surface (from lot of people who are currently digging for ways to poke around his internet facing system for ways of getting in)
Some wild guesswork: his website used to disallow right-clicking with a message that said he didn't want to share his images. Obviously people can get around that but whatever, this shows what type of person we're dealing with on a technical level. He might have thought that posting an image would prevent people from...copying the text or something? Searching for it? Who knows.
Of course, now it's HTML again, probably because he realized his website was getting hammered on bandwidth. Which makes me feel a little better about his health and well-being, since being concerned about bandwidth implies long-term thought processes.
1) so search engines don't index and remember the text? I suppose search engines only read meta data from images and not OCR them when crawling?
2) if one grants him deeper technical knowledge of information security (I don't) then you could argue he has done the image/screenshot after creating the text in his WYSIWYG editor then after publishing the article, ... so that he could switch off any backend cgi or rdbms capability to reduce his attack surface (from lot of people who are currently digging for ways to poke around his internet facing system for ways of getting in)