It’s hard enough. Let’s do better and rationalize the process. This will be a difficult battle, especially in the communities considering security issues, especially in the current development track of WordPress. We should start a serious conversation about WordPress security, how to communicate and project, and what we are saying to site owners. Changes are made in collective groups, not individual users or suppliers. To be honest, I don’t know who is responsible. I think it is unfair to put this on the shoulders of the core team. And, as mentioned earlier, it’s not a matter of programming. I want to know where the appointed security car fits in with the grand plan. We should begin to hold ourselves and others more accountable, better manage the type of information we distribute, and focus on value based articles and discussions. Instead of harassing customers, we should conduct a centralized security demonstration on all Wordcamp. Let’s think about our responsibilities as site owners. Responsibility for managing the network. It is your responsibility to ensure that the user experience is secure. How do these ideas align with the problems the community sees in safety and your own?
