#hackedu

Zrl: haven't gotten invite

mmmm, my bad this calendar invite hasn't been updated with invites

the presidio

first floor

so this is a thing from the session: https://imgur.com/gallery/M0NIC

zrl,jonl : heading out

👍 maxw

thethirdone: ready to chat with you are! http://partytime.jonl.org ?

actually 1 sec

1 minute bathroom break lol

jonl: i just realized something I overlooked

thethirdone: shoot!

Twilio.recieveCall needs the specific number in the request

jonl: that was part of why Twilio.recieveSms also had it

Is it worth it to have different arguments?

jonl: twillio doesn't support mms on my carrier

Twilio.recieveCallsFrom("Twilio-number", fn) yeah?

thethirdone:

What do you mean by different arguments?

Twilio.recieveSms("twilio-number",callback) vs Twilio.recieveSms("twilio-number","human-number",callback)

jonl: the 2nd is pretty much neccesary due to how twilio handles calls

Wait, I don't think it is, I've implemented it without that before?

I am out now

Will answer tmr?

jonl: there are some weird things about the call api due to the facts that 1) An old callback should not block a new one from being activated, 2) only one callback can be activated per call, 3) Deciding which callback to take must be done server-side

I can hop on a call with you to discuss it if you want

thethirdone: I'll be in the office in 3ish hours, a brief call sounds good

Maxw I'll be in the office in 3ish hours, primarily going to be doing reflection work first

1pm. Got it

jonl: partytime.hackedu.us

thethirdone: give me one sec

Gonna write some stuff up briefly

srue

sure*

ok, i'm opening up partytime.hackedu.us

jonl: do you think each callback should overwrite the last one rather than work only once and separate call so it wont interefere?

zrl: are we good on https://github.com/hackedu/maestro/pull/18

maxw https://scratch.hackedu.us/p/c2w1d6

thethirdone: sorry, can you clarify "rather than work only once and separate call so it wont interefere"

currently each callback lives for one call

and by "separate call so it wont interefere" I meant to make Twilio.call use a separate webhook so normal callbacks aren't messed with.

ie. Twilio.listenCall() uses /baton/Twilio/call/inbound and Twilio.call() uses /baton/call/outbound

jonl: ping

thethirdone: yeah, separate callbacks seem like a good idea

thethirdone: mutexes seem like the best currently but

mutexes > overriding > single use callbacks

jonl: mutexes are probably unimportant if multiple users dont try to use the same number

thethirdone: good call

OOH

gotcha

thethirdone: I think that blocking a new callback from being established should be the precedent "you already have another place in the code where you are listening for this, you have to close that one before listening for it somewhre else"

thethirdone: thoughts?

thethirdone: convert "should" to "potentially could"

jonl: the idea of closing a callback is somewhat tricky, I might be able to make something on the client that would check to see if a callback has already been made that would console.warn("This number already has a callback, check yourself")

thethirdone: sounds good

thethirdone: even beyond console, I'd throw an error

I did not know console.warn was a thing, tanks!

jonl: I would not throw an error

thethirdone: sry, I'm terrible at communication

thethirdone: "what are your thoughts on throwing an error?"

is what I meant to say

jonl: it would be potentially annoying to refresh the page to be able to overwrite a callback for testing

thethirdone: sounds good

maxw, this is kinda cool https://www.khanacademy.org/partner-content/ssf...

jonl: Those are the current commands; are there any you want me to rename/add/remove?