

I don’t know what google keep is and I’m too lazy to look up proprietary software while browsing this community.


I don’t know what google keep is and I’m too lazy to look up proprietary software while browsing this community.
Hahah, had the same experience. What a prick that dude.


Maybe change your situation.


The roadmap defines 3 milestone batteries. The first is released, it’s a benchtop device that you can relatively easily build on your own. It has an electrode side of 2 x 2cm2. It does not store any significant amount of energy. The second one is being developed right now, it has a cell the size of a small 3d printer bed (20x20cm) and will also not store practical amounts of energy. It will hopefully prove though that they are on the right track and that they can scale it up. The third battery only will store significant amounts of energy but in only due end of the year (probably later).
Current Vanadium systems cost approx. 300-600$/kWh according to some random website I found. The goal of this project is to spread the knowledge about Redox Flow Batteries and in the medium term only make them commercially viable.
The aniolyth and catholyth are based on the Zink-Iodine system in an aqueous solution. There are a bunch of other systems though, each with their trade offs. The anode and cathode are both graphite felt in the case of the dev kit.


Don’t recommend using FTP. It’s a shitty old protocol that needs to die. Just use nginx or apache with directory listing enabled.


Just came here to say that the guy looks like a creep!


You could upload content to make it better !
No, I rarely read the code of software I use, especially crypto code since thant’s not my thing. But good to know that you did. Thanks for your opinion.
Please tell us more about the actual security problems!


Just do it!


Agreed!


Be sure to use a passphrase


I don’t agree about the point concerning cost. You have additional training, update, maintenance and config burden. This on top of the burdon of using the VPN on top of ssh.


Ok, fair point. But why stop at one vpn? I choose to trust OpenSSH, but I agree that adding a secondary layer of security actually helps here. You basically multiply two very low probabilities to get an even lower one. The trade-off is that you add complexity. You now need to keep two services up to date, and correctly configured and access/key material distributed.
I’d only recommend this setup for projects with special security requirements.


And why exactly is that more secure?


Welcome to the internet! Your system will get probed. Make sure you run as little as possible services on open ports and only high quality ones such as OpenSSH. Don’t freak out because of your logs. You’re fine as long as your system is up to date and password login disabled! Don’t listen to the fail2ban or VPN crowd. Those are only snake oil.
A VPN is probably just as (in)secure as OpenSSH. There is no gain in complicating things. OpenSSH is probably one of the most well tested code for security around.


Public ssh is completely fine as long as you use key based auth only and keep your sshd up to date. Stop spreading bullshit.
Welcome to the internet. You will be probed. Just as your immune system, or rather your body, is being probed.
Thanks for taking the time to explain and sorry for the slightly aggressive tone.