Single post in Implementing A 'Block' Feature

re: lag Blocking won't have as much of an impact on the site as you think, D33R, specifically because we are likely not going to add the most lag-inducing aspects such as Shelter filtering (re: making sure you don't encounter eggs bred by a blocked user). Asking Sally to check all 40 eggs for their OTs every time you refresh would just be too much especially given that the Shelter is an already resource-intensive feature. This has pretty much been deemed too lag-inducing for not enough benefit to be practical. There's already less than a 1% chance you'll run into an egg hatched by someone you've blocked simply due to the sheer number of eggs in the Shelter. That's why "but the lag" is largely a non-point -- it's simply unlikely that this or other major lag-causers would be added to the block feature due to this exact concern. Those features would need to provide a benefit that is applicable to enough people and/or in enough instances to be worth it vs the server system's resources used or otherwise occupied by those processes. So, please do not use lag as a reason to not support this. Niet can make things work and will do whatever is possible to minimize the impact it has on the site in terms of lag. Don't worry about the implementation of it, and just stick to the pros and cons of the block feature itself and the features that you would like to see accompanying it.