MonitoRSS VS Synapse

I love RSS. I take a bit of an unconventional approach and use Discord as my RSS reader. I run a self hosted instance of MonitoRSS (https://github.com/synzen/MonitoRSS). I have a server with just me and my bot instance and I tend to group my feeds into categories and channels (effectively creating a tab system per subscription or group of subscriptions). I have Discord installed on my laptop, phone, and desktop so this means that I can easily look at all my subscribed feeds wherever it's convenient for me. When I'm not set to "do not disturb", I even get push notifications on my devices when content is posted to feeds that go to channels I haven't muted. I think the only real downside of the setup is some days I am very busy and don't check the server that often, so I'll come back to a large backlog of things to read and I'll end up missing or under-appreciating some gems.

i have been using monitoRSS and its done well tbh

That bot is used in nearly 70 thousand servers, and is open source. You can probably trust it, the things its asking for (identify and guilds) are quite common with bot dashboards, so I wouldn't be too worried about it.

I remember the dev said that he had plans to implement that feature with this RSS bot but he doesn't have an ETA. At least according to a reply he made two months ago in that discord support channel. Otherwise it's a very fine RSS bot.

As long as the site supports RSS, you can use this bot called MonitoRSS. If for some reason, you'd like to try a different bot, I recommend top.gg for browsing for more options.

Monitor-RSS with rss-bridge Monitor-RSS allows me to filter RSS feeds obtained from rss-bridge with keywords and let's me embed them to discord. I mainly use xpath on rss-bridge to scrape sports news (fantasy football injuries) and add those feeds to Monitor-RSS that allows to filter them by player names or anything specific I am interested in. Sending those filtered feeds to Discord results in easy reading and manage them via discord tag or channel notifications. This way I get notified for stuff I am interested in and ignore anything not relevant 😎

And by using a bot like MonitoRSS you can get all updates within your discord server directly.

Overall porting content from heroku can be done with koyeb or other listed alternatives. ## References * https://github.com/synzen/MonitoRSS * https://blog.heroku.com/next-chapter

How does this compare to MonitoRSS?

I set up my own RSS feeds for a couple of things and use MonitoRSS to get feeds into channels.

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