Tavern on the Meta

12:00 AM

@NormalHuman Oh, so @hichris123 is God. That's what I was missing. Got it.

user259867

The build failed because Smokey's set of tests includes "Body here" as a supposedly good body.

Question... if I have a question about a Chat Bot that has stopped functioning, should I ask that question on the Child meta of the site that owns the room or on MSE because the chat rooms are a site-wide space?

user259867

Never mind that it could not actually exist (len<30).

user259867

@Catija MSE. Chat is separate from sites, it's just a different thing altogether.

Catija

@NormalHuman Thanks!

user259867

12:06 AM

That said, it's not clear if it would be on topic there, if it's a bug in 3rd party code.

Catija

I'm guessing it's similar to

13

Q: Feed bots not working?

In the Sci-fi & Fantasy SE chat room, we have a chat feed bot that posts new questions. However, it hasn't worked in several hours. The RSS feed it pulls from is updating, so the issue isn't on that end. And we're not alone in this either. Can someone whack the chat feed bots, and get them wo...

bjb568

I no longer accept www.dd, www is stupid

Kevin Brown

couldn't get something to work with www so you're just killing it off?

user259867

But... a cookieless domain for static content?

user259867

> I drank water made from human feces. Here’s an update on the machine that produced that water: b-gat.es/1hyEu2p pic.twitter.com/w78xVYswSH -- Bill Gates at 4:04 PM - 12 Aug 2015 via Twitter

user259867

12:15 AM

Bill has his own URL shortener?

user259867

He is truly an embodiment of evil.

user259867

Okay, looks like there is no flood of false positives from posts with few unique chars. I tightened it to <8 chars (after html tag discount) to be on the safe side.

hichris123

@durron597 Yep.

bjb568

@KevinBrown nah, I just decided I don't like it

Is it possible to disable TLS 1.0 and 1.1 on node and only use TLS 1.2?

SSL_OP_NO_TLSv1 flag I think disables all of the above

I think I figured it out:

secureOptions: constants.SSL_OP_NO_TLSv1_1|constants.SSL_OP_NO_TLSv1|constants.SSL_OP_NO_SSLv3|constants.SSL_OP_NO_SSLv2

James

12:48 AM

Hey

Life...... Don't talk to me about life

bjb568

buahaha, screw you old browsers!

James

Good

tchrist

1:06 AM

@NormalHuman Good, I was worried about that. Thanks.

hichris123

ugh ugh ugh no @bjb568.

GCM is before CBC.

bjb568

Mozilla likes it that way

What's wrong with it?

hichris123

GCM should always come before CBC. Chrome's thinking of depreciating it...

bjb568

:o

Wait what, I do have GCM on top

	ciphers: [
		'ECDHE-RSA-AES256-GCM-SHA384',
		'ECDHE-ECDSA-AES256-GCM-SHA384',
		'kEDH+AESGCM',
		'ECDHE-RSA-AES256-SHA384',
		'ECDHE-ECDSA-AES256-SHA384',
		'ECDHE-RSA-AES256-SHA',
		'ECDHE-ECDSA-AES256-SHA',
		'!aNULL',
		'!eNULL',
		'!EXPORT',
		'!DES',
		'!RC4',
		'!3DES',
		'!MD5',
		'!PSK'
	].join(':'),

hichris123

Where's it even picking CBC from?

bjb568

1:12 AM

IDK, doesn't it enable some things by default even if I don't mention them in the list?

hichris123

Maybe. I guess so.

But at least your list is good.

bjb568

So should I explicitly disable CBC?

hichris123

nah.

bjb568

ohkeydonkey

hichris123

You should just always prefer AES-GCM and ChachaPolly (which node.js doesn't support) before AES-CBC. That way, Chrome doesn't yell at you.

bjb568

1:16 AM

Oh noes! What do I need to do?

hichris123

huh.

user259867

Copy-paste the second part into search?

user259867

I mean, there's no clue to what is considered obsolete here.

tchrist

@bjb568 Get yourself a 2560×1440 monitor for starters.

hichris123

@NormalHuman Everything but AES-GCM & ChachaPolly

user259867

1:23 AM

TIL that when Date.parse("2015-08-08 15:40:53Z") returns a date, that's just due to the kindness of strangers...

user259867

implementing JS in a particular browser.

hichris123

IIRC Firefox doesn't do it that way?

I forget.

user259867

Let me try.

hichris123

Oh oh I see what you're saying.

user259867

No, I mean it's NaN in FF

hichris123

1:25 AM

Yeah, Date.parse() returns a Javascript timestamp value.

Oh oh oh.

I'm tired.

user259867

Chrome is being too kind here.

hichris123

What's wrong with it?

Too lazy to check the source/spec.

user259867

By ECMA spec, the format must be 2015-08-08T15:40:53.000Z

user259867

with milliseconds and all

hichris123

Not necessarily. It's the T.

user259867

1:27 AM

Let me try...

hichris123

In Edge, Date.parse("2015-08-08T15:40:53Z") works.

user259867

In Firefox, too. But again, this may be their kindness.

hichris123

I don't think so.

But I'd have to pull up the spec.

user259867

Google Apps Script rejects it (i.e., NaN). Apparently, it runs Rhino, en.wikipedia.org/wiki/Rhino_(JavaScript_engine)

hichris123

Nope, it's fine.

> It also includes “date-time” forms that consist of one of the above date-only forms immediately followed by one of the following time forms with an optional time zone offset appended:
THH:mm
THH:mm:ss
THH:mm:ss.sss

ecma-international.org/ecma-262/6.0/…

bjb568

1:30 AM

@tchrist is 2880 x 1800 enough?

tchrist

@bjb568 Probably. Your display was strange.

bjb568

nah, just retina

user259867

Hm, indeed. Was also valid in ES 5.1. No idea what Apps Script is thinking there.

Transcript for