Hi, from my personal impression, the problems are clear. We have some likely solutions. I'd say we force *both* category and importance level to be given by the application (the more information, the more appropriate the server can handle it). Anything beyond that can be easily defined after a first implementation is there (like which importance levels, how to call them, which categories...). I don't anticipate a very complicated implementation with regards to the actual service, so changes should be relatively easy. The most complicated part of the thing is likely the settings panel. So, IMHO (of course), we should pick up discussion after Ryan has got something to show, unless someone has an idea which has really not come up yet at all. I'm just saying it, because *anything* can be misused, and I think we have found a reasonable approach. At a certain point, you have to let go and trust some responsibility with the user. If a developer misuses this service badly, you can always just deinstall the app or write an email to the developer. I mean there are ways, but we shouldn't let ourselves cripple our creative power by trying to forsee *too* much. Best regards, -Stephan