That does not look like a molotov.
pcn
joined 2 years ago
Some compliance measures (PCI DSS 4, HIPAA) mandate encryption in transit and none penalize it, so making any of that easier and less error-prone seems like a step in the right direction.
I'm not windows expert, but as far as I know, the way to get snapshots on NTFS is via VSS, which is usually going to work by making a block level snapshot that can be mounted independently and used read only. I don't believe NTFS was designed or has been updated to implement the kind of filesystem features that I was describing.
And yes, NTFS is usually slower at a lot of day to day things. It's very sophisticated in some respects, but it's traditionally not strong at dealing with lots of small file operations across lots of files, something that Linux filesystems tend to be good at, especially as e.g. got was written to support kernel development and if there is something that would speed up git that required a filesystem change due to git showing a performance weakness, well, I believe that had precedent
Filesystems are either pretty simple or really complex. The old dos FAT filesystem just overwrote the first character of a file name with an omega, and so usually you could just undelete by having a utility that would change the name back, as long as nothing used the blocks.
Modern filesystems are an absolute wonder of spinning wheels inside of spinning wheels allocating ranges of blocks, and then doing bookkeeping to reorganize linked data structures as fast as an SSD can write or as efficiently as possible on spinning rust.
Some log structured filesystems can do special snapshotting either automatically like NetApp ontap or manually like zfs so that when you take a snapshot any further changes preserve a view of that snapshot at a point in time that you can treat like a special directory where you can cd to and copy back out data as it was as long as you have space. Windows supports this kind of functionality with the VSS API if the underlying FS tech supports it.
The downside to these approaches is that they tend to cause fragmentation, can cause a lot of extra space to be used (after all, if you delete a tb, it may be because you meant to and you needed to, so if you mean it, why hasn't it gone away, etc.,) and are a lot of complexity that 99% of the time 99% of the people don't want to think about it or pay for it (pay as in it's slower, uses more space, the complexity leads to more failure modes, etc )
Yeah, this is complete bullshit. Every bathroom in every home in Brazil has a spray nozzle, at least, to rinse off one's dirty bum.
We'll it hasn't killed the owner, neighbors, or any nearby ducks. Yet.
If you think about it, preserving rain forests is free! Reforesting them only requires a few dedicated people, some seeds, and some time. The hard part is stopping people from fucking them up to make such small amounts of money.
I couldn't use the current alpha as a daily driver because I didn't see a supported/intended way to manage starting and maintaining my ssh-agent upon login. Besides that, it felt good enough that I'd use it for more than a few days if I could.
A 65w or so PD supply works fine for driving dual 4k monitors and general programming etc. You only need the 180watt+ for using the external gpu
Keepass2android works pretty well. I'm not sure for iPhones