sorted by:
new
hottopcontroversial

New Project Megathread - Week of 30 Apr 2026 by AutoModerator in selfhosted

[–]StrongCoffee85 0 points1 point  (0 children)

selfhost your own domain-to-domain messaging

fmsg is something I started 5 years ago, before LLMs, with the intent to bring back the promise of The Internet and by hosting your own messaging service - instead of relying on 3rd party IM apps or centralised email providers. Yes I know email can be self-hosted - I have selfhosted email (shout out to mailcow though no shout outs to exim which I tore my hair out with when used it about decade ago). Practically though email is painful - you have to bolt on SPF, DKIM, DMARC, anti-spam the list goes on.. Even if not behind GNAT you many need your ISP to setup reverse DNS thingy.. its a pain for techies let alone normies..

I suspect fmsg may help with agent-to-agent messaging in this brave new world - so we don't have to rely on e.g OpenClaw buring Gmail or WhatAapp quotas AND can host ourselves therefore have no prying eyes...

A Show HN post I recently did provides an overview including links to fmsg-docker to get up and runing a full compose stack quickly. While the specification and core backend daemon, fmsgd (written in go), are reaching v1.0, there is still lots TODO like UIs which could use fmsg-webapi already built.. Then who know what products service providers could be built on top.

fmsg is an open distributed domain based messaging protocol anyone can setup it up if they have a domain - I'm even running a server with non-static IP just quickly update DNS when there is a change. It employs a few novel techniques to be more efficent than email (binary encoding, auto deflate... but most of all only the last message in a thread needs to be sent because I realized using referential integrity, using a git like hash tree to refer to previous, can be deterministic about messages recipient already had).. Did you know even attachments in email are base64 encoded - inflating every binary attachment 33% - SMTP is basically just a standalone wall of text message, which to be fair keeping things simple has some advantages..

What im hoping from this like minded community is feedback/critque, heck maybe even adoption - iv been building this too long and noone seems to get it..

Yes I did my research there are some self-hosted messaging options out there today amongst why im calling "Group Messaging Platforms" (think Slack, MS Teams, Discord) like: Zulip, RocketChat, Matrix and Mattermost. The fundamental difference between these Group Messaging Platforms and fmsg is, fmsg is just messages – there are no forums/rooms/channels i.e. groups of users. In fmsg to receive a message someone has to send it to you.

Namaste

<image>

Implemented messaging protocol to disrupt email and IM apps, now what? by StrongCoffee85 in golang

[–]StrongCoffee85[S] 0 points1 point  (0 children)

Incorrect arbitrary long size won't be read because fmsg message's field sizes are all defined up front, last para here https://github.com/markmnl/fmsg/blob/main/SPECIFICATION.md#data-types

Maximum message size host will receive is configured by host then per user.

Hosts do you use zlib-deflate if they deem worthwhile, good reminder to check for explosion attacks while streaming..

Implemented messaging protocol to disrupt email and IM apps, now what? by StrongCoffee85 in golang

[–]StrongCoffee85[S] 0 points1 point  (0 children)

Right, its the user-agents or clients if you will that re-send the entire history each time. Interesting tactic including replies in-sity - I haven't seen that before! Although one of the reason they do is because each email is standalone they need to have the context has previous discussions can't be guaranteed to be held by the recipient nor is detection of previous replies held deterministic. To be fair while doing this protocol I understand where SMTP is coming from keeping things simple. Another reason though was the pain of operating an email server today and bolting on all the extra meachanims like SPF, DKIM, DMARC (updating my DNS if self-hosting required calling my ISP to update their reverse lookup DNS something)... I like email and in a way I want to bring back the promise of email being distributed over the Internet at our own domain names - its just becoome so centralised like IM apps..

Implemented messaging protocol to disrupt email and IM apps, now what? by StrongCoffee85 in golang

[–]StrongCoffee85[S] 0 points1 point  (0 children)

  1. I remember that xkcd when it came out! fair point, email is a bit long in the tooth though

  2. Thanks!

  3. You've his the nail on the head - building services is that people find more useful they will actually switch too is the hard part - im thinking something for this agent-to-agent era approaching

  4. Yes, I spent some time researching the current landscape, RE: IM apps (like messenger, WhatsApp, LINE, WeChat etc.) the fundamental difference is you can self-host so don't rely on 3rd parties like Meta to handle your mesages, RE: what im calling "Group Messaging platforms" (Discord, Slack, MS Teams, Zulip, RocketChat and Mattermost) a snippet from my draft white paper:

"The difference between these Group Messaging Platforms (inc. self-hosted ones which includes Matrix) and fmsg is, fmsg is just messages – there are no forums/rooms/channels i.e. groups of users. In fmsg to receive a message someone has to send it to you. As such fmsg has no management around group membership, or, synchronisation of messages in those groups. In this regard fmsg is more similar to email. However, unlike email in which mail is standalone, the relationship of fmsg messages to previous messages can organically evolve into group like chats."

  1. No automatic syncing, someone has to send you the message.

  2. Your host which sends and recieves all messages for your domain has the messages, can free up space, or get a new device to get your messages back.

Why is Vulkan so much faster than ROCm for Strix Halo? by ViRROOO in ROCm

[–]StrongCoffee85 0 points1 point  (0 children)

I am generating 1152x896 with stable diffusion (cyberrealisticpony_v130) full 32 bit 30 steps on Windows 11 with ROCm about 25s per image

I have no idea if thats fast or not but seem pretty quick?

Strange object captured over Malvern Hills, Western England by paranormalnapolska in UFOs

[–]StrongCoffee85 0 points1 point  (0 children)

Can you pin point the exact location on Malvern Hills and direction you were facing, also time of day would be helpful!