Topic: Main Topic: Kayode Ezike with Updates on MIT/DCC Credential Status WOrk
<xander> I don’t think you can set http cache control headers on GitHub-hosted files.
Xander: I guess I have to have you spoken before so I'll just quickly I'm the security lead for the pocket team just wanted to follow up on David's question real quick so the idea there was that you were going to rely on HTTP cache control headers to set the expiry time for a different certificate right but you're also talking about using services like GitHub to do the hosting I don't believe that you can set the expired header value if you're using a service like that. ✪
Xander: You may need to put that you may need to put the time value on the file done. ✪
Xander: I don't think so I got used the Enterprise version before I think basically if you're using GitHub to host files like get on pages or whatever they really handle everything and you don't get access to that level. ✪
Jonathan_Bethune: Better I was using one earpod and it's the one that's dead so okay sorry about that so real quick by way of introduction I think I've spoken much my name is Jonathan and the engineering manager for pocket colleague of Xander who spoke a little while ago just real quick I was wondering if there was a way to get a link to the presentation and actually had a lot of discussion internally about the X and we're just wanted to look into a little. ✪
<phil_l_(p1)> Nate's Comment:
Jonathan_Bethune: There we go oh that's fast okay let me well I actually didn't get the click on it we just grabbed it's in the chat right there we go. ✪
<phil_l_(p1)> Good point Nate.
Jonathan_Bethune: Yeah got it alright thank you. ✪
Mahesh_Balan_-_pocketcred.com: Yes I had a question slightly unrelated here but more on the open badges 3.0 spec I've been trying to get hold of it and I seem to be pay bald by this IMS Global if somebody has that and can make the open badges 30 spec which is publicly visible I would appreciate it thank you. ✪
TallTed_//_Ted_Thibodeau_(he/him)_(OpenLinkSw.com): I just following up on responding to David's question about the unique identifier for each credential in the same way that a URI is expected to be stable that is that is the stability that we mean for the ID in these verifiable credentials URI is always meant to name the same thing which doesn't mean that it the thing it names stays the same forever. ✪
TallTed_//_Ted_Thibodeau_(he/him)_(OpenLinkSw.com): Much like your name always means you, but your contents don't stay the same forever. ✪