search

whatwg / html

HTML Standard
https://html.spec.whatwg.org/multipage/
Other
7.98k stars 2.61k forks source link

"4.6.6.23 Other link types Extensions to the ..." #3704

Open reschke opened 6 years ago

reschke commented 6 years ago

https://html.spec.whatwg.org/multipage/links.html#other-link-types

4.6.6.23 Other link types

Extensions to the predefined set of link types may be registered in the microformats wiki existing-rel-values page. [MFREL]

Registration is defunct, in that new users are required to pass a reCAPTCHA V1 which has shutdown.

annevk commented 6 years ago

cc @tantek

tantek commented 6 years ago

Registration (on the microformats wiki) works fine. I just tried it and created a new account. If you are having trouble understanding the microformats wiki, whether with registration or anything, please state the problem as a question and check the FAQ accordingly: http://microformats.org/wiki/faq

Recommend closure of issue #3704, works for me, no changes to HTML Standard needed.

(Originally published at: http://tantek.com/2018/143/t6/)

reschke commented 6 years ago

The account registration box embeds a captcha that says:

 rePCAPTCHA V1 IS SHUTDOWN
 Direct site owners to g.co/recaptcha/upgrade

How am I supposed to pass it? Leaving the field empty leads to:

Login error: Incorrect or missing confirmation code.
reschke commented 6 years ago

Ping?

sideshowbarker commented 6 years ago

I can confirm that the login page displays a big red rePCAPTCHA V1 IS SHUTDOWN thing:

captcha

…and as can be seen in the screenshot above, there’s no way to pass the captcha — it doesn’t display in any captcha text, so there’s nothing you can type into the Type the text input field to match.

sknebel commented 6 years ago

FWIW, the captcha check fails open, so any input is accepted. E.g. I created a new account using "kittens kittens" as the captcha solution.

prlbr commented 5 years ago

The microformats wiki still includes the defunct captcha for user registration.

Additionally passing the captcha is required in order to post external links (references, links to implementations, examples …), but it has not been possible to pass it anymore for months. This has been known to site administrators for at least four months.

Sorry, but this is unacceptable for a website which is officially responsible for HTML's rel extensions and thereby also determines whether HTML errors are reported by HTML validators or not. Please fix microformats.org as soon as possible or create an alternative solution to register rel values.

sideshowbarker commented 5 years ago

Please fix microformats.org as soon as possible or create an alternative solution to register rel values.

I’d support moving the existing set of allowed values from the microformats wiki into the HTML spec, and making the new registration mechanism be that when you want to add a new value, you create a pull request with a patch.

a3nm commented 5 years ago

I also don't think it makes any sense for the spec to direct users to a wiki to register new authorized values. Note that the spec also says that conformance checkers are expected to somehow scrape the wiki to find the correct values, and that they should also offer to add unknown values to the wiki.

This problem has been discussed already on the two previous bugtrackers, since 2011:

Now that registration on the wiki is dead, I really think it's time that the set of allowed values be moved to the spec. Barring this, the spec should clearly indicate that conformance checkers should accept any value and not pretend that the set of allowed values is normatively maintained on a defunct wiki.

BigBlueHat commented 5 years ago

The captcha is indeed missing now (so registration isn't possible). The site also lacks HTTPS support.

Meanwhile, IANA is now (since 2017) using a GitHub link-relations/registry repository for managing it's Link Relations registry.

That repository is covered by the IETF's contribution terms as well as code of conduct.

Perhaps there is a way to combine efforts?

mnot commented 5 years ago

Happy to try to combine efforts again. As @BigBlueHat says, we're using a GitHub issues list to manage that registry now, so it should be lower friction.

We're also looking at refining that (input welcome) to make it easier, and putting more Web-related registries there (probably under a dedicated org). Next up should be well-known URIs, then HTTP headers.