AlienDomains

In memory of… One day, your phone will stop receiving messages from someone you love. Their number will still be there. Their photos will still be there. But their voice? Their stories? The little things only they knew? Those can disappear. Unless we choose to preserve them. Imagine a future where a child can meet their great-grandfather—not in person, but through his voice. Hear the stories he told. See the photographs he treasured. Discover what he built. Read the letters people wrote about him. Understand why everyone who knew him said: “You had to know him.” That’s bigger than a memorial. That’s memory becoming inheritance. With .inmemoryof, a life can have a permanent digital home. With .inlovingmemoryof, families can build a private collection of the things that made someone unforgettable. freename.com/discover/inmemo… With .foreverinourhearts, an entire community can contribute—one photograph, one story, one recording, one memory at a time. And maybe that’s the future of remembering. Not simply keeping someone’s name alive… but keeping their presence alive. Because death may take a person. It doesn’t have to take their story. And when generations from now ask, “Who were they?” We should have more to give them than a name on a stone. Give them a voice. Give them a story. Give them the memories. Give them the legacy. Because the people we love shouldn’t become forgotten chapters. They should become stories we keep telling. #DigitalLegacy #InMemoryOf #ForeverInOurHearts #InLovingMemory #Legacy #PreserveMemories #FamilyHistory #NeverForgotten #Memorial #OurStories

🚨 FYI for the Web3 domain community There is an important issue worth understanding as .robot potentially enters the ICANN process. If you own FYI.robot in a Web3 naming system, that ownership exists within that alternative naming system. ICANN recognizes that blockchain-based naming systems operate outside the global DNS. (ICANN⁠) If .robot ultimately becomes a delegated ICANN TLD, that does not currently mean that your existing Web3 registration automatically becomes a DNS registration. What happens to existing Web3 names—and whether they can be integrated with corresponding DNS names—is an open technical and policy question. In fact, ICANN has established a Technical Study Group specifically to examine the implications of integrating the same gTLD name into alternative naming systems. ICANN says such integration could create security, stability and usability challenges if appropriate controls are not established. (ICANN⁠) So the questions the community should be asking are: 🔹 Will existing Web3 .robot registrants receive any priority or protection? DEMAND ANSWERS AS A CONSUMER! Or stop consuming if they don’t answer! It’s that simple. Power in the numbers. 🔹 How will existing on-chain registrations be treated if .robot is delegated in the DNS? 🔹 Can the same name be reliably associated across both systems? 🔹 What rules will apply to registrations and ownership if integration occurs? These questions do not have a predetermined answer yet. This isn’t an argument against ICANN or Web2. It’s a call for transparency and clarity for people who already own Web3 names. Before assuming that an ICANN .robot and a Web3 .robot will have identical ownership rights, understand that they currently belong to different naming systems. Web3 owners deserve to know how their existing registrations will be treated before the rules are finalized. #Web3 #ICANN #Domains #Blockchain #DNS #DigitalIdentity #TLD #UnstoppableDomains #Internet