How do you feel about adding URLs to attestations?

Is it worth it to have them knowing they might break eventually?

E.g.:

String
urlForSomething

stackrlabs.xyz // software dev interested in dev tools, threat intel, chain analysis, MEV // coordination, public goods, game theory // zkcat_eth.twitter

A network of technologists & journalists supporting digital public infrastructure for /journalism & media | https://journodao.xyz/

co-founder @nounsamigos.eth working on /nouns-amigos and the Nouns Fair | prev. MetaMask, Bitso, GBM+

Organization services: www.clinamenic.com
 // 
Newsletter: solosalon.clinamenic.com // @journodao @opencivics // /journalism /philanthropy

I’ve resolved not to use URLs but eth addresses since those are meaningful for this use case. 

To give more context. This is to attest houses/rounds/winners in @prophouse 

Houses and rounds are eth addresses. Proposals have an ID and belong to a round.

Thank you both for your input! @zkcat @clinamenic

Yeah agree with @zkcat, URLs can be included as fields, but ideally wouldn’t be relied on for whatever you’re trying to achieve. Arweave and IPFS hashes seem preferable to me, and that’s what we’re doing with @journodao’s new attestation project, PermaPress (a publishing/indexing tool).

All URLs should be considered temporary, so not a fan

a better alternative might be to store IPFS hashes which can be used with any IPFS resolver