Günther Foidl

> We are using .net 6 currently. That's interesting, because until .NET 7 QUIC was only used internally for HTTP/3. So I wonder where the (blocked) traffic comes from. MQTT...

> Are you sure that setting is not DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT ? Yes, as HTTP/2 has nothing to do with QUIC. > MQTT doesnt use QUIC at all? At least the implementation...

Same question in https://github.com/dotnet/MQTTnet/discussions/1752 (we should only have one place that is followed along).

REST implies HTTP-based. Is gRPC also considered? I don't know what will be better for usage, but I see advantage for gRPC as a strong contract of the API can...

> suggest the following syntax: `session.Events.AnonymizeStream(streamId);` Do you suggest that the anonymizing happens when requested under GDPR? So plain information in normal use, and when requested the stream is anonymized?...

You are right with > which leads me to believe many other developers will end in a similar position and that there may be (lots) of data already in streams,...

This looks good 👍🏻

Should there be a different exception be thrown? I mean a NRE alludes a bug (here within Weasel) which isn't the case. Maybe wrap the NRE in custom exception that...

Unfortunately this doesn't work anymore. `--resultxml` ([Reference](https://github.com/nunit/dotnet-test-nunit/blob/1f4e95e66aa3394d55272143a456f685c9b7b423/src/dotnet-test-nunit/CommandLineOptions.cs#L270)) doesn't work neither. It is hard to maintain the overview by all the recent changes in dotnet core (project.json -> MsBuild amongst others),...

This would make sense, especially as there is https://github.com/serilog/serilog-sinks-eventlog/blob/dac4ef3e2fa3ce4d389c15f22c7141430791ffb0/src/Serilog.Sinks.EventLog/LoggerConfigurationEventLogExtensions.cs#L68-L71