On clients and APIs

Apr. 20th, 2014 01:53 am
darael: Black lines on a white background.  A circle, with twenty-one straight lines connecting seven equally spaced points. (Default)
[personal profile] darael posting in [site community profile] dw_dev
Dreamwidth's APIs are poorly documented (people basically have to work off docs for old versions of LJ's APIs). They're also missing key features, like comment handling for more than backups.

I've been told there have been "some internal conversations about deprecating the XML-RPC API -- keeping it for backwards compatability, but moving to a much more modern second-gen API", but that nobody has had both the time and the inclination to work on designing such a thing.

Well, this is me, volunteering. To that end, I'm looking for input on what exactly such a new API needs to provide, and whether there's a preferred underlying technology to build on (exempli gratia, stick with XML-RPC? Change to SOAP? Use JSON? RESTful or not? et cetera). What I'm getting at here is that I'm entirely happy to take point, as it were, and to make decisions (especially where there's little or no consensus and someone has to make the call), draw up specs, write docs, and so forth, but the result is highly unlikely to be a really useful API unless I get input from more sources than my own experience and looks at the code.

At this stage, therefore, I want everything you, the reader, have to say on the subject. Use cases especially.

Go.
rydra_wong: dreamsheep with spork and "SheepSpork" logo; no, it wouldn't make any more sense if you saw it  (dreamwidth -- sheepspork)
[personal profile] rydra_wong posting in [community profile] metaquotes
[personal profile] minim_calibre had a terrible idea:

Or, why the hell did I decide to put on Acqua di Gio (pour femme)?

HELP, I SMELL LIKE 1995.

WHICH, APPROPRIATELY, WAS A YEAR OF POOR LIFE CHOICES.

I can't even review it. It's... a fruity floral with notes of Weezer.

"Heartbleed" security vulnerability

Apr. 8th, 2014 08:16 pm
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_maintenance
For those who have seen reference today in the press to the "Heartbleed" security vulnerability in OpenSSL, we'd like to reassure you that although we (like a large portion of the internet) were running the affected software, we patched our servers last night and were no longer vulnerable from that point.

We have no reason to believe that anyone was exploiting this vulnerability against us or that any user data has been compromised. We'll be changing our security certificates for extra confidence.

On the other hand, the nature of this vulnerablity means that it's impossible for a website to know for absolute certain whether someone was exploiting it. If someone was exploiting the vulnerability, against us or against any other website, they potentially have access to any information you sent to the site, including your username/password for the site and any data you sent to the site under HTTPS. It's a good idea to change your passwords pretty much everywhere, but don't do it until you can verify that a site is no longer vulnerable.

If you have any questions, feel free to ask!

Updated FAQ

Apr. 6th, 2014 08:04 pm
misskat: Picture of me with a lot of pink, smiling. (Kat at CONvergence)
[staff profile] misskat posting in [site community profile] dw_docs
Updated FAQ 104 to mention that backdating isn't available for community entries.

Profile

csjewell

June 2011

S M T W T F S
   1234
567891011
12131415161718
192021 22232425
2627282930  

Style Credit

Page generated Apr. 20th, 2014 03:51 pm
Powered by Dreamwidth Studios

Expand Cut Tags

No cut tags

Most Popular Tags