a trick I have used in all languages to temporarily block out large sections (usually for test/debug/new-feature purposes), is to set (or define) a var at the top, and use that to conditionally comment the blocks; an added benefit over if(0) (samuli's comment from nov'05) is that u can have several versions or tests running at once, and u dont require cleanup later if u want to keep the blocks in: just reset the var.personally, I use this more to conditionally include code for new feature testing, than to block it out,,,, but hey, to each their own :)this is also the only safe way I know of to easily nest comments in any language, and great for multi-file use, if the conditional variables are placed in an include :)for example, placed at top of file:<?php $ver3 = TRUE; $debug2 = FALSE; ?> and then deeper inside the file: <?php if ($ver3) { print("This code is included since we are testing version 3"); }?><?php if ($debug2) { print("This code is 'commented' out"); }?>, Comments do NOT take up processing power. So, for all the people who argue that comments are undesired because they take up processing power now have no reason to comment ;), And with that, you have a fresh new comment system based on the Fediverse for your blog! Note: I’ve kept as a fallback for existing posts (with existing comments) Disqus, so if a post does not define a toot ID, then the comments system fall backs to Disqus..