I write business letters in HTML. I have a custom letter.css and a base letter.html+.js that loads individual letters into a template. I have some custom tags for date, address and similar. The individual docs are super clean. I can export compiled html files with embedded css (no js needed) and images that render perfectly and are even smaller then the pdfs I export (print) and those are small too.

Two downsides. The biggest problem, I didn’t find a way to do proper multi page docs. And especially Firefox has limited print css support.

Second: everything is crudely hacked together and in no way usable by others…

maybe chatgpt can rewrite the code better, so I can publish it?

I know million dollar machines that ship without MS office, but with Openoffice (!). The problem is, the Software can copy graphs to the clipboard in WMF (or something like that) that neither the super old Openoffice nor a recent Libreoffice can import. So wordpad is the only ootb software able to use the data.

Their reason is that 90% of their customers have an office subscription anyways…

Certificate 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 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…

Imo the most important thing is the separation of what you do. If you’re logged in on facebook, you can do that from your public ip. Anything you’re not associated with your name you want to use a diffferent browser identity and maybe a different ip.

If you use Torrents or do anything illegal or whistleblowing or similar stuff, use a live linux iso with no persistence and a vpn bought with monero.

Ok, but how does the password file get compromised but the 2FA file not? Why not have a separate password file for every login with a different password then?