[snowflaxxx]

That’s fair criticism of the current implementation.

The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport.

GitHub happens to provide one out of the box, which makes the proof of concept extremely easy to try.

If I need to run databases, message brokers, servers and monitoring just to send my mom “please cook macaroni”, I’ve already lost interest.

[boomlinde]

> The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport.

It's sharing this advantage with every other free, third party managed communication service I can choose to depend on. It's also sharing the weakness that it puts me at the mercy of whatever third party I am relying on. It introduces a new weakness in that the third party being relied on here never intended for their infrastructure to be used in this way.

> If I need to run databases, message brokers, servers and monitoring just to send my mom “please cook macaroni”, I’ve already lost interest.

So don't. To that end, what specific problem does this address that other free third party communication service providers don't? My mother will have seen my email or SMS before you have instructed your mother on how to join GitHub and get an API token. We don't even need to agree on or stick to a provider.

[Hugsbox]

I don't think this was meant to be taken as seriously as you seem to be taking it

[boomlinde]

I'm directly addressing arguments made by the person I responded to. I'm not going to be taking you seriously, because you are not.

[snowflaxxx]

Email and SMS are faster. Also monitored, moderated, and mined.

Macaroni doesn't fix speed. It fixes who holds the keys — and who gets sued. That's the point.

[boomlinde]

If I use Outlook 365, Microsoft holds the keys. If I use Github, Microsoft holds the keys.