Tangential - I have officially retired from Emacs(hand-off of maintenance of Elfeed recently) - https://nullprogram.com/blog/2026/04/26/

Single tenant(and single core) tiny VMs with OpenBSD's VMM hypervisor and confidential computing through AMD-SEV.

Nice! Had to lookup when one was last released, 7.3. https://www.openbsd.org/lyrics.html

How about F# support? Until then, happy to support Avalonia.

It won't happen, already on UWP you had to avoid specific F# code idioms that could generate MSIL that the .NET Native compiler wasn't happy with.

With WinRT on top of Win32, the .NET Native runtime support now lives in CsWinRT, where they also only have C# into account, not even VB as it used to be on UWP side.

There's also Crunch Scheme(from creator of Chicken): https://wiki.call-cc.org/eggref/6/crunch

This brings back painful yesteryear memories when consultants would push Microsoft Small Business Server for an on-prem all in one IT solution and charge extra to move to the cloud(colocation). A Linux-based alternative appeared named Clark Connect.

If he was "behind the fence", at most he would be a team sergeant or maybe even assistant team sergeant. Talking 4-6 members max.

Continue to be impressed with the quality and quantity of work Mauro is putting out for this project. Transition to management with JMAP replacing REST and TOML for configuration is major and glad to see the decision made to do it.

TempleOS, is that you?

Created to work with Stalwart Mail server but from the FAQ:

(Does Bulwark work with non-Stalwart mail servers? Bulwark communicates via the JMAP protocol (RFC 8620). Any mail server that implements JMAP should work. However, Stalwart is the primary tested backend and offers the best integration, including calendar, contacts, admin panel, and plugin management support. You can also configure custom JMAP server endpoints directly from the login page."

Seems like a neat project, but outside of Fastmail and selfhosting your own mailserver, there has not been much traction for JMAP over the decade it has been around.

IMAP meanwhile is still nearly universally supported, and there are many independent mail providers that will host your inbox for a low cost without being locked into paying Fastmail or running your own infrastructure.

JMAP for mail, contacts, calendar and files landed in Stalwart mail server about 5-6 months ago. In a discussion here on HN( https://news.ycombinator.com/item?id=45672336 ), a member( @solarkraft ) floated the idea of using Stawart as the "server" implementation of JMAP and using something like mbsync to sync IMAP from their mail provider. And build a client on top of this Stalwart "server." This might very well be the client to serve as a way to use the new JMAP protocols and not self-host.

> floated the idea of using Stawart as the "server" implementation of JMAP and using something like mbsync to sync IMAP from their mail provider. And build a client on top of this Stalwart "server."

That really does not seem like a workable solution. It would probably be brittle, require double the storage, require mapping of accounts and and credentials, would not account for caldav/carddav, etc.

If JMAP is to take off we need proper clients, servers and bridges. I'm not sure we even have one proper OSS implementation for each.