#Gargroni dont think pA is important so no big loss there
#sandro(Lots of W3C staff members are also opposed. One staff member let it influence his decision to keep working for W3C. Others of us don't see that as a useful tactic.)
#cwebber2so yeah I think there's good reasons to oppose EME, I don't object to someone taking a stand on it if they're vocal on it
#cwebber2(though conflating it with other things might be another matter)
#sandromeanwhile, w3c.social (hosted on scaleway, where mastodon.social is also hosted) was unreachable for a few minutes just down. I didn't think to check if I could reach mastodon.social at the time.
#cwebber2context for #social, I'm presenting on ActivityPub and the paper I wrote about "even more decentralized activitypub", and Mastodon's implementation of Linked Data Signatures, and etc on the CCG call today
#Loqi[marten-de-vries] #119 'the hub terminates the subscription'
#cwebber2sandro: julian said some reassuring things, I guess we're in the land of "I need to ask Ralph" because it looks probably ok to me but it's not up to me
#cwebber2tantek: the best we can do is provide Ralph with enough background and information to make a judgement call
#cwebber2sandro: I wish we didn't have to, it doesn't fit in the process; if we say it doesn't need a new CR it doesn't involve ralph until we do another PR
#cwebber2sandro: if we say this is not a normative change and it turns out we're wrong, we won't know until we go back, kind of a rude way to find out
#cwebber2sandro: how we've been doing in the last year is to ask Ralph for advanced ruling but I've done that like 4 times.... I guess it's time for another one though. or we could make another normative draft but aaron and julian aren't here
#cwebber2sandro: and aaron hasn't weighed in on the normative aspect yet
#cwebber2tantek: aaron deferred to julian's comment when I asked him
#cwebber2tantek: julien hasn't answered the question of whether it's normative or not, just about whether it'd break
#cwebber2sandro: my interpretation is it is a change in behavior, but a change during failure, so it won't break things that are working
#cwebber2tantek: I guess that depends on how normative / well defined our error handling is
#cwebber2sandro: that was my closing comment, make sure the hub-masters were all okay with it
#cwebber2tantek: I think you're right that it's a weakness in the w3c process about normative changes for error conditions...
#cwebber2tantek: there are 2 things going on. 1) I don't think it's affecting interop when things work, which is the point of interop
#cwebber2tantek: however, the handling of errors is where we often find security and privacy problems in computer systems in general. so if I were Ralph that's what I'd ask, how would it affect security and privacy if at all. I'd want the group to have an answer to that question before making a ruling. I don't know, I'm just asking it
#cwebber2sandro: since it's limiting behavior it's changing a MAY to a MUST
#cwebber2tantek: it may close some holes, but we're not sure
#cwebber2sandro: actually it's changing a MAY to a SHOULD... no wait a MUST, the hub MUST keep the subscription alive till the end of the lease duration
#cwebber2tantek: which we believe hubs are already doing
#cwebber2sandro: we know some are, haven't heard confirmation if all are
#cwebber2tantek: this sounds like a normative change since we're tightening the requirements
#cwebber2sandro: def a normative change since we're adding a MUST
#cwebber2sandro: but it's a normative change that doesn't restart the CR process?
#ajordanis the problem with a new normative CR that it restarts the CR clock? and editorial updates don't?
#cwebber2tantek: CR period is when you're supposed to be making changes based on implementations. We believe this tightening the CR requirements... we believe it's on what implementations do, that the tightening of the requirements will lead to more interop not less. not a new feature, just a tightening of requirements
#cwebber2sandro: right... not exactly how I'll phrase it but I think I can make the case
#cwebber2tantek: one of the reasons the process tries to make us restart like that is for IPR reasons
#cwebber2tantek: that's typically around the scope of a document, what's essential to implement
#cwebber2tantek: this is one of those things to implement that way
#cwebber2tantek: some random hubmaker could raise an issue though, that's the theoretical problem we have to give a heads up about and ask for a ruling at his level
#cwebber2sandro: I think the case simply has to be made that it's not invalidating reviews
#cwebber2tantek: I would even say it's a non-substitative normative change
#cwebber2sandro: that seems like a reasonable description
#cwebber2tantek: I believe this is one of the things CR is for
#cwebber2 how bad would it be to restart CR anyway?
#Loqi[aaronpk] Previous text:
> Hubs SHOULD retry notifications up to self-imposed limits on the number of times and the overall time period to retry. When the failing delivery exceeds the hub's limits, the hub terminates the subscription.
Proposed text:
...
#Loqi[aaronpk] Previous text:
> Hubs SHOULD retry notifications up to self-imposed limits on the number of times and the overall time period to retry. When the failing delivery exceeds the hub's limits, the hub terminates the subscription.
Proposed text:
...
#ajordanFINALLY got a new laptop and now has a working e key. I feel your pain :P
#ajordanit's just the JSON-LD context which gets thrown in every time we add something new to it
#ajordanso e.g. when Mastodon ships a version with the 1.7 version, if a new version comes out with the 1.8 context then the old version will pull down the 1.8 context and cache it
#ajordan... major topic of discussion, ended up having a good solution
#ajordan... I think that was the big thing, that resolution actually happened afterwards
#ajordansandro: there was another aspect that we didn't resolve
#ajordan... we still haven't figured out basically the governance question
#ajordan... how do we decide which terms get added to the AS2 namespace and when?
#ajordan... in general terms we get it but now we need specific
#ajordan... that question happened so fast and we were kinda on a deadline
#ajordan... we said "I guess just use terms that aren't in the AS2 namespace"
#ajordan... in the future we should find a more organized way for this
#ajordan... e.g. giving people permission to temporarily "lease out" a name that hasn't been specified yet
#ajordan... just do a temporary hand-wave kinda thing
#ajordansandro: it's interesting how much you can't change it later
#ajordan... I want to say "oh we can just change this later" but actually Gargron is shipping this to many admins who might not upgrade away from this relase for a year
#ajordantantek: definitely good real-world experience on some of the constraints that might shape your process
#ajordan... some of the ??? problems you might encounter
#ajordan... how do you deal with deployed implementations
#ajordan... I think these are important questions that whatever process you come up with should answer
#ajordantantek I gotta leave soon, need a new scribe
#ajordansandro: one interesting thing is that historically we said we'd delegate to the CG after the WG shut down
#ajordan... it might not hurt to have a resolution on the record saying we definitely delegate
#ajordantantek: I think I did that resolution a week ago?
#Gargroni started dabbling in my youtube project (codename "kobold" for now), it's ridiculous how unsure i am about the storage schema now, lol. either i approach it like in mastodon, or i do something different. no clue what's best. afraid to commit same mistakes.
eprodrom joined the channel
#cwebber2Gargron: the great thing about that phase is you can make massive experiments and switch things out and you've got no users yet to be upset about the upchurn by a big ol' refactoring
#cwebber2Gargron: I look forward to seeing more about MediaKobold ;)
#cwebber2Gargron: btw I do think you'll have a lot of fun with postgres + jsonb
#xmpp-social[ajordan] sandro: the SocialCG org homepage layout used to be borked too; I reported it but I've no idea if it got fixed