Re: payswarm, webid and javascript SSL.

If you can, put up your code on some open source repository: github, mercurial or such, and make the licence clear. That
will make it easier for people to help you out and contribute.

Henry

On 26 Apr 2011, at 07:15, peter williams wrote:

> Having dominated what I need to know to applying WIF and modern websso on windows and .NET 4.0 (and doing webid helped force the issues on certs, consuming sparql, working with naming authority), I think I will move on in terms of coding. The platform is stuck on 2000 era SSL, and is resisting innovation with SSL. I need source (and GNUTLS is not mature enough for my needs).
>  
> If anyone is interested in classical webid work, one might look further at http://identity.thinktecture.com/stsce/docs/configuration/userMappings.config.htm. Its an STS, with openid bridge, that does client certs for https too, and addresses identity delegation. Sounds like a great platform on which to build a more advanced webid prototype looking at the more involved flows, including authorization lookups.
>  
> Im going to have a look at the micro-payments world again, assuming the semantic web added something to the work done in 2001/2002 type period. This will hopefully enable me to at least get the tool skills to build that javascript ssl client library, and see how it can fit into the usual windows eco-system of tools and cloud, etc. Hopefully, this can add something to the final phase of this incubator, as it rounds out its “applicability and uses” type of considerations. Getting a real client in javascript, with a UI and trust stores built using javascript (not browser vendors) sounds like nirvana!

Social Web Architect
http://bblfish.net/