Cocoa (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
momijizukamori) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_dev2017-12-10 11:56 am
momijizukamori) wrote in dw_dev2017-12-10 11:56 am
Entry tags:
Looking for API testers!
The new API I've been working on (more discussion here) is getting to the stage where it needs lots of rounds of testing and feedback, because I am extremely scatterbrained and bad at testing. Benefits of helping:
1) get to play with API things now instead of whenever it's ready to go live on the production site
2) my eternal gratitude?
3) idk if you want some custom CSS or something I'm happy to help
In particular, I'd love feedback from people who make use of different security settings on tags, and access and subscription filters, because I don't use these features and thus am less certain of expected behavior.
Caveats
-I don't have API keys working yet, though they're partially written and mostly just need debugging right now. In the meantime, auth is via regular session cookies.
-posting photos is still in the works, because I have to interface with and/or convert an older API to fit the current API conventions, and trying to understand file uploads gives me a headache.
-There is no support for reading or posting comments (outside of inbox notifs) right now, because there needs to be some larger high-level conversations about privacy expectations and what kind of query load the servers can support before we can work out implementation details.
-Icons and image uploads aren't working because I was testing some icon stuff unrelated to the API and slightly borked my config - I will try to get that sorted in the next day or two.
How to do the thing
-Make an account on my dev machine. The workers for content import should be working, if you want to import content from Dreamwidth to play around with.
-Poke at the API - raw JSON-formatted description is here and a slightly cleaner HTML-formatted one is here.
-Leave me feedback! This can be anything you notice - down to 'you misspelled this word'. It's all gotta get fixed at some point, so don't worry about being too picky.
1) get to play with API things now instead of whenever it's ready to go live on the production site
2) my eternal gratitude?
3) idk if you want some custom CSS or something I'm happy to help
In particular, I'd love feedback from people who make use of different security settings on tags, and access and subscription filters, because I don't use these features and thus am less certain of expected behavior.
Caveats
-I don't have API keys working yet, though they're partially written and mostly just need debugging right now. In the meantime, auth is via regular session cookies.
-posting photos is still in the works, because I have to interface with and/or convert an older API to fit the current API conventions, and trying to understand file uploads gives me a headache.
-There is no support for reading or posting comments (outside of inbox notifs) right now, because there needs to be some larger high-level conversations about privacy expectations and what kind of query load the servers can support before we can work out implementation details.
-Icons and image uploads aren't working because I was testing some icon stuff unrelated to the API and slightly borked my config - I will try to get that sorted in the next day or two.
How to do the thing
-Make an account on my dev machine. The workers for content import should be working, if you want to import content from Dreamwidth to play around with.
-Poke at the API - raw JSON-formatted description is here and a slightly cleaner HTML-formatted one is here.
-Leave me feedback! This can be anything you notice - down to 'you misspelled this word'. It's all gotta get fixed at some point, so don't worry about being too picky.
no subject
That's on my to-do list :) The JSON file isn't sorted so it kind of goes in a random order every time it's loaded (because it's a hash, and hashes aren't sorted etc) - the web doc frontend is also fairly randomly sorted, I think, but honestly that was me just slapping a pre-existing package up there to provide some sort of interface that wasn't raw JSON. Once I get the actual api functionality a little better fleshed-out (and debugged), I'll probably make a custom page for the API docs that actually uses site-style rendering and whatnot.