@Mike1576218
@lemmy.mlCertificate pinning?
Also all let's encrypt certs are public. So if someone malicious gets a cert for your domain, you can notice.
(Thats also why it may be a bad idea to use that for secretButPublicStuff.Yourdomain.com certificate transparency logs are a great way to find attack surface.)
edit oh certificate pinning has been deprecated in favor of checking transparency logs.
It is not bad per se. It should be the goal of every government to make all people fat and happy. The problem is, it is enough to only make >50% happy.
Note: every file on Ipfs is unencrypted and semi-public unless you encrypt before upload.
It is not a problem to distribute the decryption algorithm. The question remains against what this will protect. Normal https encrypts the traffic safely during transit. With this, the data is also encrypted on the server. But if you can access the server, you can modify the javascript code to send the password back to a server.
It could be used on something like IPFS, where all data is basically public but you can be sure it hasn't been modified.
Aren't all (most?) those centralized services? What good is having the app if the service is unavailable? Tox, Jamie and Veilidchat are fully decentralized, not just federated, fully decentralized. They come with their own downsides though...
I also didn't like AitD. The tank controls, static "3D" screens where you overlooked something if you didn't walk into every corner and a new screen presented itself... Oh wait, you're talking about a remaster? I'm talking about the original...
Myst.
I came for the graphics and because I liked adventuers. Was disappointed by the static graphics and I didn't understand what to do at all.
I still sometimes have a similar problem. Where I do something small with python, call it "serial.py", first line "import serial"...
No wonder. That file is super slow to transfer for some reason. but wait till you get to /dev/urandom. That file hat TBs to transfer at whatever pipe you can throw at it...