Herbert

Thanks v77 for your remarks on this. A lot of installers for example extract themself into a temporary folder. Some of those can be as large as several gigabytes. Also if you extract zip files, etc. This is just super wastefull usage of limited write cycles of a SSD. If you are not an entitled rich kid like other people who just buy insame amount of RAM, you probably won't have enogh RAM to savely put the temp folder in there (because there is no guranatee about the maximum file size) and this feature...

So in your opinion, you would then just not use the RAM disk for use cases where very seldomly the limit of the RAM is exceeded. (or where no limit can be guaranteed) In my example case I assume that 99% of the data written is in the first 10GB range and only 1% or so exceeds that limit. By just dismissing this idea you would end up using less RAM disk than with my proposal where I open the concept of RAM disk to whole new use cases that were not possible before. Just think about it. I have thought...

So in your opinion, you would then just not use the RAM disk for use cases where very seldomly the limit of the RAM is exceeded. (or where no limit can be guaranteed) Then you would end up using less RAM disk than with my proposal where I open the concept of RAM disk to whole new use cases that were not possible before. Just think about it. I have thought about page file earlier, but the problem is that all content is affected by swapping not just the RAM disk so you would potentially slow down the...

Hi, I recently had an idea that could make RAM disks more usable for a temp folder. The problem with temp folders is you never know how many space is needed. Let's say you have 16GB RAM, but there is some stupid application that writes 18 GB of temp data. Then this application would crash or whatever. And this possibility prevents people from actually using a RAM disk for temp folders. So my idea would be the following: Extend the partition, if necessary, to a local hard drive, once a limit is reached....

Hi, I recently had an idea that could make RAM disks more usable for a temo folder. The problem with temp folders is you never know how many space is needed. Let's say you have 16GB RAM, but there is some stupid application that writes 18 GB of temp data. Then this application would crash or whatever. And this possibility prevents people from actually using a RAM disk for temp folders. So my idea would be the following: Extend the partition, if necessary, to a local hard drive, once a limit is reached....

Support for the Autocrypt header would be nice: https://autocrypt.readthedocs.io/en/latest/ It does automatic key exchange and could make setting up encryption for less advances users easier. Also it adds compatibility to clients that already use Autocrypt.

To workaround some issues for the use case described here, I had the idea that you could add an option "Export keys unencrypted", where the keys are exported without password protection, but the password protection stays intact for the keys in my database.

To woraround some issues for the use case described here, I had the idea that you could add an option "Export keys unencrypted", where the keys are exported without password protection, but the password protection stays intact for the keys in my database.