简要描述问题

windows10，.net组件正常，能够正常运行冰使用Shadowsocks 4.1.10，
只是最近朋友给我的ss节点，其密码都是64位的字符串，填入Shadowsocks 4.1.10，客户端中，结果连接不上，节点的加密方式为chacha20-ietf-poly1305。朋友说是这个认证方式是 shadowsocks-libev 引入的。

用朋友给我的一个命令行程序（[demon.zip]https://github.com/shadowsocks/shadowsocks-windows/files/5012306/demon.zip)
）能够连上。

shadowsocks-windows将来能支持这种类型的节点嘛？

Suggested code to add to Fields.xaml

<smtx:XamlDisplay
Grid.Row="1"
Grid.Column="4"
UniqueKey="fields_30">

            <StackPanel>
                <CheckBox
                    x:Name="MaterialDesignOutlinedPasswordFieldTextCountComboBox"
                    Content="View Text Input Count"/>

Based on findings from the TechEmpower perf work. We probably want a very high default which can then be tuned down if the application wants to reduce maximum memory at the expense of speed.

The original issue was reported in dotnet/performance#1701:

// Benchmark Process Environment Information:
// Runtime=.NET 6.0.0 (6.0.21.11801), X64 RyuJIT
// GC=Concurrent Workstation
// Job: Job-AQTFSE(PowerPlanMode=00000000-0000-0000-0000-000000000000, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1)

OverheadJitting 

Is your feature request related to a problem? Please describe.

We often rename the Display Name of a Content Type and make a mistake afterward on it's technical name.
It is not displayed on the Content Type edit form anywhere else than looking at it's element created in the Parts section to reorder it's fields.

Describe the solution you'd like

I think we should display the Display Na

Expected Behavior

Lean should include a basic template for every security type.

Actual Behavior

Missing BasicTemplateFutureOptionsAlgorithm

Potential Solution

Add C# and Py BasicTemplateFutureOptionsAlgorithm. Since it's an Options algorithm, it should include Greeks and Implied Volatility. I think this GH issue might lead to others, because of the setting of `Volatilit