When Phabricator is in a production configuration, we should start checking hashes and 404'ing requests with bad hashes to improve robustness. There's no real reason why we don't do this now, except that Akamai was aggressive about caching 404's at Facebook in 2007.

• Registered @phacilitystatus.
• Added a link to it to the admin console.
• Credentials in K41.

I've been pushing the cluster weekly, but it basically goes down for about 30 seconds some time early on a Saturday and no one notices. My tentative plan here is:

@rbalik, see T4778: When will my feature get built, or my bug get fixed?

I think the new "evaluation period" copy is a pretty good starting point for now. We'll probably evolve this over time.

How about changing the entire product to default to not sending any email?

Are you sure about that? I don't understand a lot about this, but isn't this what Edge Side Includes is supposed to solve? Better caching for logged in users?

• Column layout now has send-on-enter.

There's still a race condition that we should fix, the window is just a lot narrower.

This is almost a year old, I can't reproduce it, and we haven't seen other reports.

Support for streaming files (vs fire-and-forget requests) -- which I think was discussed somewhere -- is no longer very important after T7149. We can now store files of arbitrary size in engines that only expose the existing writeEntireFile($big_chunk_of_data) API without major downsides.

After T7149, drag-and-drop uploads support arbitrarily large files and resumable uploads for files larger than the chunk threshold (currently 8MB).

This has been a few months, any idea if there was a resolution?

• In Files → (Choose a File) → Edit File, the only available option is "Visible To".
• Add a "name" field.
• Add a "name" transaction type, editor support, etc., so changing the name shows up in the file's edit history.

I don't think there's any product or technical reasoning here, Files just predated ApplicationTransactions and came from a simpler time.

There's (intentionally) no natural way to get to /repository/<branch>/. It's reachable by clicking the crumbs from /browse/<branch>/.

Why do you want to go to /repository/ instead of /browse/? See:

Yes, use a rule like this:

This was caused by a miscast of a floating point value to an integer, which could incorrectly truncate it and leave us trying to load the same page over and over again in a loop. It required a particular combination of subpriority value, paging boundaries, and task visibility; we happened to have all three. rP106ca70a should resolve it.

We should already do this. See this document for some details. We refer to caching reverse proxies as "CDNs", under the assumption that most users will not be configuring their own, but the principle is the same:

We make a request to /blah/?meme=x, which generates the appropriate image on the server side and redirects to it. The meme rule doesn't know anything about the underlying image.

I can break it in full Conpherence if my browser window is narrow enough that the highlander macro is rescaled by the max-width: 100% rule.

This is probably:

I think it's this:

Pushed, but "pesistant" is still spelled incorrectly. :)

Just a quick update here -- there are really two barriers:

D12060 or followup work should remove the limit from arc upload.

No. You can write herald rules which match paths against regular expressions, but Owners only matches prefixes.

See, e.g., https://secure.phabricator.com/book/phabdev/article/conduit/

In Safari, dragging files to the homepage now flashes the mask on and off rapidly. You have about a 50% chance of actually hitting an upload.

The new protocol will go roughly like this, either via a new Conduit API method like file.allocate or an extension to file.uploadhash:

Quicksand is going to take a long time to sort out sufficiently -- I expect we're a minimum of 2-3 weeks away from making this public/announced, since I'm probably not even going to start working on it until later next week at the very earliest.

D12053 marks this as fixed. Specifically: