Re: [Semanticscuttle-devel] Privatekey

[Christian W. <cw...@cw...>]

Hi Mark,


> Good idea.  Assuming disabling it at the user level, do you think
> there needs to be an option for the site to turn off/on this feature?
I don't think that's needed, given that by default nobody has private
feeds enabled.


> Question on the ajax call, would you entertain the option to do an
> ajax call if the browser has js enabled?  So code it to work both
> ways?  This might help with the other components that make ajax calls
> (i.e. voting). Thoughts?
I'm all for that. Having it working with JS is always nice; I just
don't want to exclude non-js browsers.

> To Do List:
> 1) build additional unit tests
I did some additional unittest fixes in the master branch; you might
want to merge them in your branch.

> 2) Remove ajax call for new key generation and make it POST (unless
> above is acceptable)
The REST rules state that actions that change data should never be
GET, so using POST is fine.

> 3) user option to enable/disable private key option
I think some checkbox or radio button would work here nicely:

( ) feed key: [abcde....] <regen>
(·) disable feed key

> 4) possible site option to enable/disable private key option
Ok.

> Cheers!  North Carolina weather is fantastic for February!
Have a nice weekend!


-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-