I thought that Ditto @Soapbox was meant to do that, but I don't know if it does anymore

Yup. So far Zapstore seems to be the only project that brings in external media like that, with analytics, comments etc... all gathered in one place (for outreach like you say...). The Mostr bridge in some way too I guess, but no clear picture to send to the external creators.

Zapstore is a great focused place to try that strategy indeed, at least you know you are targeting people who are serious about distribution and not entirely amateurs or shit posters.

Yeah. Anything more serious beyond "shit posting", like what we're trying, at the very least leads to good reality checks. You see pretty fast how much lower the value prop is without bringing in external content. You see the flaws of nsecs when you have to build customer service for devs signing releases. Like what do we even tell teams that keak their key? "F you, start over, we told you to be careful" Etc...

Interesting, haven't thought about that from your pov but I did consider how awful Pkarr is for an organisation even if it wasn't too long because of this issue. To be fair, not even Blockchain based key management is fool proof, but because the smart contract can mimic anything, a team can even use their control of a domain (and DNSSEC) to recover a Mlkut name... But even then, none of this comes for free you have to develop it. But Gnosis Safe is widely used by crypto companies to manage funds, so I assume it is adequate.

That being said, I am afraid many orgs will see Mlkut Name System and wonder why not just use RNS which allow them to rent their app actual name... And the name squatting argument won't land, so I suspect MNS and RNS might have to coexist.

Mmm, yea. But is RNS sovereign enough over just the usual domain names etc..., to justify any move/adoption from orgs at all? If the value prop is "sovereign", you go all the way, no?

Gotta make the names (and visuals for them) sexy enough 😜

I haven't looked too deep into the contract, but theoretically you can make a contract that doesn't allow any authority intervention not even to upgrade it. In that case I would count it as sovereign, you only pay rent. However, the same orgs that might prefer RNS to MNS, might also just prefer ICANN to Blockchains.. I also don't hate living in a world where apps support both .mns.alt and .rsk.alt MNS is primarily meant to work like phone numbers and be provisioned to users who never and would never pay for a domain... So if it also worked for orgs the way some orgs are happy with DIDs and Npubs, that's a bonus, but if they must use RNS, or even ENS, that's ok.

I don't think I can make the names any nicer, they sound Italian/latin and fun. The visuals on the other hand are at most placeholders... So I am supportive of anyone who finds a nicer defaults than a Go board :)

Actually I think I noticed that you can't have names in RNS shorter than 5 characters... Obviously because they don't want name squatting too early, but the frontend says that it will be enabled eventually, so I assume they have a way to activate this stuff. But again, many people are happy to trust a DAO, if anything ICANN is a fairly distributed organisation, but some people may assume a Blockchain DAO is easier to avoid regulation... That is yet to be challenged, but we will know if we started seeing ENS takedowns

Just checked again, and yup names are nice 👍