With his “Island of Strangers” speech Starmer was doing Farage’s work for him.

Truth

I think it might be trying to say something smart about “we” vs. “i” in a way that is applicable to culture conflicts, ai, etc.

So I’m going to stick to it while it develops. Much like Severance, I hope it will grow as its dramatic conflict develops.

But I’m not in the “genius” camp, yet.

This is why I left Labour and joined the Greens. The first step on that path was the “island of strangers” speech. Starmer should have resigned over that.

I assume they are not all gone yet.

This is how revolutions start: one day it’s “let them eat cocoa substitute” the next day folks are knitting whilst the guillotine falls.

Full release notes are here: github.com/BrighterComm.... Updated documentation for V10 is in progress.

Simplified Configuration: We have simplified the configuration, including renaming obscure methods. This needs more work in future releases.

Nullability: We have enabled nullable reference types.

Scheduled Requests/Messaging: We now support integration with schedulers such as Quartz.NET, Hangfire, or AWS Scheduler. This can be used with requests or messages. We use this support to allow "Requeue with Delay" where the messaging protocol does not support it.

Reactor and Proactor: We have made considerable under-the-hood improvements to synchronous and asynchronous message pumps in your consumer. The asynchronous pipeline is now end-to-end.

Request Context Improvements: You can now inject the RequestContext more easily into a pipeline. The RequestContext now supports the OriginatingMessage for subscriptions to queues or streams.

Agreement Dispatcher: We support a callback to determine the handler to dispatch a Command or Event to. Previously, we matched the request and the handler based on the request type. You can now add a callback to dynamically determine the handler from the request and context.

Dynamic Message Deserialization: Previously, we required that you use a DataType Channel (one type per channel). Whilst this remains the default, you can now provide a callback to determine the type from the message itself, such as via the Cloud Events type, before deserializing.

Default Message Mappers: There is no need to provide a mapper if your goal is to serialize your body as JSON. You can use a default mapper. You can create your own default mapper for other formats. You only need explicit mappers for complex transform pipelines.

Open Telemetry: We now support the OpenTelemetry Semantic Conventions for Messaging. This will mean that you have different traces to V9, where the OTel conventions were Brighter's own.

Cloud Events:We now have full support for Cloud Events headers; you can set values in your Publication and have them reflected on messages.