Discover rel="payment" links.

Prompted by #2, but since this suggestion should probably not be the primary means of determining a payment URL (favouring something explicit in package.json would be better in my opinion) I've moved it to this issue to avoid adding noise to #2.

In the wild there's a microformat to make payment URIs discoverable within a webpage. The gist is that any link or anchor with a rel="payment" contains a payment href (and ideally also a title attribute to describe it) which resolves to a means to donate. I've made a scraper for these in this module (only checks HTTPS pages by default).

The package file contains a couple of opportunities to use this. The homepage field would be useful for project-level donations, and author info which includes a URL could be used for personal donations.

Pending the outcome of #2, and if you think it's an idea worth persuing, I'd be happy to open a pull request.

Cool, didn't know about this spec. I definitely think that explicit package.json is the way to go, but I'll leave this open until that's implemented to see how it goes.

Yup, it definitely makes sense to favour explicit links.

Argh, sorry. Creaking browser and poor aim with my clicking.

should start reading links from .github/FUNDING.YML should be the the go to method of adding themself into the list instead of sending PR to add themself, easier then parsing readme rel links