New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion for Host-Meta feature At Risk #97

Closed
aaronpk opened this Issue Apr 4, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@aaronpk
Member

aaronpk commented Apr 4, 2017

This issue is a placeholder for discussion of the "At Risk" feature of host-meta based hub discovery.

https://w3c.github.io/websub/#discovery

The working group knows of no publishers that depend solely on the host-meta based discovery, and believes that all publishers offer discovery in either of the two other ways. If you have an implementation that is only able to advertise its hub via host-meta, please comment below.

@sandhawke

This comment has been minimized.

Show comment
Hide comment
@sandhawke

sandhawke Apr 13, 2017

Contributor

There's an argument in #101 that host-meta for rel=hub is useless unless we also allow host-meta for rel=self (with templates) or allow rel=self to be optional.

Contributor

sandhawke commented Apr 13, 2017

There's an argument in #101 that host-meta for rel=hub is useless unless we also allow host-meta for rel=self (with templates) or allow rel=self to be optional.

@aaronpk

This comment has been minimized.

Show comment
Hide comment
@aaronpk

aaronpk May 5, 2017

Member

There has been some more discussion on the mailing list relevant to this topic, in support of dropping this feature.

https://lists.w3.org/Archives/Public/public-socialweb/2017May/0003.html

Member

aaronpk commented May 5, 2017

There has been some more discussion on the mailing list relevant to this topic, in support of dropping this feature.

https://lists.w3.org/Archives/Public/public-socialweb/2017May/0003.html

@julien51

This comment has been minimized.

Show comment
Hide comment
@julien51

julien51 Jun 5, 2017

Collaborator

I am still sad we cannot find a way to support all these static hosting platforms which do not let us alter headers conveniently (👀 at you Github!) and I worry that people (we?) will try to re-invent the wheel when inevitably some people wil try to achieve this...)

Collaborator

julien51 commented Jun 5, 2017

I am still sad we cannot find a way to support all these static hosting platforms which do not let us alter headers conveniently (👀 at you Github!) and I worry that people (we?) will try to re-invent the wheel when inevitably some people wil try to achieve this...)

@aaronpk

This comment has been minimized.

Show comment
Hide comment
@aaronpk

aaronpk Aug 23, 2017

Member

As discussed on the 2017-08-15 call, due to a lack of interest and implementations of the .host-meta method of endpoint discovery, the group resolved to drop the at-risk feature from the spec. https://www.w3.org/wiki/Socialwg/2017-08-15-minutes#resolution04

Member

aaronpk commented Aug 23, 2017

As discussed on the 2017-08-15 call, due to a lack of interest and implementations of the .host-meta method of endpoint discovery, the group resolved to drop the at-risk feature from the spec. https://www.w3.org/wiki/Socialwg/2017-08-15-minutes#resolution04

@aaronpk aaronpk closed this in 1295fea Aug 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment