Possibly something dumb like "mount an EFS volume on /mnt/logs/ on every host" is another AWS-only approach. That feels really dumb but maybe it's only somewhat dumb?

I'm fine with CloudWatch logs, I didn't realize it had a logging thing. I'm currently not terribly warm on investing a ton in CloudWatch alarms or log analysis, but if we can get logs reliably streaming into some storage service so they can't fill up the disk I think that's quite valuable on its own. We can always replace that with something we control directly in the future if we want to invest more here. I can't imagine ever really caring about old logs no matter what happens in the future.

I definitely don't want to send logs to a third-party service.

In the modern era: I think we generally understand what private clusters will look like now, but I'd like to take a much more iterative approach to getting there than we have in the past. I had this concern above (circa June 2017):

Multiple installs would like API access to edit Almanac bindings.

This feels a bit like a return to the era of "epriestley design", but I think it's an improvement overall:

Still needs work:

I don't currently plan to pursue this. We haven't seen interest from other installs and I think the upstream behavior is reasonably good most of the time and not a huge issue even when we get it wrong (you can still review the file without doing anything, and can get highlighting with a few clicks -- plus, the file and page render much faster).

• The secret $1-2,7-9 syntax for highlighting multiple noncontiguous blocks of lines in Diffusion is no longer supported.

im super ethical https://github.com/PoE-Profile/poe-profile/pull/20

A related attack is a bare whatever.patch file which writes to .git/config or .hg/hgconfig or whatever.

In Safari we get this marvel:

This will ultimately be covered by T13105.

Effectively now covered by T13105.

See T13105 for browse cases (and perhaps diff cases, eventually).

• If a file is non-UTF8, we should try the repository's "Encoding" as a default (or maybe just remove this feature).

Junk I'm about to break in Diffusion (but plan to restore):

I don't currently plan to pursue this.

We now support emoji; we might support stickers at some point. If we did, I'd expect them to use the autocomplete element (which I think is in a relatively good place for emoji), not actually be invoked with :P, ^-^, etc.

Since there's no known actual problem with this today, I don't plan to fix it.

This is well-suited to a third-party extension, particularly after T5055.

I don't currently plan to pursue this.

I don't currently plan to pursue this.

I don't currently plan to pursue this.

I don't currently plan to support this.

I don't currently plan to support this. You may be able to add a rule to support something like <br /> with a Remarkup extension.

I don't currently plan to change the remaining edge case behaviors since I'm not sure they ever occur in the wild.

This seems largely resolved.

This request seems very niche, so I don't currently plan to pursue this. It may be possible to implement it as an extension.

I don't currently plan to pursue this.

This is unlikely to ever happen without stronger use cases for nested block-level elements.

See T13110 for some followups.

i met the same issue, and i found the root cause was the OpenSSH upstream issue.

This script can back-populate revision sizes that haven't been updated since D18832:

where I plan to explore the [----++ ] element