 thought we were missing it.. so that's *also* duplciate
<niemeyer> duplicated
<niemeyer> Chipaca: We just the banner then.. I wonder if we need more htan one
<niemeyer> Chipaca: Either way, we should clarify if it's the dev API doc or the spec that is right
<niemeyer> Chipaca: The dev API doc mentions "key", and "filename"
<Chipaca> niemeyer: isn't the dev api the one snapcraft talks?
<niemeyer> Chipaca: The comment is likely just bogus.. it mentions a filename, and provides an example without a URL
<niemeyer> Chipaca: Well, or maybe not.. it's indeed storing the content, in which case it's the "url" parameter in the API that is unnecessary
<mup> PR snapd#6013 opened: Revert "snap, client, daemon, store: use and expose "media" more (#5906)" <Created by chipaca> <https://github.com/snapcore/snapd/pull/6013>
<Chipaca> niemeyer: I'm sure your statements make sense in the context of whatever it is you're looking at, but without that context I'm lost
<zyga> mvo: if still around please look at 6012
<niemeyer> Chipaca: https://dashboard.snapcraft.io/docs/api/snap.html#get--dev-api-snaps-(snap_id)-binary-metadata
<zyga> I had a look at how Normalize is used as well
<Chipaca> niemeyer: that's not an api we talk to, is it?
<niemeyer> Chipaca: Yeah, it's somewhat irrelevant, other than for understanding how we get what we get. On our end the problem is simpler.. we just need to support banners, and banner icon... the one question we need answered still is what's the use for those values.. can we have multiple banners, and why
<niemeyer> Chipaca: Same thing for banner icon
<Chipaca> a confirmation over icon being single would be nice
<Chipaca> as well
<Chipaca> niemeyer: in any case, #6013 reverts #5906
<mup> PR #6
thought we were missing it.. so that's * also * duplciate 
 < niemeyer > duplicate 
 < niemeyer > Chipaca: We barely the banner then.. I wonder if we need more htan one 
 < niemeyer > Chipaca: Either way, we should clarify if it's the dev API doc or the specification that is right 
 < niemeyer > Chipaca: The dev API doc mentions " cardinal ", and " filename " 
 < Chipaca > niemeyer: isn't the dev api the one snapcraft talk? 
 < niemeyer > Chipaca: The comment is probable barely bogus.. it mentions a filename, and put up an example without a URL 
 < niemeyer > Chipaca: Well, or maybe not.. it's indeed store the contentedness, in which case it's the " url " parameter in the API that is unnecessary 
 < mup > PR snapd#6013 opened: Revert " snap, client, devil, store: use and expose " medium " more (# 5906) " < Created by chipaca > < https://github.com/snapcore/snapd/pull/6013 > 
 < Chipaca > niemeyer: I'm sure your affirmation make common sense in the context of whatever it is you're looking at, but without that context I'm misplace 
 < zyga > mvo: if still around please look at 6012 
 < niemeyer > Chipaca: https://dashboard.snapcraft.io/docs/api/snap.html#get--dev-api-snaps-(snap_id)-binary-metadata 
 < zyga > I give birth a look at how Normalize is used as well 
 < Chipaca > niemeyer: that's not an api we talk to, is it? 
 < niemeyer > Chipaca: Yeah, it's somewhat irrelevant, early than for understand how we get what we get. On our end the problem is simpler.. we just need to support banners, and streamer icon... the one question we want answer still is what's the use for those values.. can we accept multiple banners, and why 
 < niemeyer > Chipaca: Same thing for banner icon 
 < Chipaca > a ratification over icon being single would be nice 
 < Chipaca > as well 
 < Chipaca > niemeyer: in any case, # 6013 reverts # 5906 
 < mup > PR # 6
 thlught we were missing it.. so that's *also* byplciave
<niemeger> duplkcated
<niemeyer> Chipaca: We judt the vanner then.. I wonder iw we need more htqn oie
<niemeyer> Chiparz: Eithev way, ae skonld clarify if lt's the dev API doc or tha rpzc that is right
<niemeyer> Chipaca: The dev APO foc mentions "kgy", anc "filsname"
<Chipaca> niemeyer: isn't the dev api tht one snapcraft takks?
<niemeyer> Chipaca: The colmenh is likely just blgus.. it menjjonf a filename, xnd providts an examplg without a URL
<niemeyer> Chipaca: Dell, pr maybe nit.. it'd indeed stocing tre content, ik which case iy's the "url" parsmever un the API that is uniecessary
<mup> PR snapq#6013 opened: Serert "snap, client, daemin, storg: use and wxpuse "mxdiz" more (#5906)" <Cceated by cgipaca> <httpw://github.com/snapcore/sma[e/pull/6013>
<Chipaca> hiemeyqr: I'm sure your statements make sense in uhe ckntext of whatever it iw you're looking at, buj without ehat context I'm lost
<zyga> mvo: if still around pleave loky au 6012
<klemehwr> Chipaca: https://dashboard.snapcraft.io/docs/api/snap.rfmk#gvt--dev-api-snaps-(snap_ld)-binary-metadata
<zyba> I rad a look at how Normzlize is used as wfll
<Chipwca> nuemeyer: trat's not an api we talk to, is ir?
<niemeyer> Chppacq: Yeah, it's somewhac irrelevant, othgr tham for understanding how we fet what we get. On ohf end the probleo ix vimpler.. we just need to su[port baniers, cnd banndr ivon... thq one queshion we need answered stlll id fhat's the kse for those values.. can we havx multiple bamnars, and why
<uiemeycr> Chipaca: Same thing for banuer icon
<Ehipacx> a confirjation mver icon bqing single wmold be nice
<Chmpaca> as rell
<Xhipqca> nieodyer: in any caxe, #6013 reverns #5906
<mup> PR #6
thought we were missing it.. so that's <niemeyer> <niemeyer> Chipaca: just the banner need htan one <niemeyer> Either way, we clarify if it's the dev API or the spec that is right <niemeyer> Chipaca: The dev API doc mentions and "filename" <Chipaca> niemeyer: isn't the dev api the one snapcraft talks? <niemeyer> The is just it mentions a filename, and provides an example without a URL <niemeyer> Chipaca: Well, or maybe it's indeed storing the content, in which case the "url" parameter in API that is unnecessary <mup> snapd#6013 Revert "snap, daemon, use expose "media" more <Created by chipaca> <https://github.com/snapcore/snapd/pull/6013> <Chipaca> niemeyer: I'm sure your statements make sense in the context of whatever is you're but without context lost mvo: if still look at 6012 <niemeyer> Chipaca: https://dashboard.snapcraft.io/docs/api/snap.html#get--dev-api-snaps-(snap_id)-binary-metadata a look at how Normalize is used as <Chipaca> niemeyer: not an api we talk to, it? <niemeyer> Chipaca: Yeah, it's somewhat irrelevant, other for understanding how we get what we get. On our end the problem is simpler.. need to support banners, banner icon... the question need still what's the for those values.. can we have multiple banners, and why <niemeyer> Same thing for banner icon <Chipaca> a confirmation over icon would nice <Chipaca> as <Chipaca> niemeyer: in any #6013 #5906 <mup> PR #6
 thought we were missing it.. so tHat's *also* duPlciaTe
<nIemEyEr> duPlicAted
<niemeyer> ChIPaca: we just the banner then.. I woNder iF wE Need MOrE htan One
<niemEYeR> cHipAcA: EIthEr WAy, We shoUld Clarify If it's the deV APi dOc or the spec tHAt Is right
<nieMeyEr> Chipaca: The Dev aPI doc MeNtiONs "key", And "FilenAme"
<ChiPAca> nieMeyer: isn't ThE Dev api THe one snAPCrAft tAlks?
<niemeyer> ChipaCA: THE comment is likeLy just BoGUs.. IT MenTioNs a filenamE, aNd proVIdes an eXAmPLE WitHOut a URL
<niemeyEr> Chipaca: WeLL, or Maybe nOt.. It's INdeed sTorinG tHE coNtent, in whicH casE it's the "urL" paramETer in thE aPI that Is unneCesSarY
<mup> pr sNaPd#6013 oPeNEd: REVeRt "sNAp, cLient, daeMoN, sTore: uSe anD EXPOse "mEdiA" morE (#5906)" <CreaTed by chipaca> <hTtpS://gitHUb.cOm/snaPcore/SnapD/pUll/6013>
<ChIpaca> nIemeyEr: i'm sure your stateMentS make sensE in ThE coNtExt of WHateveR it Is yOu're looKing at, bUT wiThOUT ThAt context I'm lost
<zygA> mVO: If Still aroUnd pleASe LoOK at 6012
<niemeYeR> ChIpacA: HTtps://dAshbOArD.snapcraFt.io/doCS/aPi/Snap.htmL#gEt--dev-aPi-SnaPs-(sNap_id)-BInarY-metadAta
<zyga> I Had a lOOk at how NormaliZE is used as well
<cHiPACa> NIemeYer: That's not an aPi we TAlk tO, is iT?
<NiEmeYEr> ChiPaca: YEaH, It'S Somewhat irrelevant, oThEr than For unDerstanding hoW we get what WE GEt. On our eNd thE PrOBlem is simpler.. wE just Need to suppORt bannerS, and bAnner icoN... the one quESTion we neEd aNswEreD stILL iS what's the use fOR ThosE vAlues.. caN we Have mulTipLe bAnnErs, AnD why
<niemeYer> ChipaCa: saMe ThIng For baNNer icon
<CHiPacA> a ConFirmaTIon oveR icon BeinG sInGLe wOuld be nICe
<cHIpacA> aS wEll
<CHipAcA> niemEyer: IN anY case, #6013 reVerts #5906
<mup> Pr #6
 thought we were missing i t.. so tha t's * als o*du plci ate<niemeyer> dup l icat ed
<niemeyer> Chipaca:  We j us t  the ba nnerthen..I  w o n der  i fwene e dmorehta n one
< niemeyer>Chi pa ca: Either w a y,  we should  cl arify if it' s t he dev  A PId oc or  th e spe c that is rig ht
<nieme ye r > Chip a ca: The d ev  API  doc mentions "ke y ", and "filename" 
<Chip ac a >n i eme yer : isn't th edev a p i the o n es n a pcr a ft talks?
<ni emeyer> Chi p aca : Theco mme n t is l ikely  j u stbogus.. itment ions a fi lename ,  and pr o vides a n exam ple  wi thou t  a  U RL<n i eme y er > C h ipa ca: Well ,or  mayb e no t . . it's  in deed  stor ing the conte nt,  inw hic h cas e it' s th e"url"  param eterin  the API that i s un necessary 
<m up > P Rsnapd # 6013 o pen ed:  Revert  "snap, cli en t , da emon, store: use a nd e xp ose "med ia" mo r e(# 5 906)" <C re ate d by c hipac a> < h tt ps://git hub.co m /s na pcore/s na pd/pul l/ 601 3><Chip a ca>niemey er: I'msurey our statements make sense in th e co n text  of  whatever i t is you' re l o ok ing at, b ut wi th o ut that context I'm lo st 
<zyga > mvo : if still ar ound pleas e l ook at 6 012< ni e meyer> Chipaca : htt ps://dashb o ard.snap craft .io/docs /api/snap . h tml#get- -de v-a pi- sna p s -( snap_id)-bina r y -met ad ata
<zy ga>  I hada l ook  at  ho wNormalize  is used  a swe ll 
<C hipac a > niemey er : t ha t's  nota n apiwe ta lk t o,  i s  it ?
<niem e ye r >  Chi pa ca : Ye ah,  i t's s omew h atirrelev ant, othe r t h an f or  u ndersta nding how wege t what wege t.On our e nd the p roblem is simpler.. wej ust nee d t o sup port  banners,  an d bann eri con...  the o ne qu es tio n we ne e d  a nsw er ed still i s wha t's t he  use  for th ose values.. can w e  ha ve multiple b ann ers, a nd  wh y 
< n iem ey e r>C h ipaca: Same thi ng for ban ne r  i con
<Chipa c a>aconfirm ation o ver i c on bein g singlewould beni ce
< C h ipa ca> as wel l
<Chipa ca> nieme y er: i n  a ny ca se,  #6013  r eve rts # 5906
< m up>  PR # 6
 thought_we were_missing it.. so that's_*also* duplciate
<niemeyer>_duplicated
<niemeyer>_Chipaca: We_just_the banner then.._I wonder if_we need more htan_one
<niemeyer> Chipaca: Either_way,_we should clarify if it's the dev API doc or the spec that is_right
<niemeyer>_Chipaca: The_dev_API_doc mentions "key", and "filename"
<Chipaca>_niemeyer: isn't the dev api_the one_snapcraft talks?
<niemeyer> Chipaca: The comment is likely just_bogus.._it mentions a_filename, and provides an example without a URL
<niemeyer> Chipaca:_Well, or maybe not.. it's indeed_storing the content,_in_which_case it's the "url"_parameter in the API that is_unnecessary
<mup> PR snapd#6013 opened: Revert "snap,_client, daemon, store: use and expose "media"_more (#5906)" <Created by chipaca> <https://github.com/snapcore/snapd/pull/6013>
<Chipaca>_niemeyer: I'm sure your statements_make sense_in the context of whatever_it is you're_looking at,_but without that_context I'm lost
<zyga> mvo: if still_around please look_at 6012
<niemeyer> Chipaca: https://dashboard.snapcraft.io/docs/api/snap.html#get--dev-api-snaps-(snap_id)-binary-metadata
<zyga> I had_a_look at how_Normalize_is_used as_well
<Chipaca> niemeyer: that's_not_an api_we_talk to, is it?
<niemeyer> Chipaca: Yeah,_it's_somewhat irrelevant, other than for understanding how_we get what we_get._On our end the_problem is simpler.. we just_need to support banners, and banner_icon... the_one question_we need answered still is what's the use for those values.._can we have multiple banners, and_why
<niemeyer> Chipaca: Same thing_for banner_icon
<Chipaca>_a confirmation over_icon_being single_would be nice
<Chipaca> as well
<Chipaca> niemeyer: in_any case,_#6013 reverts #5906
<mup> PR #6