Can we already do a DNS change at url server so we can show the #shakespeare #mkstack when people use use url www.traveltelly.com !? Instead of a sharing a strange/ long url nostr:nprofile1qqsgvxzpp84wjd7c6mucpd9qk3k6fmcdnql2meqracd5czmtmc3ck3cpz4mhxue69uhkg6t5w3hjuur4vghhyetvv9usdz6n9a nostr:nprofile1qqsfxfs52ud0ewk569apj8hzs83ea6amgxunlty0mpuzjc32avgj7ngpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q3gamnwvaz7tmjv4kxz7fww4u8gmewdahx2kuhsyh nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzxmhwden5te0vakx2ctndahxzar0wghxgetk9aex2mrp0yeru66d
Discussion
I believe this might be a far-future idea, but at this very moment, you could create a CNAME record and/or redirect via an external DNS provider. Here are some examples from Namecheap:
Just in case - if this is in reference to the share URLs for sites, you would likely need to do something akin to the following to use a different URL than the base URL of the site (https://*.shakespeare.to):
But if I add the url frome shakespeare project in this ‘TXT’ from nostr-admin that does not work I think!?
Hm, is this to identify an admin pubkey externally via DNS?
This goes a bit outside the scope of Shakespeare the tool, but answering this in the context of an external project - you'd have to tell the application to fetch a TXT record for your domain. As long as the DNS record exists externally for said domain (e.x., traveltelly.com), then the application should be able to fetch it regardless of where it is actually hosted.
You would have to explicitly instruct the agent to "retrieve TXT records from traveltelly.com and extract the key value for nostr-admin-pubkey". This request is a bit more 'complex' for something like Shakespeare/mkstack to handle. It's not completely impossible, but it's certainly outside the scope for what the current tooling is intended to support; or rather, unfortunately, you would be heavily relying on the LLM's direct knowledge/capabilities to make this function. 😔
Ok don’t really get it. I think most normies like me like to know ones you build you project, you want to keep updating it but also show case/ use on a normal site/url. I think it’s a very important thing for people who are not devs and use shakespeare. Also let nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgzaq60d nostr:nprofile1qqsfxfs52ud0ewk569apj8hzs83ea6amgxunlty0mpuzjc32avgj7ngprpmhxue69uhkummnv3exjan99eshqup0wfjkccteqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap05dgt5x nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309aex2mrp0yhxummnw3e8qmr9vfejucm0d5hst8nxq7 know this :) We are not all devs on Nostr at least some not😂 and if you want to have more creatives/non-devs use the product we think how can we show it all. Just sharing my content creators side📸🙏🗺️
Ah, for using a normal site URL - that will likely be supported (or more nicely documented) in time. I agree, that is a common use case that should be more easily supported. I will relay your feedback in any case!