Unhosted Web Community Group - Activity in 2014
No matches.
Participants
-
1 participant joined.
-
Timofey Marinin joined.
-
GitHub
remotestorage/spec
-
2 issues closed.
-
CORS expose-headers doesn't need to contain Content-Type remotestorage/spec#80.
-
folder should contain? remotestorage/spec#81.
-
GitHub
remotestorage/spec
-
4 issues opened.
-
scope permissions remotestorage/spec#82, by @ghost.
-
folder should contain? remotestorage/spec#81, by @ghost.
-
CORS expose-headers doesn't need to contain Content-Type remotestorage/spec#80, by @ghost.
-
webfinger properties value must be string or null remotestorage/spec#79, by @ghost.
-
-
1 issue closed.
-
scope permissions remotestorage/spec#82.
-
-
1 issue reopened.
-
webfinger rel parameter remotestorage/spec#78.
-
-
5 issues received 20 new comments.
-
folder should contain? remotestorage/spec#81 (10 comments by @ghost, @michielbdejong, @raucao, @silverbucket)
-
CORS expose-headers doesn't need to contain Content-Type remotestorage/spec#80 (2 comments by @changetip, @raucao)
-
consider adding support for sharing/collaboration remotestorage/spec#58 (1 comment by @michielbdejong)
-
GitHub
remotestorage/spec
-
12 issues opened.
-
webfinger rel parameter remotestorage/spec#78, by @ghost.
-
WebFinger properties mix http and https remotestorage/spec#77, by @michielbdejong.
-
Webfinger authURL wrong in example remotestorage/spec#76, by @ghost.
-
Content-Type missing with WebFinger wire example remotestorage/spec#75, by @ghost.
-
304 status code never mentioned in Versioning section remotestorage/spec#74, by @ghost.
-
If-Non-Match: * on PUT requests remotestorage/spec#73, by @ghost.
-
node is also a folder, contradicting 404 remotestorage/spec#72, by @ghost.
-
Add proper README content remotestorage/spec#71, by @raucao.
-
correct language and typos remotestorage/spec#70, by @michielbdejong.
-
add a way to announce web authoring capability remotestorage/spec#69, by @michielbdejong.
-
Expires: 0 missing in Example wire transcripts remotestorage/spec#68, by @ghost.
-
does a non existing folder have an ETag response? remotestorage/spec#67, by @ghost.
-
-
12 issues closed.
-
304 status code never mentioned in Versioning section remotestorage/spec#74.
-
node is also a folder, contradicting 404 remotestorage/spec#72.
-
Content-Type missing with WebFinger wire example remotestorage/spec#75.
-
Webfinger authURL wrong in example remotestorage/spec#76.
-
WebFinger properties mix http and https remotestorage/spec#77.
-
consider mentioning the w3c manifest format when it comes out remotestorage/spec#66.
-
If-Non-Match: * on PUT requests remotestorage/spec#73.
-
Add proper README content remotestorage/spec#71.
-
does a non existing folder have an ETag response? remotestorage/spec#67.
-
correct language and typos remotestorage/spec#70.
-
add a way to announce web authoring capability remotestorage/spec#69.
-
Expires: 0 missing in Example wire transcripts remotestorage/spec#68.
-
-
1 issue reopened.
-
does a non existing folder have an ETag response? remotestorage/spec#67, by @michielbdejong.
-
-
10 issues received 32 new comments.
-
webfinger rel parameter remotestorage/spec#78 (8 comments by @ghost, @michielbdejong, @raucao, @silverbucket)
-
consider mentioning the w3c manifest format when it comes out remotestorage/spec#66 (7 comments by @michielbdejong, @raucao)
-
does a non existing folder have an ETag response? remotestorage/spec#67 (5 comments by @ghost, @michielbdejong)
-
304 status code never mentioned in Versioning section remotestorage/spec#74 (3 comments by @ghost, @michielbdejong)
-
consider adding support for sharing/collaboration remotestorage/spec#58 (1 comment by @michielbdejong)
-
Participants
-
1 participant joined.
-
Casey Kuhlman joined.
-
Participants
-
2 organizations joined.
-
University of Edinburgh joined.
-
University of Edinburgh [Duplicate] joined.
-
-
1 organization left.
-
University of Edinburgh [Duplicate] left.
-
GitHub
remotestorage/spec
-
1 issue closed.
-
require support for Hawk remotestorage/spec#64.
-
-
1 issue received 3 new comments.
GitHub
remotestorage/spec
-
1 issue opened.
-
consider mentioning the w3c manifest format when it comes out remotestorage/spec#66, by @michielbdejong.
-
-
1 issue closed.
-
Allow to patch documents remotestorage/spec#65.
-
-
1 issue received 17 new comments.
-
Allow to patch documents remotestorage/spec#65 (17 comments by @almet, @clochix, @ghost, @michielbdejong, @raucao, @waldheinz)
-
GitHub
remotestorage/spec
-
3 issues opened.
-
Allow to patch documents remotestorage/spec#65, by @clochix.
-
require support for Hawk remotestorage/spec#64, by @michielbdejong.
-
Reconsider using 404 responses remotestorage/spec#63, by @michielbdejong.
-
-
13 issues closed.
-
Reconsider using 404 responses remotestorage/spec#63.
-
compare with OpenID Connect remotestorage/spec#62.
-
align open web app manifest paragraph with DataStore API remotestorage/spec#53.
-
Specify for a variety of authorisation mechanisms remotestorage/spec#39.
-
Specify for a variety of authentication mechanisms remotestorage/spec#38.
-
Do not "SHOULD NOT" expiring tokens remotestorage/spec#36.
-
providers may/should offer a way to get a personal access token from their UI remotestorage/spec#60.
-
confusing wording "add a 'remotestorage' parameter to the URL fragment" remotestorage/spec#59.
-
support weak ETags? remotestorage/spec#61.
-
old format still mentioned for empty folder remotestorage/spec#54.
-
change http/1.1 and chunk from SHOULD to MUST in -03 remotestorage/spec#52.
-
consistently use 'folder', not 'directory' remotestorage/spec#56.
-
put application/ld+json content-type on folder descriptions remotestorage/spec#55.
-
-
1 issue reopened.
-
old format still mentioned for empty folder remotestorage/spec#54, by @michielbdejong.
-
-
10 issues received 31 new comments.
-
Allow to patch documents remotestorage/spec#65 (8 comments by @clochix, @michielbdejong, @raucao, @waldheinz)
-
Reconsider using 404 responses remotestorage/spec#63 (5 comments by @michielbdejong, @raucao, @waldheinz)
-
old format still mentioned for empty folder remotestorage/spec#54 (3 comments by @michielbdejong, @raucao, @waldheinz)
-
change http/1.1 and chunk from SHOULD to MUST in -03 remotestorage/spec#52 (3 comments by @michielbdejong, @raucao)
-
Specify for a variety of authorisation mechanisms remotestorage/spec#39 (2 comments by @michielbdejong, @raucao)
-
providers may/should offer a way to get a personal access token from their UI remotestorage/spec#60 (1 comment by @raucao)
-
-
1 pull request closed.
-
Rewording suggestion for OAuth wire transcript example remotestorage/spec#50.
-
GitHub
remotestorage/spec
-
1 issue opened.
-
compare with OpenID Connect remotestorage/spec#62, by @michielbdejong.
-
GitHub
remotestorage/spec
-
2 issues opened.
-
support weak ETags? remotestorage/spec#61, by @michielbdejong.
-
providers may/should offer a way to get a personal access token from their UI remotestorage/spec#60, by @michielbdejong.
-
-
2 issues received 8 new comments.
-
providers may/should offer a way to get a personal access token from their UI remotestorage/spec#60 (4 comments by @michielbdejong, @raucao)
GitHub
remotestorage/spec
-
2 issues opened.
-
confusing wording "add a 'remotestorage' parameter to the URL fragment" remotestorage/spec#59, by @michielbdejong.
-
consider adding support for sharing/collaboration remotestorage/spec#58, by @michielbdejong.
-
-
1 issue closed.
-
Publicly accessible URLs by default remotestorage/spec#57.
-
-
5 issues received 14 new comments.
-
consider adding support for sharing/collaboration remotestorage/spec#58 (5 comments by @michielbdejong, @raucao, @silverbucket)
-
confusing wording "add a 'remotestorage' parameter to the URL fragment" remotestorage/spec#59 (4 comments by @michielbdejong, @raucao)
-
Specify for a variety of authorisation mechanisms remotestorage/spec#39 (3 comments by @michielbdejong, @silverbucket)
-
Specify for a variety of authentication mechanisms remotestorage/spec#38 (1 comment by @michielbdejong)
-
GitHub
remotestorage/spec
-
1 issue opened.
-
Publicly accessible URLs by default remotestorage/spec#57, by @joepie91.
-
-
1 issue received 3 new comments.
-
Publicly accessible URLs by default remotestorage/spec#57 (3 comments by @joepie91, @michielbdejong)
-