https://sxmo.org/ looks like a good way to get little Safes set up on mobile, at least for a techy crowd (who I guess we’d hope would be jumping in early)
Anonymous are literally bringing V for Vendetta to life. Putin looking likely to be toast more each day.
Maybe I’m getting caught up in wishful thinking, but…
Some papers to consider regarding Microsoft’s Github CoPilot.
Today we celebrate the Bulgarian holiday Baba Marta! Good health and love to all!
And of course don’t forget to update your Safe Calendar for the month:
Privacy. Security. Freedom
Would it be too tinfoil hat of me to bring up the subject of code backups?
For the safenetwork project, and all your own personal code too.
Given the current situation could we expect internet attacks on centralized services like github?
Would it be wise to have a weekly/monthly offline repo backups on good old fashioned CD / DVD ?
Low effort insurance to protect years of work.
I thoguht this article might be of high interest to the Safe network.
Jack Haverty: "The Internet Never Got finished"
He is one of those who participated in and developed a number of standards, such as TCP (Transmission Control Protocol), FTP (File Transfer Protocol), RFC (Request for Comment) and one of the world’s first systems for e-mail. .
When the internet became something that was to be used to connect institutions and companies outside the research world, it became urgent to make everything work, as much of the internet was based on the ARPANET of that time. According to Haverty, he and his colleagues had a long list of different things that needed to be implemented for the internet to work in an optimal way, such as that it would be possible to do troubleshooting. However, much of what was planned at the time never became part of standards such as TCP and UDP. Haverty believes that this is why we sometimes have problems when we use the internet,
Byzantine fault tolerant CRDTs (PDF):
This paper shows that the situation with BFT CRDTs is
very different from BFT consensus: it is possible to guarantee
the standard CRDT consistency properties even in systems in
which arbitrarily many nodes are Byzantine, e.g. where the
Byzantine nodes outnumber the correct nodes. This makes
the algorithms immune to Sybil attacks, allowing them to be
deployed in open P2P systems that anybody can join, without
requiring proof-of-work or proof of any other resource.
Moreover, making CRDTs Byzantine fault tolerant does
not require a redesign of the algorithms: it is possible to
retrofit BFT to existing CRDT algorithms with some modest
tweaks, without changing the fundamental way how they
work. This paper introduces the principles that are needed
to make operation-based CRDT algorithms robust against
Interesting. So even the often suggested 8 character minimum is worthless.
Yes, that’s why I use https://bitwarden.com/
Privacy. Security. Freedom
Keep in mind that this is brute force with no delay between attack. So for example, locally hacking an encrypted zip file.
For a website there are multiple delays (some deliberate to prevent ddos and password hacking) that would increase that time required very greatly.
Still always good to have the most secure password that you can in any case.
Yes, because some breaches are where they grab the files and then start processing them in parallel (multiple machines), so brute force often has to be considered for web sites. This is where the importance of using different credentials for each site is important.
This is where the Safe Network shines since there is no set of password/ID files that can be grabbed and brute force attacked. Each individual account on Safe has its own file so there is no wholesale attack on Safe Network accounts. But you still need to have solid credentials for your own account.
Yip the worlds catching up All great to see.
4 posts were merged into an existing topic: Ukraine
Some gems in here.