judas_iscariote

There isn't much to be said right now, as far as I 'm aware the app will continue to get bugfixes, I'm not sure if new features are indeed planned for soon.

I'm afraid this was not tested ever nor it will be unless microsoft adds ReFS again to the mainstream windows releases.

You could try to run on WINE, but I do not think it will work fine. try k3b, brasero etc..

the daily snapshot process has resumed, new builds will however be available later, right now only the last successful build is available, dated March 24 2019.

How much build power do you need and how much electricity was it estimated to cost ? @floele

If you burned an audio disc the format must be the standard understood by CD players. If what you wanted was to burn the flac files you need to create a data cd

Thanks but there is no hardware shortage, . it is just that the machine that does all the automated building (not the one that serves the content) has not pushed builds out due to a defect that needs developer time to fix. @floele is the only person with the relevant knowledge and he is almost certainly beyond busy atm.

No. Create a bitlocker encrypted file container and burn it later, You can also use Veracrypt IIRC. I wouldn't trust anything else to do things correctly and safely.

If the source file really does not fit the media you have to split the content with an audio editor such as audacity and burn the result into two discs.

The server that actually does the daily snapshot magic is dead, so there is no content in the machine that just serves it. this will be fixed at some point.

No such thing as secure erase for a well funded adversary, use some kind of media destruction, incineration, shredding or whatever other creative way to ensure no data can be ever retrieved.

Your account will be deleted shortly, if you do not wish to trust us with extra information, use one of the single sign on options at a later time. Cheers. BTW..We do absolutely nothing with the user data on this forum.

Please ensure all your installed .NET versions support and have enabled strong crypto, Some versions do not. Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord In an elevated powershell, reboot.

Interesting.. just wondering.. do you have any special SSL/TLS configuration on your system ? peraphs TLS 1.2 was disabled by mistake or purposefully by policy? Our systems no longer support TLS < 1.2 and that may be the reason it is failing.

No, There is no MacOS X version available and it is unlikely it will ever be.