Thanks for the update! I would have attended this meeting if it wasn’t at 2 AM CET. Having said that, right off the bat, I have three low-hanging integrations to put forward:
Arweave integration: Integrate Arweave into the avatar field and other content/text-records where it is relevant. This statement needs more context; for that keep reading.
Well-Known URI integration: Well-known URI standard is a very simple framework that allows reading of host metadata before making requests. It can be used to do cute tricks like the one some esteroids discord people pulled recently. This trick requires creating a hidden .well-known repository inside the Arweave or IPNS hashed directory, and then manipulating the files and metadata contents inside this directory. In the cute trick mentioned above, BTC payments over Lightning Network were enabled using an ENS domain stdin.eth as the router. There are possibilities to do more here, such as automatising the Well-known URI setup for generic tasks when an ENS user requests it through a text record.
lnurlp integration: This is essentially the cute trick mentioned above that requires setting a lnurlp record inside .well-known URI. Create a dedicated lnurlp text record for ENS domains and use it to demonstrate metadata routing capabilities of ENS + IPNS/Arweave.
Vanity integration: Linking this here: New App Preview: https://preview.ens.domains/ - #6 by inplco