Masella: That’s not part of OAuth, mind you, it’s part of what the oauth provider asks the user to do while negotiating/authenticating the user
Rowlison: I’m trying to accomplish this: when the user is authenticated somehow, i need the script tag the blog placed on their site to make a post request on behalf of the user
Berum: It contains a data tag the blog placed on their site
Loeza: Can’t wait to start using sum es6 in njs4
Meneus: Vioz: that will probably require some kind of oauth negotiation, then, yes
Cane: How can get a variable value to be interpreted within a regex definition?
Meneus: Snockerton: use a constructor instead of the regexp literal notation
Lader: I.e. var1 = “abc”, regex = /.*var1…/g
Drozdowski: I guess i need to deep dive into oauth and figure things out
Deters: I think regex is of type regex though
Balle: Like it doesn’t turn into a basic string
Masella: Snockerton: you have to use new RegExp str + ‘.’ + strn
Lagueux: Guess i’ll need to use open id connect
Meneus: Var value = ‘ohai’; var reg = new RegExp’.*’ + value, ‘g’; reg.exec’abcd ohai’
Konopacki: Meneus: object ‘abcd ohai’
Masella: Vioz: openid is different from oauth
Moras: Iirc, it’s an authentication layer on top of oauth 2.0
Meneus: Var value = ‘ohai’; var reg = new RegExp’.*’ + value, ‘g’; reg.exec’abcd oha’
Chery: Meneus: o i didn’t try building it inside a RegExp block yet
Masella: Vioz: oh. wow. openid has fallen then.
Meneus: Snockerton: they’re two different things. /foo/ is one way to make a regexp, using the literal notation. new RegExp’foo’ is another, using the constructor
Konopacki: Snockerton: RegExp – JavaScript MDN https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp
Saballos: Right i see that now as I do a print on the RegExp variable, it dumps out the literal format
Meneus: Basically, you can store the actual regexp stuff in strings and then build it using the constructor
Meneus: It prints it in regexp format because that’s how toString works on regexp
Blazich: In node.js, what is the best practice for requiring modules nested within multiple directories? for example, can i use var connection.foo = require’./connection/foo’;?
Meneus: Xnil: best practice is to just require what you need directly. There IS a require-dir module on NPM you can use to require a whole directory structure but it’s best not to use in production applications
Boahn: Joepie91_: Are you there?
Boahn: Joepie91_: I talked to you before? About errors module?
Boahn: Joepie91_: Sorry, wrong channel
Lantelme: Ok, got a question that i’ve not been able to find a proper answer on the interwebs.
Escott: I have a select list, and the options have their values. i need them to have two values or a name and a value, one is the actual name that is p***ed to my save function so it saves it as that file name, the other is a URL
Niemeyer: The URL needs to be p***ed to a function that converts images to base64 via a URL because the images will not be local on my server
Romanchuk: Fairly novice at JS, but i can get around
Gull: PatrickC: you need to combine two values into one
Gull: That could be as simple as concatenating them with another character in between
Gull: Or you could use a more cmoplex format such as JSON
Hosner: Gull: http://hastebin.com/egomocokuk.xml
Ruballos: This is how i’m currently doing it
Nancy: I have the option with a value, the value corresponds to an if/else statement, and inside the if/else statement it has the value of the base64
Hoeller: PatrickC i want to be able to specify two things for the option one is a size identifier, this will never ever change. they’ll always be 1080, 1920, 1440, etc