Unhosted Web Community Group - Activity in 2015
No matches.
GitHub
remotestorage/spec
-
5 issues opened.
-
Cache-Control: no-cache also on failures? remotestorage/spec#140, by @ghost.
-
Think of a way to implement server-to-client push notification remotestorage/spec#139, by @michielbdejong.
-
rationale for ETag update propagation on change remotestorage/spec#138, by @ghost.
-
Consider need for MOVE verb remotestorage/spec#137, by @michielbdejong.
-
Mention comparison with WebDAV in the introduction remotestorage/spec#136, by @michielbdejong.
-
-
2 issues closed.
-
Point about updating version of folders left empty remotestorage/spec#133.
-
Changes in draft-dejong-remotestorage-06 but not in source.txt remotestorage/spec#129.
-
-
13 issues received 50 new comments.
-
Think of a way to implement server-to-client push notification remotestorage/spec#139 (15 comments by @ghost, @raucao, @untitaker)
-
rationale for ETag update propagation on change remotestorage/spec#138 (7 comments by @ghost, @raucao, @untitaker)
-
Redefinition of HTTP: Content-Type on PUT remotestorage/spec#130 (4 comments by @michielbdejong, @untitaker)
-
Mention comparison with WebDAV in the introduction remotestorage/spec#136 (4 comments by @ghost, @michielbdejong, @raucao)
-
Find a proper way of supporting resumable uploads remotestorage/spec#131 (3 comments by @michielbdejong, @untitaker)
-
Point about updating version of folders left empty remotestorage/spec#133 (2 comments by @michielbdejong, @untitaker)
-
Whether or not to mention response bodies for error responses remotestorage/spec#134 (2 comments by @michielbdejong, @untitaker)
-
Changes in draft-dejong-remotestorage-06 but not in source.txt remotestorage/spec#129 (2 comments by @michielbdejong, @untitaker)
-
Whether to mention conditional or unconditional requests in the intro remotestorage/spec#135 (1 comment by @untitaker)
-
-
2 pull requests opened.
-
Remove false changelog entry remotestorage/spec#142, by @untitaker.
-
client_id is already mandated by OAuth remotestorage/spec#141, by @untitaker.
-
-
2 pull requests received 10 new comments.
-
client_id is already mandated by OAuth remotestorage/spec#141 (8 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
GitHub
remotestorage/spec
-
16 issues opened.
-
Whether to mention conditional or unconditional requests in the intro remotestorage/spec#135, by @michielbdejong.
-
Whether or not to mention response bodies for error responses remotestorage/spec#134, by @michielbdejong.
-
Point about updating version of folders left empty remotestorage/spec#133, by @michielbdejong.
-
Change all ACAO values to * remotestorage/spec#132, by @michielbdejong.
-
Find a proper way of supporting resumable uploads remotestorage/spec#131, by @michielbdejong.
-
Redefinition of HTTP: Content-Type on PUT remotestorage/spec#130, by @untitaker.
-
Changes in draft-dejong-remotestorage-06 but not in source.txt remotestorage/spec#129, by @untitaker.
-
Use IRIs instead of URIs remotestorage/spec#128, by @untitaker.
-
Upgrade notes remotestorage/spec#126, by @raucao.
-
restructure specification remotestorage/spec#125, by @ghost.
-
Optionally support byte ranges support on PUT requests. remotestorage/spec#124, by @michielbdejong.
-
Restrict set of filenames allowed remotestorage/spec#121, by @untitaker.
-
Incorrect usage of URI_ENCODE remotestorage/spec#119, by @untitaker.
-
remove PUT range request support or define it remotestorage/spec#117, by @ghost.
-
add 413 (payload too large) to list of supported response codes remotestorage/spec#106, by @ghost.
-
Clarify whether apps are expected to have their own subdomain remotestorage/spec#104, by @untitaker.
-
-
12 issues closed.
-
Restrict set of filenames allowed remotestorage/spec#121.
-
Clarify whether apps are expected to have their own subdomain remotestorage/spec#104.
-
no longer mention speedy, but http 2.0 remotestorage/spec#102.
-
Add clear rationale for requiring Expires: 0 remotestorage/spec#95.
-
Rationale for disallowing wildcards in CORS GET headers remotestorage/spec#92.
-
Consider adding Kinto's extra features as extensions remotestorage/spec#90.
-
Let user select sandboxed directory to use? remotestorage/spec#88.
-
spec author remotestorage/spec#89.
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85.
-
GET requests are allowed for /public/. Why not HEAD? remotestorage/spec#94.
-
What etag to choose for empty folder listings? remotestorage/spec#93.
-
webfinger properties value must be string or null remotestorage/spec#79.
-
-
4 issues reopened.
-
Changes in draft-dejong-remotestorage-06 but not in source.txt remotestorage/spec#129, by @untitaker.
-
use client_id to identify clients remotestorage/spec#101, by @michielbdejong.
-
CORS on 304? remotestorage/spec#100, by @michielbdejong.
-
Rationale for disallowing wildcards in CORS GET headers remotestorage/spec#92, by @untitaker.
-
-
19 issues received 163 new comments.
-
define URI_ENCODE remotestorage/spec#103 (69 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
Optionally support byte ranges support on PUT requests. remotestorage/spec#124 (19 comments by @ghost, @michielbdejong, @untitaker)
-
Add clear rationale for requiring Expires: 0 remotestorage/spec#95 (16 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
add 413 (payload too large) to list of supported response codes remotestorage/spec#106 (13 comments by @ghost, @raucao, @untitaker)
-
Clarify whether apps are expected to have their own subdomain remotestorage/spec#104 (9 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
use client_id to identify clients remotestorage/spec#101 (6 comments by @michielbdejong, @raucao, @untitaker)
-
What etag to choose for empty folder listings? remotestorage/spec#93 (4 comments by @michielbdejong, @untitaker)
-
remove PUT range request support or define it remotestorage/spec#117 (3 comments by @ghost, @michielbdejong, @untitaker)
-
Changes in draft-dejong-remotestorage-06 but not in source.txt remotestorage/spec#129 (2 comments by @untitaker)
-
consider adding Resource Owner Password Credentials Grant flow remotestorage/spec#83 (2 comments by @michielbdejong, @raucao)
-
Rationale for disallowing wildcards in CORS GET headers remotestorage/spec#92 (2 comments by @michielbdejong, @untitaker)
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85 (1 comment by @ghost)
-
consider adding support for sharing/collaboration remotestorage/spec#58 (1 comment by @michielbdejong)
-
-
16 pull requests opened.
-
Frko 06 review 2 - rest remotestorage/spec#127, by @michielbdejong.
-
Clarify terminology around empty vs non-empty remotestorage/spec#123, by @untitaker.
-
Remove syntax specification of etags remotestorage/spec#122, by @untitaker.
-
client_id is already mandated by OAuth remotestorage/spec#120, by @untitaker.
-
remove PUT range request mention, issue #117 remotestorage/spec#118, by @ghost.
-
Frko 06 review 2 remotestorage/spec#116, by @ghost.
-
review of 06 spec remotestorage/spec#115, by @ghost.
-
Restrict set of filenames allowed remotestorage/spec#114, by @michielbdejong.
-
Restrict set of filenames allowed remotestorage/spec#113, by @untitaker.
-
Add recommendation to avoid unsafe/reserved chars remotestorage/spec#112, by @untitaker.
-
SPDY -> HTTP/2, fix #102 remotestorage/spec#111, by @michielbdejong.
-
Identify app by origin of redirect_uri remotestorage/spec#110, by @michielbdejong.
-
Allow leaving out CORS headers on 304s remotestorage/spec#109, by @michielbdejong.
-
Remove outdated requirement of echoing back origin in CORS remotestorage/spec#108, by @michielbdejong.
-
Allow leaving out 'me@' in user address remotestorage/spec#107, by @michielbdejong.
-
Clarify 401 vs. 403 remotestorage/spec#105, by @michielbdejong.
-
-
9 pull requests merged.
-
client_id is already mandated by OAuth remotestorage/spec#120.
-
Restrict set of filenames allowed remotestorage/spec#114.
-
Identify app by origin of redirect_uri remotestorage/spec#110.
-
SPDY -> HTTP/2, fix #102 remotestorage/spec#111.
-
Remove outdated requirement of echoing back origin in CORS remotestorage/spec#108.
-
Allow leaving out 'me@' in user address remotestorage/spec#107.
-
Clarify 401 vs. 403 remotestorage/spec#105.
-
Allow HEAD requests in public category remotestorage/spec#97.
-
Update webfinger example to conform to its spec remotestorage/spec#99.
-
-
10 pull requests closed.
-
Frko 06 review 2 remotestorage/spec#116.
-
Frko 06 review 2 - rest remotestorage/spec#127.
-
Clarify terminology around empty vs non-empty remotestorage/spec#123.
-
remove PUT range request mention, issue #117 remotestorage/spec#118.
-
review of 06 spec remotestorage/spec#115.
-
Restrict set of filenames allowed remotestorage/spec#113.
-
Allow leaving out CORS headers on 304s remotestorage/spec#109.
-
Add recommendation to avoid unsafe/reserved chars remotestorage/spec#112.
-
Clarify that folders are not created for each GET remotestorage/spec#98.
-
Narrow scope of 401 responses remotestorage/spec#96.
-
-
1 pull request reopened.
-
Add recommendation to avoid unsafe/reserved chars remotestorage/spec#112, by @untitaker.
-
-
18 pull requests received 134 new comments.
-
Frko 06 review 2 remotestorage/spec#116 (25 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
Restrict set of filenames allowed remotestorage/spec#113 (16 comments by @michielbdejong, @raucao, @untitaker)
-
Allow leaving out 'me@' in user address remotestorage/spec#107 (16 comments by @ghost, @michielbdejong, @untitaker)
-
Identify app by origin of redirect_uri remotestorage/spec#110 (14 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
remove PUT range request mention, issue #117 remotestorage/spec#118 (6 comments by @ghost, @michielbdejong, @untitaker)
-
SPDY -> HTTP/2, fix #102 remotestorage/spec#111 (6 comments by @michielbdejong, @raucao, @untitaker)
-
Remove syntax specification of etags remotestorage/spec#122 (4 comments by @michielbdejong, @untitaker)
-
Clarify terminology around empty vs non-empty remotestorage/spec#123 (3 comments by @michielbdejong, @untitaker)
-
Allow leaving out CORS headers on 304s remotestorage/spec#109 (3 comments by @michielbdejong, @untitaker)
-
Add recommendation to avoid unsafe/reserved chars remotestorage/spec#112 (3 comments by @ghost, @untitaker)
-
Clarify that folders are not created for each GET remotestorage/spec#98 (3 comments by @michielbdejong, @untitaker)
-
Remove outdated requirement of echoing back origin in CORS remotestorage/spec#108 (1 comment by @ghost)
-
Update webfinger example to conform to its spec remotestorage/spec#99 (1 comment by @michielbdejong)
-
GitHub
remotestorage/spec
-
8 issues opened.
-
define URI_ENCODE remotestorage/spec#103, by @ghost.
-
no longer mention speedy, but http 2.0 remotestorage/spec#102, by @ghost.
-
use client_id to identify clients remotestorage/spec#101, by @ghost.
-
CORS on 304? remotestorage/spec#100, by @ghost.
-
Add clear rationale for requiring Expires: 0 remotestorage/spec#95, by @untitaker.
-
GET requests are allowed for /public/. Why not HEAD? remotestorage/spec#94, by @untitaker.
-
What etag to choose for empty folder listings? remotestorage/spec#93, by @untitaker.
-
Rationale for disallowing wildcards in CORS GET headers remotestorage/spec#92, by @untitaker.
-
-
1 issue closed.
-
HTTP return codes remotestorage/spec#34.
-
-
2 issues reopened.
-
HTTP return codes remotestorage/spec#34.
-
webfinger properties value must be string or null remotestorage/spec#79.
-
-
11 issues received 67 new comments.
-
Let user select sandboxed directory to use? remotestorage/spec#88 (28 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
use client_id to identify clients remotestorage/spec#101 (12 comments by @ghost, @raucao, @untitaker)
-
What etag to choose for empty folder listings? remotestorage/spec#93 (10 comments by @ghost, @raucao, @untitaker, @waldheinz)
-
Rationale for disallowing wildcards in CORS GET headers remotestorage/spec#92 (4 comments by @ghost, @michielbdejong, @raucao)
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85 (1 comment by @untitaker)
-
-
4 pull requests opened.
-
Update webfinger example to conform to its spec remotestorage/spec#99, by @untitaker.
-
Clarify that folders are not created for each GET remotestorage/spec#98, by @untitaker.
-
Allow HEAD requests in public category remotestorage/spec#97, by @untitaker.
-
Narrow scope of 401 responses remotestorage/spec#96, by @untitaker.
-
-
3 pull requests received 9 new comments.
-
Clarify that folders are not created for each GET remotestorage/spec#98 (7 comments by @raucao, @untitaker)
-
Participants
-
1 organization joined.
-
Mobiletta joined.
-
GitHub
remotestorage/spec
-
1 issue opened.
-
Consider adding Kinto's extra features as extensions remotestorage/spec#90, by @michielbdejong.
-
-
2 issues received 12 new comments.
-
Consider adding Kinto's extra features as extensions remotestorage/spec#90 (10 comments by @ghost, @michielbdejong, @raucao, @untitaker)
-
Let user select sandboxed directory to use? remotestorage/spec#88 (2 comments by @michielbdejong, @raucao)
-
GitHub
remotestorage/spec
-
1 issue opened.
-
spec author remotestorage/spec#89, by @ghost.
-
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Mike Perlman joined.
-
GitHub
remotestorage/spec
-
1 issue opened.
-
Let user select sandboxed directory to use? remotestorage/spec#88, by @raucao.
-
-
1 issue closed.
-
Mention whitelisting of content types remotestorage/spec#84.
-
-
2 issues received 2 new comments.
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85 (1 comment by @elf-pavlik)
GitHub
remotestorage/spec
-
1 issue opened.
-
consider mentioning w3c capability URLs remotestorage/spec#87, by @michielbdejong.
-
-
3 issues closed.
-
webfinger rel parameter remotestorage/spec#78.
-
Content-Type not required on PUTs? remotestorage/spec#86.
-
consider mentioning w3c capability URLs remotestorage/spec#87.
-
-
1 issue reopened.
-
Mention whitelisting of content types remotestorage/spec#84, by @michielbdejong.
-
-
5 issues received 7 new comments.
-
consider adding support for sharing/collaboration remotestorage/spec#58 (2 comments by @michielbdejong)
-
consider adding Resource Owner Password Credentials Grant flow remotestorage/spec#83 (1 comment by @michielbdejong)
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85 (1 comment by @michielbdejong)
-
Participants
-
1 organization joined.
-
DUPLICATE Ripple Labs Inc. joined.
-
-
1 organization left.
-
DUPLICATE Ripple Labs Inc. left.
-
GitHub
remotestorage/spec
-
1 issue opened.
-
Content-Type not required on PUTs? remotestorage/spec#86, by @raucao.
-
GitHub
remotestorage/spec
-
3 issues opened.
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85, by @michielbdejong.
-
Mention whitelisting of content types remotestorage/spec#84, by @michielbdejong.
-
consider adding Resource Owner Password Credentials Grant flow remotestorage/spec#83, by @michielbdejong.
-
-
2 issues received 4 new comments.
-
Mention whitelisting of content types remotestorage/spec#84 (3 comments by @michielbdejong, @raucao)
-
Consider allowing host.com instead of user@host.com as identity remotestorage/spec#85 (1 comment by @michielbdejong)
-