We are using the w3name service for making sure our IPNS keys are constantly republishing. w3name announced they would be deprecating the service in January.
Does anyone know about any good alternatives? Or is this the writing on the wall that we should build this service out in-house?
Here’s a blog post that outlines how we are using IPNS: https://blog.dappling.network/adding-ens-support-to-dappling/
For other readers, if you follow the link they do say why they didn’t do this in-house from the beginning, basically crummy documentation about how to actually do it.
For the poster, I’d say that yes, if you have the resources to do it, this sounds like something you should do in-house. Maybe use Kubo for NS even if you use Helios for everything else? Kubo might be more mature and easier to set up for something like this.
Also, the main alternative to IPNS is DNSLink, and I don’t see that mentioned in your blog post. Maybe DNSLink would work for your case, and it sounds like you’d have the centralized platform to operate the nameserver needed for it, in-house.
web3 is centrally controlled malware, I’d avoid any scammers who have anythign to do with “web3” as they can only be scammers, no different from psychopaths like Vitalik and other premine scammers, rug pullers, liars, and thieves. it’s not possible for an intelligent or honest person to fall for “web3” where what controls everything is centrally printed by 1 party. if you can count to 1 party in control, you’re smarter than every web3-tard or eth-tard there is. counting to 1 is math beyond those brainless trash. as they can’t count to 1 or lie about it, they are not developers, they are scammers. treat any of them same as you would similar psychopaths like child abusers, 0 difference in personalities.