Me and IP have decided on that we will not host OSmap or allow direct links within public view. We are also going to put in a rule that you cannot debate protection/unprotection unless the topic is specifically about debating the two due to the actions of some people.
The reason for doing this? Honestly some of the bullshit arguments (morality and whatever, which doesn't apply at all to the issue) we're hearing honestly was making us lean more towards hosting OSmap because they're just so stupid. This topic was intended to be how we handle discussion on these issues, not to
actually discuss it, but for some people that's simply too much to ask. People keep insisting on completely distorting and warping the issue with carefully chosen words.
So we looked at the facts. There is already one site with OSmap that supports it, so we'll keep SEN the way it is for the time being. Although a lot of the community has changed their views to the point where it would actually be okay to host it, two different sites with two different policies sounds much better.
I will still be spreading Open Mapping. Just so you people know:
Protection = Mappers corrupting maps to prevent other people from learning or editing them.
Open Mapping = Mappers leaving their maps as open and allowing people to edit or learn from them.
Unprotection = Mappers unprotecting or "fixing" corruption on maps so they can edit or learn from other mappers maps.
Really, the mapping community gives so much to you with free information like tutorials and downloads. I've been with the community for years and I don't usually ask for much, but leaving your maps as open is giving back to the community that gave so much to you. Consider it, if you will.
Also, me and IP previously talked about how to handle the maps db with the "do not edit flag" idea I had back at maplantis. It will be considered that authors who do not come on and claim if they want their map to be able to be edited or not are considered as "abadonware" until the author comes on. Anyone wishing to edit abadonware maps must look for any mappers wishes notices, and are encouraged to contact the original author. If the map was originally protected and the author did not come on and mark their map and "do not edit" on SEN, it will still be free to edit if the person who wishes to edit it can unprotect it. Most battle.net maps have been edited and then reprotected, so it makes no sense to limit people unless the authors are still around to "protect their investment" as "time is money" as some people say.
The discussion on protection vs unprotection is now basically over and going nowhere. You can now discuss these policy changes we'll be implementing.
None.