The https://mt.lv/nightly-build (which redirects to box.com) now requires a password, at least for me and from GitHub.
Is anyone also getting the same message when trying to download the "nightly build" now?
Yeah I didn't think it was just me. I guess between the VTI thread and me adding "nightly" as version to RouterOS Schema — Side-by-Side Diff, the transparency was too much for MikroTik.
IDK if a permanent thing or temporary. I guess we're back to guessing.
NOTICE:
I'm temporarily lifting the voluntary ban, because this deserves a response,
not just a like + / - or a heart... (the only things you can do while banned).
It was a fairly private thing, only a few used it, and MikroTik tolerated it.
Then the unjustified ABUSE, including polluting posts from other builds with features in the Night Build,
led to everything being locked down.
As usual ABUSE, like the Schema, of something tolerated leads to a countermeasure.
This does NOT mean I agree with what MikroTik did,
nor do I agree with the concept of ABUSE they applied.
I'm very disappointed.
BUT I expected it.
By constantly pestering them with Night Builds, criticizing them, requesting them to release it every night,
analyzing them, etc., I was sure they'd shut them down sooner or later.
It just proves a truth about life: Give somebody an inch and they'll take a yard.
Same in Italian: (literally translated from the proverb)
"If you give them a finger, they'll take your whole arm..."
Polish version is the same as Italian one. Probably the Queen Bona Sforza brought it to Poland (just speculating).
The Lord gave, and now he has taken away. May his name be praised! (Job 3:21)
This is not a user problem, or even "too much chatter" This a process and communication problem with MikroTik. If they don't want to publish nightly builds for publish, okay... but don't offer them and change it without a word. And same could be said about WinBox3 and 7.25, they never said "WinBox3 will no longer work past 7.x" although certainly one could infer that at some point that be true..
This kinda stuff should only be on some web page or even social platform someplace. But you need to have a coherent policy/process behind it, which MikroTik is lacking.
This.
Isn't it so, that the folder's original purpose was to give people who submitted support tickets a place to get test versions with the bug fixes to their issues? They were not supposed to leak the link but it ends up on the forum and known to everyone.
Ah, so it was @normis himself.
Some links from support are direct to a custom build, that is different.
But I knew @normis published the link from mt.lv that redirects... so I figured it wasn't a secret. And, given a few folks post comments about nightly build, with same link... I figured if it was sensitive, it be removed from forum.
They're probably celebrating (the dead of WinBox 3, or the betrayal of all the faithful users of RouterBOARD devices for decades),
and no one has updated the link with the new build, which hasn't been made yet.
Sharing expired, and the link asks for a password.
Just wait Monday (or the next Monday) until someone return...
Fantasy or reality? Who knows...
It's time to go back. Have a nice day...
Yup. Equally easy to imagine that it is a manual process to update the link/box.com that someone forgot on Friday. 
And an optimistic view MikroTik is actually trying to rationalize the package channels.
Currently 7.*rc goes to "testing", while 7.*beta is on "development". So one can imagine that next "alpha"/_ab becomes development once a "rc" has been declared. And that there are no "alpha" build in development if there is an active "beta". And, to be complete, that a patch to stable is pending, it go to "testing" as 7.23.4rc, if an next release "rc" was not already in progress. This fully use the channels so that you have consistent range from "long-term" to "development" without needing box.com/"nightly-build". Historically for 7.x all beta and rc went to "testing" and development was not used..
And again I suggest...
Use device-mode in favor of it!
Install RC or Dev channels its just to those who are aware of what can happen.
Put a lock to RC and DEV based on Device-Mode.
If something stupidly wrong happens using that versions...
It means that the stupid already had explicitly agreed with the possibility of that stupidity.
Hi Guys!
Just to clarify the confusion.
It was a deliberate decision to limit access to nightly builds, as they may contain dangerous, untested stuff and so on. Now, ab versions of RouterOS are provided on a case-by-case basis if a user would like to test a fix early on their system.
I understand that this might be frustrating, but unfortunately, that is the way it is.
Please...
Implement to allow the use of "testing" and "development" channels only if this is enabled on "device-mode".
And with that avoid that kind of pain with unadvised users.
"Hi, thanks for your support ticket. Do you want to test potentially dangerous and untested stuff?"
I usually reply "thanks, I'll wait for the next public release containing the fix."