00:15
<wanderview>
JakeA++ for dealing with twitter storm
10:46
<annevk>
Hmm, is it "a HTTP/TCP/UDP API" or "an HTTP/TCP/UDP API"?
11:04
<_francisco>
annevk: ping
11:05
<annevk>
_francisco: I'm around
11:05
annevk
prefers http://www.nohello.com/
11:05
<_francisco>
annevk: will take that in mind
11:07
<_francisco>
annevk: i'm working with serviceworks in b2g, testing to intercept post and put request, but had some problems with the body of those request, bkelly told me that are not part of the standard, just get request are, and wanted to double check
11:08
<annevk>
_francisco: you can't cache non-GET requests, but they should work when it comes to interception
11:08
<annevk>
_francisco: there should be a fetch event for them, for instance
11:10
<_francisco>
annevk: was planning to use http verbs to modify the content of the cache, in chrome was able to intercept the post request, but wasn't able to read the request body, an implementation problem I guess, same in gecko, https://bugzilla.mozilla.org/show_bug.cgi?id=1134325
11:12
<annevk>
_francisco: a simple request.text() does not work? That sounds very broken :-(
11:13
<_francisco>
annevk: right, tried that, also tried to read directly from the stream reader, and no luck
11:13
<annevk>
_francisco: stream reader?
11:16
<_francisco>
annevk: sorry :(, the body, i was trying to read directly the body and no luck either
11:16
<annevk>
_francisco: I don't think we expose the body yet
11:16
<_francisco>
annevk: that explains what then :)
11:16
<annevk>
_francisco: you have to use .blob() .text() .json()
11:17
<annevk>
_francisco: then wait for the promise to resolve, etc.
11:17
<_francisco>
annevk: tried with .text() setting the request headers to text/plain, and no promise resolved :(
11:23
<_francisco>
annevk: another question, sorry if this is a stupid one, what's the reason why non-GET request cannot be cached?
11:24
<annevk>
_francisco: I think the main reason is that it's unclear how that would work semantically
11:24
<annevk>
_francisco: e.g. a POST is typically expected to clear the cache entry for that URL or some such
11:37
<MikeSmith>
does substack normally behave in a caustic and uncivil way or the twitter stuff from yesterday out of character?
11:38
<MikeSmith>
also does he usually express himself in a way that's entirely devoid of wit and humor
11:38
<annevk>
I'm not sure, but he's from the Node.js community I think, which already had a bad rep with standards
11:40
<MikeSmith>
annevk: from what I've seen I think the Nodes.js community doesn't have a bad rep with standards, but instead a couple of influential individuals within the community try to get others to share their anger and hate
11:41
<MikeSmith>
annevk: plus a lot of the isn't directed at standards but instead at people working on standards
11:41
<MikeSmith>
or just, at people
11:41
<annevk>
Yeah dunno, seems he's over it: https://twitter.com/substack/status/578003665727852544
11:42
<MikeSmith>
I can still remember the days when slightlyoff was pretty outspoken about how browser vendors were doing things, but he was always a lot more civil and articulate about it
11:44
<MikeSmith>
annevk: that tweet's cool but before he got to that point he just scattered out a lot of bad energy and hate toward people who are trying to fix the very stuff he's hating on about
11:44
<MikeSmith>
I mean I realize he feels strongly about this stuff, and that's good
11:45
<MikeSmith>
but he might have the human courtesy to imagine that the people he was directing all that at care a lot about it to and don't have their heads way up there asses the way he makes it sound
11:45
<annevk>
I have a hard time getting upset over a rant from someone who hasn't even done basic fact checking
11:46
<MikeSmith>
well the thing is, in terms of the work he does, that guy is a major force for good
11:46
<MikeSmith>
gotta have deep respect for the work he's done
11:46
<MikeSmith>
he's not some uninformed fool
11:46
<Ms2ger>
So a Linus type?
11:47
<MikeSmith>
Ms2ger: dunno
11:47
<MikeSmith>
but there's no shortage of those I guess
11:47
<MikeSmith>
it's the rule, not the exception
11:48
<MikeSmith>
I guess what is exceptional is that we have people like JakeA who put their hearts into responding thoughtfully instead of just ignoring them or fanning the flames
11:49
<MikeSmith>
anyway I wish more people would take time to think about the fact that real people are on the other end of their hate gun
11:50
<MikeSmith>
even when they think they're directing their hate toward abstract entities
11:51
<MikeSmith>
and thank god for JakeA
11:59
<smaug____>
Ms2ger: Linus type? Linus is fine
12:07
<annevk>
MikeSmith: yeah, I replied too https://twitter.com/annevk/status/577759092065832960 but the guy ignored me
12:11
<MikeSmith>
annevk: you probably just caught him at one of the points where he had to stop to wipe the rage sweat off his brow
12:11
<MikeSmith>
annevk: btw I met hirano today
12:12
<annevk>
MikeSmith: cool
12:23
<annevk>
Chrome's unsung heroes from Tokyo
12:27
<MikeSmith>
annevk: indeed
12:27
<MikeSmith>
all very nice people
12:27
<MikeSmith>
along with being very clever
12:27
<MikeSmith>
Yoshino has a heart of gold as well
12:46
<annevk>
What's this W3CMemesExposed thing? Haha
13:04
<MikeSmith>
annevk: no idea but I admire the wit
13:05
<MikeSmith>
let a hundred flowers of W3C memery bloom
13:05
<JakeA>
MikeSmith: cheers! Going to print that and hang it on my wall
13:09
<MikeSmith>
JakeA: 😆
13:12
<annevk>
https://twitter.com/tomdale/status/578012373631430656 and https://twitter.com/tomdale/status/578012197206409216 are also spot on
13:17
<wanderview>
Domenic: am I just completely confused about being able to use native implementations of streams for things returned from DOM APIs?
13:17
<MikeSmith>
annevk: wow yeah
13:25
<annevk>
https://twitter.com/html5_yoda/status/545129883438166016
13:36
<Domenic>
wanderview: you should be able to ... just like promises, except instead of a tiny little `(resolve, reject) => { doRealWork(); }` function, we have a big ol' underlyingSource object with a few hooks.
13:39
<wanderview>
ok
14:12
<slightlyoff>
For some context: aspects of the node community (substack included) have been telling us *for years* that working on ES6, improving the platform, etc has all been a waste and using that as a reason not to engage in helping to make the designs better. Except now that we did it anyway, io.js is using ES6 features as marketing.
14:13
<slightlyoff>
So I don't want their feedback; not if it comes in a rageball. Will talk to the civil wing of the node world instead. Life is far too short.
14:15
<Domenic>
Ah, but isn't that tone policing? </sarcasm>
14:16
<Domenic>
https://twitter.com/substack/status/408293739665162240
14:18
<darobin>
there's so much energy spent replying to the hate there...
14:21
<MikeSmith>
slightlyoff: Thanks for the background. I'm glad to have missed the intervening years of bad vibes
14:23
<MikeSmith>
ah yes the tone policing card
14:23
<MikeSmith>
a key tool of the bigot
14:24
<MikeSmith>
tolerate mah bigotry!
14:25
<darobin>
it's a free country! I can be a jerk to you if I want to!
14:27
<MikeSmith>
yeah I cry now about all the times I've simple-mindedly been intolerant of their rights to abuse and demoralize nice people
14:29
<darobin>
hehehe
14:39
<MikeSmith>
darobin: btw the other trajectory/cycle here is where the abusive person does their abusive behavior and then in the end comes around to saying, I'm so sorry! ... til the next time two weeks later when they come back to abuse you again
14:40
<MikeSmith>
beat -> I'm sorry! cry/hug -> beat ...
14:40
<darobin>
yeah, that's a classic too
15:42
<MikeSmith>
https://twitter.com/console_dot_log
15:42
<MikeSmith>
https://twitter.com/console_dot_log/status/578054541901328384
18:00
<sambuddhabasu1>
can anyone help me with safari response headers?
21:49
<TabAtkins>
Ugh, I keep forgetting what type to use for an array-valued attribute. This would be fully author-editable, but hopefully with a typecheck.
21:49
<TabAtkins>
Pretty sure I'm not allowed to use sequence<Foo> as an attribute type.
21:52
<TabAtkins>
Oh wait, the collection I want already exists.
21:53
<smaug____>
I thought array attributes issue isn't still solved
21:53
<TabAtkins>
It's not.
21:53
<TabAtkins>
:(
21:53
<heycam>
sorry :(
21:54
<heycam>
the plan is there though. just need to unbitrot the branch I made proposed changes in.
21:54
<TabAtkins>
I can sidestep it this time, because I can just use StyleSheetList.
21:55
<smaug____>
heycam: the plan is to freeze the array or what?
21:55
<smaug____>
and keep the array until the native side just happens to want to update it?
21:56
<heycam>
smaug____, yeah
21:56
<heycam>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23682#c25
23:29
<rektide>
MikeSmith: thanks for your comments last week regarding my incindiary behavior on twitter re: push api.