i'm interested in discussing the finer points of any proposals you make. i also have my own designs that i'm working on. you saw my first draft http api, i'm refining it now and will have subscriptions implemented probably eod tomorrow. uses a single listener for the client with a relay assigend ID and then subscribe/unsubscribe methods to activate/deactivate filters on the listener.

i don't really care that much to discuss issues around message types. i think you know i'm opposed to the whole kinds field altogether for the same reason as i oppose the numbered nips. i think document types should follow the HTTP standart.