I'm working on ffl (https://github.com/nuwainfo/ffl), an Actually Portable Executable (APE) that turns any file or folder into a secure P2P HTTPS link via WebRTC.
Like llamafile, it's built on Cosmopolitan Libc. Getting the full Python stack + WebRTC to run as a single APE binary was incredibly tricky to pull off, but the result is super convenient. I mainly built it to solve the pain of moving large files (logs, DB dumps) in and out of containers—now it's just one command.
The repo has a demo showing a round-trip transfer between Windows (x64) and Android (arm64) using the same binary. I hope you give it a try!
I built a file sharing CLI called ffl which is also an APE built on Cosmopolitan Libc, just like llamafile.
Since llamafiles can be quite large (multi-GB), I built ffl to help 'ship' these single-file binaries easily across different OSs using WebRTC. It feels natural to pair an APE transfer tool with APE AI models.
I am working on FastFileLink (https://fastfilelink.com/), yet another file-sharing CLI/app that uses WebRTC for P2P transfer but exposes HTTPS links, making it compatible with browsers and tools like curl/wget.
It's ~90% production-ready. We use it internally to move files between containers and hosts (especially when volumes aren't mounted), and for WFH employees to exchange large files without a relay server.
For huge files, there's resumable upload to our infra-backed server — fast global downloads included.
The CLI will also support receiving files via WebRTC, but that feature hasn't been released yet. It is open source (https://github.com/nuwainfo/ffl), but the README hasn't been updated yet and the code is not synced with the latest version (working on these).
Another production-used tool I'm working on is
MailTrigger (https://www.mailtrigger.net/) — a programmable SMTP server that turns any email into a message on LINE, Slack, Teams, Telegram, SMS, or basically anything.
If your app can send email, it can trigger multi-channel notifications with zero extra code.
Think of it as “SMTP to Anything,” or an email-native IFTTT/Zapier.
It supports JS and WASM for preprocessing, routing, and automation — you can write custom logic, auto-reply with LLM-generated messages, or forward alerts intelligently.
We use it for price drop alerts, server health monitoring, and integrations with Jenkins/Sentry to push incidents to our DevOps Telegram channel.
Also experimenting with LLM-assisted rule creation: you can define notification logic in natural language instead of writing code — for example, auto-reply with an LLM-generated joke or handle customer support queries dynamically.
Docs are more complete than the website (which is still evolving), and the pricing page is currently a placeholder.
Already running in production for us and a few early adopters.
You might want to check out MailTrigger (https://www.mailtrigger.net/) — it's a programmable SMTP server that can even call an LLM before sending emails, so everything you listed is technically doable: blacklists/whitelists, phishing detection, spam rollups, virus scans, link previews, etc.
It’s not directly related to the MS email stack, but if you're self-hosting and looking for a flexible, programmable layer in front of your mail server, it could be a good fit. It’s still under development (though already running in production for my own company and a few early adopters), and the pricing page is just a placeholder for now. But the docs are public, and I believe it can cover what you're aiming for.
One thing to note: while the website mainly talks about multi-channel notifications, MailTrigger is actually more like IFTTT or Zapier, but specialized for email — when a message arrives, it can trigger smart, programmable actions.
You can turn your existing email system into an IFTTT-style automation engine. It supports JS and WASM for preprocessing and routing, so you could, for example, auto-reply with an LLM-generated joke or handle customer support queries dynamically.
The website might not fully reflect this yet, but the docs are more complete and show what’s possible.
I'm working on MailTrigger — a customizable SMTP server that turns any email notification into a message on platforms like LINE, Slack, Microsoft Teams, Telegram, SMS, or pretty much anything else.
The idea is simple: if your app can send an email, it can trigger notifications across multiple channels with no extra coding. Think of it as "SMTP Server to Anything."
One of the cool parts is MailTrigger supports WebAssembly (WASM), so you can customize your own notification logic and automate workflows. I’ve used it for tasks like monitoring internal systems, forwarding alerts to different chat platforms, and even adding basic decision-making logic before sending notifications. It’s been a huge time saver.
I’ve also experimented with using LLMs to assist in rule creation — you can configure notification rules using natural language instead of writing manual code. It’s like giving your infrastructure a smarter way to handle incidents.
At my company, I’m using MailTrigger for real-time price drop alerts and server health monitoring, along with integrations like Jenkins and Sentry to forward alerts to our DevOps Telegram channel.
It’s still super early, and things like the docs, pricing, and overall user experience are definitely a work in progress. But I’m iterating quickly and would love to hear feedback from this community!
Sounds like you are making fast progress. Congrats!
I wanted to check it out but using Brave Browser and Chrome on a Samsung A54 it took 10s+ to load. After a few seconds the spinner loaded, then the progress bar moved and then restarted and then loaded.
Thanks for checking it out and for the feedback — really appreciate it!
I’m sorry the loading took so long. I’m not entirely sure if the issue was with the main site or the Join Waiting List process. We’ll definitely investigate and get it fixed as soon as possible.
If it turns out that the waiting list form was the problem and you'd still like to join, feel free to shoot me an email at bear@nuwainfo.com — I'd be happy to add you directly!
Thanks again for flagging this. Your feedback means a lot and will help us improve!
Right now, each MailTrigger mailbox requires SMTP authentication (username/password), so unless someone has the correct credentials, they can’t inject messages. That gives us a basic layer of protection against spoofing from the SMTP side.
For forwarded emails (e.g. from Gmail), we do validate SPF, DKIM, and DMARC on inbound messages. Each mailbox acts as a gated endpoint — only verified senders are allowed to trigger actions.
As for pricing — you nailed it, we’re still working that out. We have a few rough ideas, but I’d genuinely love to hear what kind of pricing model would feel fair or sustainable to you.
Would you lean towards usage-based (like number of messages/month), flat monthly per mailbox, or something else entirely? Have you seen pricing models you liked (or didn’t) in similar tools like Zapier or SendGrid?
Your feedback’s incredibly helpful at this stage — really appreciate it!
You might say: but that won't change who actually wins on the private board. However when you use techniques like that you can get identify data in the test set and use it for training. It does help a some, but not a lot. The payout isn't very large for the over fitters (maybe 10-20% of payout).
Another negative is regular competitors also have no idea how they are actually doing compared to others. The leaderboard has impossible (for market data) logloss values of 0.2 - 0.4, sometimes even 0.00. They keep trying to fix it, but they haven't in about 2 months.
Procrastination is a psychological problem, not a planning problem. Seems like you solve a problem in a wrong way, or you promote your product in a wrong direction.
You can say it is a combination of kanban, time tracker, project management or even habitica...blahblahblah, but it is just combination of functions not solving any procrastination problem at all.
Yes it is, but some planning tools can help you to break out of it as long as you don't end up using your planning as procrastination.
I've known a few people that were chronic procrastinators I even had some issues with that myself, I eventually outgrew it by using a bit of additional organization but without "religious" adherence to any method.
For some a more strict method which they follow daily works, for others I've seen it can make things worse they use 2-3 planners/organizers and just spend the time they would normally be wasting on procrastination by procrastinating via planning.
>Procrastination is a psychological problem, not a planning problem.
This is one of those "circular cause and consequence" things.. our psychological state is a function with side effects changing the events in our lives, which are themselves functions with side effects changing our psychological state.
In other words, psychological problems can also be viewed as symptoms or consequences of something happening in the lives we live in the physical world which are shaped by the way we plan them.
If it is indeed circular, the question becomes not which one came first but which one is easiest to change and what you can make of both. This is akin to postponing the chicken/egg question, making poached eggs and chicken thighs for lunch, and thinking about the question while you eat.
I think phusion's base images solution is overkill (its own init written in python3 and force users to use runit). It will be great if I can use systemd inside container (I am a CentOS 7 user, use systemd is quite easy for most packages e.g.: yum install httpd; systemctl start httpd), but it requires --privileged. Now I am considering s6 as solution based on this article: http://blog.tutum.co/2014/12/02/docker-and-s6-my-new-favorit...
But I think it will be the best if docker solve this problem itself, then I can freely use my familiar tools like monit.
My ff4 also crashes "EVERYDAY", sometimes "EVERYMINUTE", I seriously consider to switch to Chrome, but I still use it even it always crashes.
Here is my about:crashes:
xpcom_runtime_abort(###!!! ABORT: Main-thread-only object used off the main thread: file e:/builds/moz2_slave/rel-2.0-w32-bld/build/xpcom/base/nsCycleCollector.cpp, line 1195)
Thank you very much. What kind of advice would you give if I am trying to build another http://www.korekt.me/? I think if we can find some solutions for this site, we will find some general solutions.
(or the problem might be that proofreading service not really frustrates people?)
Like llamafile, it's built on Cosmopolitan Libc. Getting the full Python stack + WebRTC to run as a single APE binary was incredibly tricky to pull off, but the result is super convenient. I mainly built it to solve the pain of moving large files (logs, DB dumps) in and out of containers—now it's just one command.
The repo has a demo showing a round-trip transfer between Windows (x64) and Android (arm64) using the same binary. I hope you give it a try!
reply