3 ms·
Btw, "OFF SWITCH" is fundamentally incompatible with IPFS. If you serve your website from IPFS, the first visitor will get the full copy and start serving it.
by theamk 7y ago
Btw, "OFF SWITCH" is fundamentally incompatible with IPFS.
If you serve your website from IPFS, the first visitor will get the full copy and start serving it. You can toggle your switch as much as you want, this won't have any effect.
It's funny that Facebook is much better at giving control to user than email. At least in Facebook, you can delete post. And once you send email, there is no way to retract it.
- fit2rule 7y agoSo, I don't put anything on IPFS that I don't want to be able to turn off. Things I want to be able to turn off, I leave on my local machine, and when it is off, things are off. The point is that the OS UI should accommodate this use case just fine. Facebook/Email: and again - this is a UI problem, not a transport one. If I send a mail saying 'delete the last message I just sent', the UI can do that for me. Its a UI feature, not a bug.
- TeMPOraL 7y ago> It's funny that Facebook is much better at giving control to user than email. At least in Facebook, you can delete post. And once you send email, there is no way to retract it. This is hitting straight into data ownership question. As a sender, I might want the ability to retract a message I sent. As a receiver, however, I do not want the sender to have that ability. Once a message reaches my inbox, I want to own it. I'm strongly on the receiver side on this one. This is how it works in meatspace - once you send a message, you can't unsend it; it belongs to the transport layer and then to the receiver.