One complaint about Devuan, not much ever happens, boring, uneventful, unexciting.
Yesterday I was updating/upgrading an old debian installation I had done 2 years ago and had not been updated for 2 months.  The user, relatively novice, has been using ascii instead for a while.  Debian broke its x half way through the upgrade.  I had to reboot manually and go to console and do dpkg --configure -recover ... (or whatever it is that resumes the upgrade) to get the system back.  I hadn't seen this ever before, losing the desktop half-way through an upgrade.  Needless to say the owner told me to just delete it as Debian is no longer used.  I convinced her otherwise as you never know when you will need a 2nd compatible system to chroot to the other one.  I agree, to save you some bandwidth, leaving a rolling distribution unupdated for months is not a good idea.  On this particular case, of a user not feeling confident to try apt update apt upgrade, Devuan hasn't had a problem "once".

Trolls please don't even think about pretending of having a problem.
People can tell, you know!

I'll try this or I'll transfer my laptop close to router so as to establish wire connection. The second seems more easy. Anyway,
It should not make the announcement for the stable edition, as debian didn't use this behavior. Now it's like experimental. I have to tell you I'm disappointed from the devuan project. 
PS. I'm user of debian. But when I tried the Devual rc2 I was impressed. So I decided to try the stable one.

I use the devuan ascii. Almost no problems for me. 

I am not sure though, you may have a less freedom friendly computer. yours might need blobs to work.  That can make a huge impact.

I do not trust anything with intel me still on it. or any backdoor of that sort.

1) I always chose auto.mirror.devuan.org which I believe resolves into something good. Did you use that as well, and had problems (even with a working network)?

2) It may depend on the "tasksel" choices. To be sure, you should stop at the grub installation dialog, and type ctrl-alt-f2 to gain command line access on vt2. At that point you can install e.g. either wicd-curses (for use without desktop environment), or wicd (otherwise). The command sequence would be as follows:

# chroot /target /bin/bash
# apt-get install wicd-curses
# exit

Thereafter you go back to the grub installation dialog with ctrl-alt-f5 (if you were doing "Graphical install"), or ctrl-alt-f1 (if you where doing just "Install"), and continue from there.

PS. I tried thr installation with a prepared usb stick