hackcoughgasp

5 ms·

1.
by hackcoughgasp 6mo ago
I don't remember the names, but there were client programs designed to dial up, download pre-specified content, and disconnect, to minimize phone charges. My favorite client program (not an automated one) at the time was QModem (from
2.
by hackcoughgasp 1y ago
>>"outdated certificate data" would be domains you no longer control. Or certificates which were revoked
3.
by hackcoughgasp 1y ago
I know this thread is over, but it's important to understand that it's the browsers who have all the power in CABF and they were the drivers behind this change. Apple proposed it and Google voted yes within minutes of the voting
4.
by hackcoughgasp 1y ago
Certificate pinning is suicide in an environment where certificates expire in max 47 days. You'll have to rebuild and push your app at least that often and probably sync your devops with your certificate management.
5.
by hackcoughgasp 2y ago
I was a happy customer of The Forbin Project. QModem was a great product. It's probably hard for younger people to appreciate how important terminal software once was.
6.
by hackcoughgasp 8y ago
If you're going to argue that implementation difficulties make DNSSEC too much trouble I can respect the argument. To say that it doesn't solve a problem worth solving is strange.
7.
by hackcoughgasp 8y ago
They are definitely counter to Apple's interest, but Apple is slowly pushing Webkit along anyway. See caniuse.com. You'd think the same about Google, but as I say in the article (I'm the author) PWAs are happening because Goo
8.
by hackcoughgasp 11y ago
The standards are still young and implementation is spotty. Several years from now the things that you can't do in a web app will be few.
9.
by hackcoughgasp 11y ago
I'm the author of the article and I'd like to thank Nolan one more time. He really helped me to understand a lot about this. The storage issue is this: If you install a native app, the code is there on your device, the entire prog