You're welcome! It's great to have you on board, every new .bit site counts! And clipperz is a prime candidate, IMHO.
Have you tried "compiling" FreeSpeechMe yourself (actually just assembling the .xpi file) and using a separate namecoind process? I have no idea about how things work on Mac, but maybe this works. (I don't know whether there are fundamental problems with Convergence and Firefox on Mac. Could be, but I doubt it.)
Setting up SSL for clipperz.bit
Re: Setting up SSL for clipperz.bit
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Setting up SSL for clipperz.bit
The issues on Mac are caused by a bug in upstream Convergence; it's not any of my code. If anyone knows exactly what section of the Convergence code is causing the issue, feel free to make a GitHub ticket. If not, I'll investigate myself when I have some time.domob wrote:You're welcome! It's great to have you on board, every new .bit site counts! And clipperz is a prime candidate, IMHO.
Have you tried "compiling" FreeSpeechMe yourself (actually just assembling the .xpi file) and using a separate namecoind process? I have no idea about how things work on Mac, but maybe this works. (I don't know whether there are fundamental problems with Convergence and Firefox on Mac. Could be, but I doubt it.)