pingme VS Synapse

https://github.com/kha7iq/pingme supports various services (easy to deploy being a golang binary)

Three q's: What problem are you solving? Who has this problem? What is your solution? MVPs, Proto types, and Side Projects. 1. https://notifier.so/ - Generate leads and market your product using social listening -- https://twitter.com/notifier\_so 2. www.paytable.io - Membership platform for Airtable curators -- https://twitter.com/J\_\_Rosen 3. https://apps.apple.com/us/app/ratethi... -- Get inspired by your friends -- No social 4. https://mylinks.ai/ - Build beautiful link-in-bio pages made for creators -- no social Art, Music, Misc etc. 5 The Way We Thought It Would Be - By Kate Greenwood https://www.amazon.com/Way-We-Thought... Github projects 6. https://github.com/viveknathani/maketest 7. https://github.com/kha7iq/pingme Ideas, discussions, other etc. Want me to review your side project, MVP, or creation? Paste links to your projects in the comments for upcoming episodes.

In this article, we will illustrate how to configure and send messages to multiple platforms from your scripts. A notification can be setup based on success or failure of a task or if you want to have an alert when a certain condition is meet. This article uses a small binary PingMe to send this notification, you can find more information about it on github.

Updated regarding the app. A new version has been released v0.1.2 with support for pushover service. Thanks to contribution from community member.

What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.

Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).

If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.

some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...

Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.

This is honestly really disappointing behaviour from a platform owner.

[0]: https://github.com/matrix-org/synapse/issues/14481

> That doesn't make this situation any less bad to the rest of the community.

How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.

You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.

And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.

The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.

[0]: https://github.com/matrix-org/synapse/graphs/contributors