hyperfekt

Unless civet's compiled output is hard to read you could always just check in the compiled Typescript source and continue from there if it gets abandoned. Not much of a risk when the migration is built in by the way the tool works in normal use.

There's plenty to criticize about Protonmail but this article is sensationalist bullshit. I'm surprised the HN population is letting itself be goaded like this.

You should make this much more clear. There seems to be absolutely no indication on this page that this isn't officially endorsed content.

There is a vast number of search engines that are not Google, many of whom 'respect privacy' in some way. That does not make them noteworthy.

None I've encountered so far are actually good enough to compete. This one doesn't seem any different.

I'd like to posit that getting rewarded for forwarding traffic in combination with the lack of maintenance over the node list makes Sybil attacks on this network the default instead of just a concern.

IMHO your editor should be formatting your Lisp with this kind of indentation anyway, parentheses or not. If you have that, Z-expressions seem kinda moot.

Not only this, but the article also doesn't even mention transaction fees to rule out that they may offset a lacking mining reward.

'unique' indeed. this is a curiosity at best, recognizing odors is not what i would call an essential skill anymore.

Depending what core that is, you get more on the Google Cloud free tier (600MB RAM, 30GB disk). But: only 30GB outgoing bandwidth.

oh no

This screams survivorship bias so loud it hurts my ears.

What kind of account do you keep $35B dollars in?

As far as I am aware from the last time I tried to find such a thing the packet-based interactive nature of modern display standards prevents the cheap implementation of these devices, as opposed to the non-interactive, older standards.

Very interesting! Too bad this is only for finding instruction materials. An even bigger problem than finding learning materials I often have when autodidactically diving into a new topic is having to build a concept map, which is always extremely hard.

The assumption is that the encryption can only be broken via an evil-maid attack.

If you are victim of such an attack, the encryption of the file is broken as well.

Being incompatible with most available software is not a 'non issue'.

The problem won't solve itself by adoption if it never gets to that point, that's almost a perfect catch-22.

That definitely is the first thing that comes to mind, but applications need to be built under that model.

Currently all applications assume they get access to everything by default, so even if one was to be able to implement a confirmation dialog, the user would be victim to a battery of requests.

This is not to mention that isolation excludes discoverability, so users would have to manually make files visible to other applications beforehand.

I'm running Qubes 3.2 on my laptop right now (Dell Latitude E5470) and it also fulfills all the requirements to run 4.0.

The certification requirements are higher, but that's basically if people want to stick the Qubes-certified label on their devices, signaling to customers that it measures up to the highest standards of security.

They're not necessary to run Qubes, they're just ideal.

What a coincidence. I've actually been trying to sketch out how to do this in the past few days.

I've also been looking at how projects like Hypercontainer and Clear Containers achieve minimal VM overhead to expand the model to a per-application-instance VM.

Another interesting enabling technology is VirtFS, which can be used for filesystem-level storage virtualization to gain the many benefits of COW and shared caching.

The principal question then is how to allow interaction between different application instances without the user having to manually ferry files between them, as it currently happens with AppVMs on Qubes.

For anyone interested in implementations of the Sieve of Erastothenes, here is a very interesting paper about functional ones, which are harder than they appear at first: https://www.cs.hmc.edu/~oneill/papers/Sieve-JFP.pdf

I was surprised he managed to snag it. At the current rate of ICO proliferation I expected there to be at least two dozen waste reusal coins already.

This is probably done just for the election, and it's not clear whether the ban will hold in front of courts.

linksunten.indymedia is not actually a club, as which it was forbidden, nor did they publish the contents themselves. As such, they should be subject to the 'Telemediengesetz' just like e.g. Facebook and sued on this basis.

I've taken a long look at COW filesystems in these past days as part of me wanting to set up a new workstation, and it appears that while btrfs is not a viable long-term solution for its quality issues and lack of development, ZFS does not have the pretense of being a filesystem for the general usecase, as exemplified by the lack of offline deduplication, defragmentation, the possibility to easily change disk configurations, and much more. Maybe we should consider accelerating the development of bcachefs as the future of reliable and feature-rich filesystems on Linux, which appears both more modern and holistic, but still has quite some ways to go. A new filesystem is necessary because many things we should demand from them are not modularly composable without massive disadvantages. Implementing compression as a layer, for example, demands basically creating another filesystem to manage the space, with great overhead in all dimensions. Similar things go for the consistency guarantees provided by COW or the deduplication and snapshotting that depends on it.

Am I mistaken to think that the HKPKP attacks could be mitigated to a certain degree by implementing delayed pinning - meaning a pin must be announced for a certain amount of time before it goes into effect, allowing the owner to notice and counteract a malicious pinning.

This would be neat, but isn't radical enough yet IMHO. If everything on the system is composed of pure functions operating on data, we can supercharge the OS and make everything both possible AND very simple. The whole notion of 'application' is really kind of outmoded.