Logarbo: Dash: why aren’t channels a good fit for languages with mutable state?
Zarilla: Code monkey like fritos, code monkey like Tab and Mtn Dew
Meneus: Hendershott: https://github.com/jlongster/transducers.js/pull/38 – fixed it ***uming it’s accepted so .iterator and .toIter iterators will work with for.of, yield*, and other things that accept iterators Array.from, new Map, etc. They’ll also wrap any non-compliant iterators with ones that do the same
Kopecky: I thought that lib already has iterator support though
Meneus: It does. not including the protocol on returned iterators was basically an oversight
Urtiaga: Im like 42% sure I had user an iterator with those transducers
Meneus: It takes iterators and returns them, the returned ones just didn’t have the self-returning Symbol.iterator method on them, so they wouldn’t work with anything that expects an iterable
Meneus: Mostly I’m just happy to contribute in a small way to one of my favorite libs
Biringer: Im glad his lib didn’t get smoked by the clojure port
Meneus: Hehe yeah. I think it’s because his is a lot lighter-weight while also having convenience functions the port doesn’t
Kaeo: If anyone has time to take a look at this, i would appreciate your input: https://stackoverflow.com/questions/32466868/how-does-disqus-authentication-work
Meneus: Vioz: the answer is in the doc you link – they use OAuth2 and/or Single Sign On
Masella: Vioz: the client grabs the disqus code from the disqus server so your client sends the disqus cookies
Masella: The SSO they’re referring to there is, i ***ume, how you log in to the current website but then get authenticated and authorized to use the disqus
Labrada: Meneus: wouldn’t that involve cookies?
Masella: From the doc you linked: “cookies are required to keep you logged in between pages in some browsers.”
Meneus: It does involve cookies, but the other domains aren’t accessing them directly
Baller: Masella: if they are using cookies, how are they sending disquss cookies? if you visit a site for the first time, you won’t have cookies to send, right?
Masella: 17:11:00 Masella vioz: the client grabs the disqus code from the disqus server so your client sends the disqus cookies
Bobrowski: Cookies you throw really far
Masella: Vioz: if your browser makes any request to the disqus server, it sends the disqus cookies
Ormond: You don’t even need oauth to do that
Meneus: Yeah, oauth is so you can sign into a third party site using your foo credentials
Meneus: Sorry, didn’t mean to confuse the issue
Masella: Right. oauth is so disqus can ask example.com the site using disqus who you are
Beauparlant: I don’t really see the point of oauth
Overgaard: He just told you the point lol
Pullman: Just because the script is on a different domain doesn’t mean your browser will send cookies ***ociated with that domain, it’s the domain you are POSTing to
Masella: It’s so you can use your own site’s authentication who are you? to authorize what can you do? the use of disqus
Masella: No, it absolutely does. cookies are sent based on the domain being connected to and the path, and ssl mode
Masella: If you go to google.com, you don’t send cookies from yahoo.com, you send the ones you got from google.com. otherwise, how would cookies work at all?
Presta: Does disqus really need to ask example.com to who i am? can’t they determine this based on the token in the cookie?
Masella: If example.com wants to use their own authentication, then that is what they will set up
Masella: So if you already have an account with example.com, how then can you use disqus on example.com? how will example.com know who you are when you’re commenting?
Turnner: Masella: wait, you’re saying that if i visit google.com but i POST to yahoo.com, i will be sending google cookies and not yahoo cookies?
Masella: No. you’re connecting to yahoo to send the post, so you send yahoo cookies