You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a special case, since the string that is recognised is only used as the label for a hyperlink to https://15-15-15.social/@instituto_resiliencia. The link clearly does not point at a mailto: URI.
This is because of a design choice made in how Mastodon addresses are displayed. The @ is shown directly before of the string that is recognised as an email address, but not part of the link anchor.
It appears check-if-email-exists, of which an outdated fork exists at github.com/lycheeverse/check-if-email-exists, which has fallen back considerably behind github.com/reacherhq/check-if-email-exists, does not recognise that the link points some place else. Eventually by grepping the whole file for a regular expression matching an email pattern, not considering the semantics of the HTML.
What would be the best way to proceed from here?
The text was updated successfully, but these errors were encountered:
When running Lychee on degrowth.net/organisations/instituto-resiliencia/index.html, it reports, that the email address cannot be reached:
This is a special case, since the string that is recognised is only used as the label for a hyperlink to
https://15-15-15.social/@instituto_resiliencia
. The link clearly does not point at amailto:
URI.This is because of a design choice made in how Mastodon addresses are displayed. The @ is shown directly before of the string that is recognised as an email address, but not part of the link anchor.
The HTML in action:
It appears
check-if-email-exists
, of which an outdated fork exists at github.com/lycheeverse/check-if-email-exists, which has fallen back considerably behind github.com/reacherhq/check-if-email-exists, does not recognise that the link points some place else. Eventually by grepping the whole file for a regular expression matching an email pattern, not considering the semantics of the HTML.What would be the best way to proceed from here?
The text was updated successfully, but these errors were encountered: