Namebase features

Part of the power of blockchain coins comes from the freedom to move the tokens around without too much red tape involved. Most cloud wallets allow transferring the coins to other wallet addresses, or at least to other user accounts. It's particularly important for the name community when we want to do things like donate funds to help claim names for open source projects or nonprofits. There are also tons of other important use cases.

As of now, the only way for any Namebase user to set up a secure website is to host their own DNS server and enable DNSSEC on it. Enabling it on Namebase DNS helps everyone to set up secure websites without having to maintain their own cloud server. This feedback post focuses on part 1 (of 3) below. One idea on how Namebase can support in stages: 1) Enable DNSSEC in Namebase DNS This lets the tech savvy people manually set up https without having to spin up own nameservers. Namebase DNS is based on powerdns so it's essentially a toggle from OFF to ON (but you guys would probably want to test it a bit I think ;)) - shouldn't take a lot of effort/time. 2) Set up DNSSEC for newly registered names Automatically add DS records along with the ns1 and ns2 default records being set pointing to nb dns. Again, will need a bit of code to get the value for the record first, but doable. At this point, anyone hosting a site somewhere (heroku or wherever) can set up https without a lot of work (but it's still manual process). 3) Add SSL support to thr Sia Gateway and set the TLSA record in Namebase DNS Now to get https on dlinks, the gateway should use an SSL certificate which changes for every domain. This may take work, and the community can help if open source contributions to make this work will be accepted. Dlinks will also need a small change to add 1 extra TLSA record, again, not much work. At this stage, dlinks will automatically have https.

I would prefer to use either liquid or lightning network technology for this. I want to buy a name for my website and email and don't want to spend 5 or 15 bucks on the transaction on top of the price of a single domain.

For domains that are NOT listed for sale, but set to accept offers, display "Offer" button in the "Domain search" page. Ex: attached

Given the risk of losing domains due to user error from forgetting to renew it within the 2-year period, would be great if there was an auto-renew feature that could take care of this for us. Maybe a simple switch "Auto renew on/off" on the auction page or the TLD page. Similar to how you guys have the great UX benefit of auto-revealing. As a new user, forgetting to reveal and forgetting to renew are the two biggest headaches I face. You guys took care of the reveal, would be great if you had functionality for auto-renew as well. Could be opt-in or opt-out as default. Happy to discuss the idea further. Apologies if this exists already and I missed it.

Emoji ZWJ Sequence is a combination of multiple emojis which display as a single emoji on supported platforms. These sequences are joined with a Zero Width Joiner character. Why is it that Namebase doesn't show them as a single emoji? On most platforms and devices they are displayed as one. Example: 👨🏽‍🦰 - > on Namebase 👨🏽🦰 The Man: Medium Skin Tone, Red Hair emoji is a ZWJ sequence combining 👨 Man, 🏽 Medium Skin Tone, ‍ Zero Width Joiner and 🦰 Red Hair. These display as a single emoji on supported platforms. https://emojipedia.org/man-medium-skin-tone-red-hair/ I would welcome it that Namebase upgrades to support display these as single emojis

To improve security, add an option to activate 2FA when withdrawing funds from Namebase.

Having the ability to flag an HNS domain as toxic/harmful when viewing the marketplace, search, or an auction would go a long way in stopping bad actors from using them for nefarious purposes. Allowing the community to find and buy such names and then transfer them to a safe namebase wallet where it will be kept off market would also be a solution. Both would improve the safety and adoption of the dweb going forward. Thanks.