{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/bbdfde19f55c80d3115650ab020bc7b1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bbdfde19f55c80d3115650ab020bc7b1","url":"https://api.github.com/users/Sleaker","login":"Sleaker","id":702071},"assignee":null,"updated_at":"2011-11-17T16:18:56Z","labels":[],"closed_at":null,"comments":9,"url":"https://api.github.com/repos/codename-B/bPermissions/issues/13","body":"The way you're handling case-sensetivity is causing massive amounts of issues with people attempting to use your plugin.Confusion in what needs to be set, which plugins use uppercase-partially in their permission checks, and in plugins that need to add permissions transiently.\r\nI suggest going back to what Bukkit does, instead of breaking functionality from what bukkit already provides, like what certain other permission developers do...  \r\n\r\nSecondarily. Why would you possibly want case-sensitivity on them, when are you going to use 2 permissions that are identical but differently cased?\r\n\r\n","html_url":"https://github.com/codename-B/bPermissions/issues/13","title":"Case Sensetivity","number":13,"id":2259905,"created_at":"2011-11-16T18:34:10Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/bbdfde19f55c80d3115650ab020bc7b1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bbdfde19f55c80d3115650ab020bc7b1","url":"https://api.github.com/users/Sleaker","login":"Sleaker","id":702071},"updated_at":"2011-11-17T16:18:56Z","url":"https://api.github.com/repos/codename-B/bPermissions/issues/comments/2777969","body":"and this is exactly why using permission nodes for chat info is not a good idea.","id":2777969,"created_at":"2011-11-17T16:18:56Z"}}