What fucking browser demands it twenty fucking times? My fucking Mozilla doens't fucking demand it twenty fucking times. It fucking only demands it fucking once. That's once fucking ever, not once per fucking session, let alone once per fucking page load.

I mean, fuck!

`Coz it sure doesn't do that with mine.

Thanks, I needed that. The posts of gfolkert alone are sufficient reason to frequent zIWETHEY. All else is just gravy.

Dunno where it leaves me, though. All the Freenet gateways I currently know of are https: - and rightly so. But I have a feeling they all have untrusted keys. Being a paid-up serf of the VeriSign monopoly is too much for some people. It's not so much the money that's the issue. It's a control thing.

Well. Back to square one, it seems.

The point is to prime the Freenet cache. Get pages into the gateway and keep them there, *before* someone wants to look at them, thus saving time.

But if it's going to cause this kind of trouble, it's not worth it. So I'm rethinking. I'm already moving some of that stuff onto the Web. For the rest, probably give up the banners. They were mainly there to prime the cache anyway, and that's looking like a foregone conclusion at this point.

I thought it was worth a try, but it didn't work as I had hoped. So now I gotta do some script fiddling, and they'll be gone.

If anyone wants to follow a Freenet link to a page other than mine, he'll get the untrusted certificate. I don't know any way around that, short of mirroring the entire Freenet on the Web, and that's hardly practical.

Later, I think I'll try to set up two versions, one that primes Freenet, and one that doesn't. Still further into the future: set up my own gateway, using http. Seems like a copout, though. And I don't want to be beholden to VeriSign. Would anonymous Diffie-Hellman key exchange be worthwhile?