Comment by 🚀 jsreed5
Do you know if this was a bug in the cargo distribution of ALFIS, or was it a configuration issue on your machine? I run ALFIS on my home server, but I use a precompiled binary from GitHub, and I originally generated my keys on the Windows build.
Apr 21 · 2 weeks ago
3 Later Comments ↓
🚀 fstfabi [OP] · Apr 21 at 19:35:
once you have the 'key.toml' files saved and backed up you're fine. I just didn't know the GUI didn't come with a save dialog until I needed one.
🐙 norayr [mod] · Apr 21 at 20:18:
one question:
if someone can mine a domain by running a computer for 3 days, can someone else mine same domain in same time and fake the domain by pointing it to their own server?
do you need to run alfis constantly if you have already mined the domain?
do you have to run it a client?
📻 eugene [mod] · Apr 22 at 06:20:
@norayr
No solid clue to the first question. It would make the system pretty useless if that were possible though.
For the other two, though, the answer is definitely no to both: You need to leave ALFIS running for a few minutes after mining completes for the domain to stick, because other participants need to sign the block you just produced, but that's it. You don't have to run it to resolve ALFIS domains either: you can use, e.g., Reverton's in-Yggdrasil servers to do it. And you don't have to trust them for anything outside the ALFIS TLDs either, but that's a matter of configuring your resolver.
Original Post
A sad Alfis moment — decided to try out alfis for dns. installed via cargo. ran it for a combined 30h or so. key finally mined. click 'save key'. a 'tiny file dialogs' opens, telling me it's missing software to give me a proper save dialog. "press enter to continue". window unresponsive. crashes. no key saved. dns is overrated anyway.