Yes it is confusing, there's a lot to learn with spaces that's for sure.

The good news is now that the protocol is finally built and live on Bitcoin mainnet, the focus has shifted to building tools that make spaces easier to interact with. Everything is open source.

[To be clear:

This spaces wallet you screenshot above is not an official wallet built by the core team. It was built by Andrew Lunde, who's an enthusiast of the project. He won the @TabConf name in auction (Bitcoin block #953,822 Transaction id ffac0ff85c2ed26e6a417aced6302d344420fe2033241d8e5631f56e759b8a9a) and was giving away names at the tabconf event. He's been away dealing with a personal matter for the past week or so after the burn.

I'm not an official member of the team either and I'm not affiliated with spaces wallet. I just see real value here and want more people to learn about spaces.

The official wallet built by the core team is the Akron wallet (akron.io) that allows users to manage top level spaces, bitcoin bidding, etc. and the Nacho app (nacho.io) that allows users to manage handles and point them at anything they want. Also the official sites (spacesprotocol.org) and (atbitcoin.com).]

As far as the @TabConf name, that's done. From the lead developer ''subs is asking if they (the owner of the @TabConf space) have the .sdb file for the zero hash commitment, proving its a continuation of the @tabconf tree, but it doesnt exist. so it cannot be recovered, ever.''

Only the handles that were minted under @TabConf can be used, no further handles can ever be created under that space.

There's billions of other names available though, tabconf is a cool thing and it's cool if you got one, but there's plenty more. Both top level spaces and handles.

You can roll out new top level spaces with Akron wallet or through the space-cli. Then create your own handles.

or

You can register an @bitcoin or @orbee name through the Nacho app.