heya,

i made the package a little while ago to house a similar package i was working on (@js) however i stopped working on due to how simple the api and questioning if there really is a real reason to need a wrapper for it. that being said i am interested in how you approach your project so come back to me when you’re done and i’ll take a look to so if it makes sense to use that package name. if it fits a role not yet filled, it is also possible for me to converse with jeffalo about making it an official package under the wasteof org scope, which may make more sense depending on what your package is/does.

in the meantime i’m curious what you’re planning are, as i’m fairly well versed in the api and may be able to give some pointers, so whats the general idea thus far?