This is no longer my fight.

This has effectively expanded in scope into T13098.

Closing in favor of Discourse as the main user hangout spot for now.

After T12652, rCORGI is here on secure.phabricator.com.

On meta

Corgi

Yeah, I was surprised neither of you jumped on "phounder". Where does that content live? I can't seem to find it in any of the repos I already have checked out.

(choose whatever you like)

I think we should all pick "Ph" titles.

Only if I get a cool title.

The video in T12078 now plays correctly for me so I think this is, in fact, resolved.

I have many other excellent ideas for the Phacility online swag store, these are my favorite:

If only Phortune had an inventory management system.

Also ordered hoodies.

I want

Ordered a new batch of tshirts at great corporate expense.

Those are old now I guess, I'll file something to see if @chad can fix it because I am not licensed to pixel.

I'm going to merge this into T12134, which begins defining a more concrete plan roughly following some of the outline above. The major change from an upstream perspective since this task was filed is that we have a more specific set of harder technical requirements around support for Phacility SAAS instances (particularly after the launch of free instances), so it makes more sense to let those requirements drive product design and then accommodate general free support under that umbrella. Broadly, I expect to move support (bug reports, feature requests) into Nuance and continue reducing user access to the upstream.

Specifically, here's what I believe the bug is, in rough terms that probably get some specifics wrong:

.mov thing is likely an interaction between range requests and encryption. It works for me in Firefox. It only affects media files for installs which have configured file encryption and there's no data corruption/loss so I don't plan to get to it for a while unless a real install hits it.

ok forget it. works fine in other browser.

Chad's House ?

How do I reproduce that?

@epriestley maybe also related? Some files are just missing in Conpherence now.

My misunderstanding on this btw, I assumed mov was an option, not a default.

No worries, totally understandable.

I am very sorry I am declaring t-shirt bankruptcy because I have learned it takes me over five hundred years to ship a t-shirt.

Some other things that could use updates:

(Just so no one thinks too highly of me, I'll underscore that I very briefly peaked at #11. I think I had slid to about #35,000 by the end of the lightning round and "-∞ dumpster garbage rank" by the end of the competition.)

We didn't have cheering shirts this year.

Sadly, I didn't win ICFP with PHP this year. I got up to #11 (just 33,600 points from the top slot!) but had to go to a meeting in the morning:

ICFP2016 starts in about 6 hours:

CORGI will fix this and clearly it is too hard for me.

Hahaha I suddenly remembered this

Some discussion in, e.g, T9028, but we don't plan to ever actually delete these commits. They may have comments, audit status, meaningful relationships to other objects, builds, build artifacts, etc.

(T9308 is the origin story of cat1 through cat3.)

I'll put them into rotation and report back on A/B results.

Sadly, cats 1-2 were prototype cats showing a progression toward cat3. cat4 is a unique cat but I'm not sure it has the charm of cat3.

I replaced the existing logo with the one you provided some time ago. It has not been met with universal fanfare as I would have expected given the level of artistry displayed.

I believe we no longer state anywhere to go to IRC for support, though old timers are welcome to hang out.

I believe this is resolved.

oh @robla, yeah I'd be interested in a repo of that error, if you can. I've seen it in my sandbox (once) but I also nuke my questions and answers all the time so assume it was development related.

I tried answering @epriestley Q134, but got an error (which I failed to copy) and then another error "#1062: Duplicate entry '0-PHID-USER-4188de7cae592cf1bce4' for key 'key_oneanswerperquestion'". So...I'll put my answer here

Doesn't look like there's really much we can do here in the upstream which isn't filed elsewhere.