Re: writes from Cimba to data.fm

I had to manually create the microblog directory, cimba picked it up from there.

I suggest logging issues in GitHub for cimba.  Yeah, it's a "bridged" app (for lack of a better word) but... End of the day. The signup button is on cimba. ;)

Also.  I suggest a few with old webid functionality does some uat perhaps with a vm.  

Personally, don't care if issues exist with i.e. But, signup ain't that easy when starting fresh.

Tim.h.

Sent from my iPad

> On 8 Apr 2014, at 4:29 pm, cr <_@whats-your.name> wrote:
> 
> https://www.youtube.com/watch?v=z0_XaJ97rF0 is certainly evidence that it "works for deiu"..
> 
> and probably any other user of rww.io.. of course, i want to know exactly what's required for all of this RWW thing to work. so had to write a webserver from scratch, and it's been a constant tweaking of things here and there since - ok, text/turtle posts weren't accepted.. ok OPTIONS wasn't saying this or that. ok a CORS header for * didnt' exist - but now we're in a credentialed scenario so it has to be the exact domain - or something - cue reading 12 more spec docs, gold source, mitmproxy of https:// sessions to data.fm with custom-imported snakeoil certificates..
> 
> furthest i can get using data.fm 'Creating...' on a 'microblog space' just hangs, with either a 200 or 400:
> 
> creating mb w/ #storage set to https://user.data.fm/space
> 
> POSTs a 0byte text/turtle -> 200 OK, blank "RDF file" appears in data.fm
> 
> #storage set to https://user.data.fm/ throws the aforementioned 400:
> <h1>400 Bad Request</h1>
> <p>Cannot read from a directory '/mnt/md1/srv/src/data.fm/data/cr.data.fm/'</p>
> 
> which looks like it's trying to read a file using a directory path
> 
> probably should just try rww.io, but it's no fun just duplicating the exact environment when interoperable implementations are the goal. but had to use chrome - seems like Angular.JS is broken in Firefox-28. getting uncompiled {{}} handlebar.js-looking templates mixed into a semiworking UI along with all sorts of exotic-sounding errors with strange-looking operators like //# or //@ http://mw.logbook.am/img/cimba.hmm.png
> 
> unclear on exactly what's different between rww.io and data.fm - clearly they are different, eg:
> p ~ curl -I https://notfound.data.fm/space
> HTTP/1.1 200 OK
> p ~ curl -I https://notfound.rww.io/space
> HTTP/1.1 404 Not Found
> 
> 'datawiki' scripts from 2008 also did 200 on every nonexistent but creatable resource
>

Received on Tuesday, 8 April 2014 06:36:27 UTC