Hi, I am looking into OAuth. I see (and thank you a lot for this!) that Chriss Ross Gill created OAuth client part in the twitter library: http://reb4.me/r/twitter.html , I am reading into it, but does he or anyone else know how much additional work would be needed to do the rebol OAuth server part ?
I don't think it'd be that difficult - most of the difficulty in the client was making sure all the hashing was correct, the rest is just storage and logic.
For the most part, authorisation is based the parameters of a request hashed with a private key. The trickiest part I'd imagine is the initial authentication - providing a safe method for the end user to allow the client to obtain and use the key.
End user downloads X's app/uses your
End user X downloads Y's app/uses Y's web site; X tries to access a function that uses your site; Y requests a temp key from you; Y directs X to your site with temp key, X says Y is OK, you give X a PIN; X goes back to Y, enters PIN; Y requests the permanent key from you. Y can now do anything on your site on behalf of X.
Nothing to it : )
any tip for some session related function-set for REBOL CGI purposes? I am looking for the case, where Cheyenne is not an option, and need some simple stuff for sessions ....
acgiss.r from rebol.org an option?
Do we have anyone here that is knowledgeable / an expert in online markting?
I am not an expert but I have a lot of experience and also theory about various aspects of it because of making my apps grow (and helping some others)
"Is Nginx obsolete now that we have Amazon CloudFront?"
Don't quite understand what is going on here .. have to read the cloud front docs
Can you trust the cloud? Not in the sense of reliability.
I trust the clouddate being watched over, and more I trust it a 100% being watched or even analysed. Some things I just take as is without proof, like the earth to be a flat disc ;)
Yes, it's obvius. Frankly it depends on what data you want to "share". I like google documents for storing files to edit when I travel ,not very important documents. For example: if you would plan a kamikaze attack or write a personal diary on your sexual orientation, I didn't suggest you to use google documents.
Could not JS everywhere someday be replaced by Red everywhere - or some derived fork ?
Yes; they have a good model, but it's all ugly web technologies
I agree but what else could be used - something built aroud the JVM - may be ? It must be a bit like Carl's REBOL based vision, isn't it ? Entirely self contained to be deployed anywhere but written once ...