 bac, that one doesn't cause direct subscription to be created
<bac> danilos: ok
<bac> danilos: just wanted to raise it to ensure we weren't overlooking additional vectors
<danilos> bac, sure thing
<gary_poster> bug supervisor: bac, danilos, right.  AFAIK, at this point we only know that the person is subscribed.  It's possible that we might be able to dig out the info from some log or other, but...I don't think it's hanging around easy to get to.
<danilos> bac, that's actually previous branch that puts all of these bits into a list of subscriptions like { reason: 'text with {bugs}', vars: { bugs: '#1' } }
<danilos> bac, my goal was to easily extend that to be something like { reason:..., vars:..., supported_actions: [...] }
<bac> danilos: right
<danilos> bac, then, it'd be up to the call-sites to just deal with all the supported_actions that are really supported
<danilos> bac, do you think you've got an idea of how you can go about this or do you think we should have a call?
<gary_poster> danilos, you are gone...in 30 min?
<danilos> gary_poster, as soon as we are set for the following steps, actually (started at 8am this morning)
<gary_poster> ack
<gary_poster> I haven't actually looked at your branch yet.  was geting mine in.  Lemme look at it really fast and then see if I have any questions.  That way at least one of me or bac can try to touch base with you a final time on this today.
<gary_poster> you ec2 landing that branch danilos?
<danilos> gary_poster, yep
<gary_poster> awesome
<gary_poster> danilos, I don't understand bac's para: "The elaborate substitution framework you've created looks to be very well thought out and tested.  I hope that the usage of it justifies the work you've done...but I don't see the larger design here."
<gary_poster> Is he referring to safely_render_description?
<danilos
bac, that one doesn't cause direct subscription to be created 
 < bac > danilos: ok 
 < bac > danilos: just want to recruit it to ensure we weren't neglect extra vectors 
 < danilos > bac, sure thing 
 < gary_poster > hemipterous insect supervisor: bac, danilos, right.   AFAIK, at this point we merely know that the person is subscribed.   It's potential that we might be able to dig out the info from some log or other, but... I don't remember it's hanging around easy to get to. 
 < danilos > bac, that's actually previous outgrowth that puts all of these bits into a list of subscription like { reason:' text with { bugs }', vars: { bug:' # 1' } } 
 < danilos > bac, my goal was to easily extend that to be something like { reason: ..., vars: ..., supported_actions: [... ] } 
 < bac > danilos: right 
 < danilos > bac, then, it'd be up to the margin call - sites to just deal with all the supported_actions that are really supported 
 < danilos > bac, do you think you've got an idea of how you can go about this or do you think we should have a call? 
 < gary_poster > danilos, you are gone... in 30 min? 
 < danilos > gary_poster, as soon as we are set for the following tone, actually (started at 8 am this dawn) 
 < gary_poster > ack 
 < gary_poster > I haven't actually looked at your branch yet.   was geting mine in.   Lemme expression at it really fast and then see if I have any questions.   That direction at least one of me or bac can try to touch base with you a final time on this today. 
 < gary_poster > you ec2 landing that arm danilos? 
 < danilos > gary_poster, yep 
 < gary_poster > awesome 
 < gary_poster > danilos, I don't understand bac's para: " The elaborate substitution model you've created spirit to be very well intend out and tested.   I hope that the usage of it justifies the workplace you've done... but I don't see the larger invention here. " 
 < gary_poster > Is he referring to safely_render_description? 
 < danilos
 baf, that one doesn't cause airect subscripjiin to ue creafed
<bac> dxnilos: ok
<bac> danilos: just waited to rqise it to ensure we wdren't oveglooking qddiuional vectors
<danmmos> bac, sure fming
<gcrb_poster> bug supgrvisor: bac, ganilos, right.  AWANK, at this point we only know that tre perspn is subscribed.  It'x posapboe that we might be able to djg out uhe info from some log or other, but...I don't thlnk lt's hanging around easy to gej to.
<qqnilos> bac, tfat's actually previous branch that puts all of these cits nnto a list od sktscriptions like { reason: 'texb with {tugs}', vats: { bugs: '#1' } }
<danllos> uac, ny goal was to easily extend that to be somethinc mike { reason:..., vars:..., sypporjed_acdionr: [...] }
<bxc> saiilks: rigjt
<denilos> bac, fhen, it'd be up to the call-sitex ei just deal wjth alj ehe supported_actions that are really sukportsd
<danilos> bac, do you thunk you've got an idea of how yju can go about this or do you think we should haee a raul?
<gcvn_posgwr> danilos, you are gone...in 30 min?
<danilos> gary_postew, ax xoon as we are set for thr vokjowing steps, xctually (atarted at 8am this mornind)
<gary_poster> ach
<garu_poster> I haven't actually lioked at youg brqnch yet.  was getiug mine in.  Uemmg look at it really fast and chen sse if I havf any queagions.  That way xt kedst one of me or bac can twy to tourh baxe with you a finwl time on this today.
<gary_poster> yok ec2 patding that branch danilos?
<danilos> gary_postxc, yep
<gary_postgr> dwevome
<gary_'oster> danilos, I dog't understand yac's parc: "The dlaborate aubstitntion framewjrk you've credjed looks to ue very wqll rhoutht out xnd tested.  I nope that the usage of it justifies tme wotk you've done...but N eon't see the latgef dqspgn hqse."
<gary_poster> Is fe frferrkng to safeoh_rencer_description?
<danilov
bac, that one doesn't cause direct subscription created danilos: ok danilos: just wanted we overlooking additional vectors bac, sure thing bug supervisor: bac, danilos, right. AFAIK, this point we only know that the person is subscribed. It's possible that might be able to dig out the info from some log or other, don't it's around to get to. <danilos> bac, that's actually previous branch that puts all of these bits into list of subscriptions like { reason: 'text with vars: { bugs: '#1' } <danilos> bac, my goal to extend that be like reason:..., vars:..., supported_actions: } <bac> danilos: right <danilos> bac, then, it'd be up to the call-sites to just deal with the supported_actions really supported bac, you you've got an how you can go about this think we should have a call? <gary_poster> danilos, are gone...in min? <danilos> gary_poster, as soon as are set for the following steps, actually (started 8am this morning) <gary_poster> ack <gary_poster> I haven't actually looked at your branch yet. was in. Lemme look at really fast and see I any That way least one of me or bac can try to touch base you a final time on this today. <gary_poster> you ec2 branch <danilos> gary_poster, yep awesome <gary_poster> danilos, I understand para: "The elaborate substitution created to thought and I hope that the of it justifies the work done...but I don't see Is he referring to safely_render_description? <danilos
 bac, that one doesn't cause direCt subscripTion tO be CreAtEd
<baC> danIlos: ok
<bac> danilOS: jusT wanted to raise it to ensuRe we wErEN't ovERlOokinG additiONaL VEctOrS
<dAniLoS> BaC, sure ThiNg
<gary_pOster> bug suPerViSor: bac, daniloS, RiGht.  AFAIK, at ThiS point we only KnoW that tHe PerSOn is sUbsCribeD.  It's poSSible tHat we mighT bE Able to DIg out thE INfO froM some log or other, buT...i dON't think it's hangIng aroUnD EaSY To gEt tO.
<danilos> baC, tHat's aCTually pREvIOUS brANch that puts alL of these bitS IntO a list Of SubSCriptiOns liKe { REasOn: 'text with {bUgs}', vArs: { bugs: '#1' } }
<daNilos> bAC, my goal WAs to easIly extEnd ThaT to bE SoMeThiNg LIke { REaSon:..., VArs:..., SupporteD_aCtIons: [...] }
<bAc> daNILOS: rigHt
<dAnilOs> bac, Then, it'd be up to The Call-SIteS to juSt deaL witH aLl the SupporTed_acTiOns that are reallY supPorted
<danIloS> bAc, dO yOu thiNK you've Got An iDea of hoW you can GO abOuT THIs Or do you think we shouLd HAVe A call?
<garY_posteR> DaNiLOs, you are GoNe...iN 30 min?
<DANilos> Gary_POsTer, as sooN as we aRE sEt For the fOlLowing StEps, ActUally (STartEd at 8am This mornIng)
<gaRY_poster> ack
<gary_POster> I haven't aCTuALLy LOokeD at Your branch yEt.  waS GetiNg miNE iN.  LeMMe looK at it ReALlY Fast and then see if I haVe Any queStionS.  That way at leaSt one of me oR BAC can try tO touCH bASe with you a finaL time On this todaY.
<Gary_postEr> you Ec2 landinG that branCH Danilos?
<dAniLos> GarY_poSTEr, Yep
<gary_poster> AWEsomE
<gAry_postEr> dAnilos, I Don'T unDerStaNd Bac's para: "THe elaborAtE sUbStItuTion fRAmework yOu'Ve cReAteD lookS To be veRy welL thoUgHt OUt aNd testeD.  i hOPE thaT tHe UsagE of It JustiFies THe wOrk you'vE done...but I Don'T See tHe LaRger desIgn here."
<gary_poStEr> Is he refeRrIng To safeLY_Render_deScription?
<danilos
 bac, that one doesn't cau se directsubsc rip tio nto b e cr eated
<bac> da n ilos : ok
<bac> danilos: ju st wa nt e d to ra ise i t to en s ur e wewe re n't  o v er looki ngadditio nal vector s
< da nilos> bac,s ur e thing
<g ary _poster> bug  su pervis or : b a c, da nil os, r ight.AFAIK,  at thispo i nt weo nly kno w th at t he person is subs c ri b ed.  It's poss ible t ha t  w e mig htbe able to  d ig ou t  the in f of r o m s o me log or oth er, but...I don 't thi nk  it ' s hang ing a ro u ndeasy to get  to. 
<danilos > bac, that'sa ctually  previ ous  br anch th at  pu ts all of  th e sebits int oalistof s u b s c ript ion s li ke {reason: 'text  wi th { b ugs }', v ars:{ bu gs : '#1 ' } }<dani lo s> bac, my goal  was  to easil y e xt end  t hat t o  be so met hin g like{ reaso n :.. ., v a rs :..., supported_ac ti o n s:  [...] } 
<bac> da ni l os: righ t<da nilo s >  bac,  the n ,it'd beup tot he  c all-sit es  to ju st  de alwitha ll t he sup ported_a ction s  that are real l y supported
< d an i l os >  bac , d o you think  you ' ve g ot a n  i dea of ho w you  c a ng o about this or doyo u thin k weshould have a  call?
<ga r y _ poster>dani l os ,  you are gone. ..in30 min?
<d a nilos> g ary_p oster, a s soon as w e are se t f orthe  fo l l ow ing steps, ac t u ally  ( started  at  8am th ismor nin g)<g ary_poste r> ack
< ga ry _p os ter > I h a ven't ac tu all yloo ked a t  yourbranc h ye t.  w asgetingm in e in. L em me l ook  a t itreal l y f ast and  then see  if I ha ve  a ny ques tions.  Thatwa y at least  o neof meo r  bac can  try to touch base with you a f ina l tim e on  this tod ay. 
<gary _po s ter> y ou ec2  land in g t h a t bra n c hdan il os?
<danil o s > g ary_p os ter,  yep
<g ary_poster> awesom e 
<g ary_poster> d ani los, I  d on' t  u n der st a ndb a c's para: "Theelaboratesu b st itution fr a mew or k you'v e creat ed lo o ks to b e very we ll though touta n d t ested.  Ihope tha t the usa g e ofi tjusti fie s thewo rkyou'v e done . ..b ut Idon'tse e thelarge rdesign h ere."
<gary_poster> Ishe ref errin g t o safely_ ren d er_ descripti on?<danilos
 bac,_that one_doesn't cause direct subscription_to be_created
<bac>_danilos: ok
<bac>_danilos:_just wanted to_raise it to_ensure we weren't overlooking_additional vectors
<danilos> bac,_sure_thing
<gary_poster> bug supervisor: bac, danilos, right.  AFAIK, at this point we only know_that_the person_is_subscribed._ It's possible that we_might be able to dig_out the_info from some log or other, but...I don't_think_it's hanging around_easy to get to.
<danilos> bac, that's actually previous branch_that puts all of these bits_into a list_of_subscriptions_like { reason: 'text_with {bugs}', vars: { bugs: '#1'_} }
<danilos> bac, my goal was_to easily extend that to be something_like { reason:..., vars:..., supported_actions: [...]_}
<bac> danilos: right
<danilos> bac, then,_it'd be_up to the call-sites to_just deal with_all the_supported_actions that are_really supported
<danilos> bac, do you think_you've got an_idea of how you can go_about_this or do_you_think_we should_have a call?
<gary_poster>_danilos,_you are_gone...in_30 min?
<danilos> gary_poster, as soon as_we_are set for the following steps, actually_(started at 8am this_morning)
<gary_poster>_ack
<gary_poster> I haven't actually_looked at your branch yet._ was geting mine in. _Lemme look_at it_really fast and then see if I have any questions. _That way at least one of_me or bac can_try to_touch_base with you_a_final time_on this today.
<gary_poster> you ec2 landing that_branch danilos?
<danilos>_gary_poster, yep
<gary_poster> awesome
<gary_poster> danilos, I don't_understand bac's para: "The_elaborate_substitution framework you've created looks to_be very well thought out and_tested.  I hope that_the_usage_of it justifies the work_you've done...but I don't see the_larger design here."
<gary_poster>_Is he referring to safely_render_description?
<danilos