novu VS telescope

I'll guide you on how to swiftly build an In-App Notification system for your next app using Novu and the Dev.to API. While it might not exactly resemble the system mentioned above, it'll have many similarities.

PR for Reference: https://github.com/novuhq/novu/pull/5187

Remember, this is just a glimpse into Novu's broad range of functionalities. Hopefully, you've gained a solid understanding of the core workflow. If you're interested in learning more, I highly recommend exploring the project's GitHub repository.

You can find the full changelog on GitHub.

feat(application-generic, shared): Add Rate Limiting feature flag in https://github.com/novuhq/novu/pull/4667

Novu- The open-source notification infrastructure for developers. Simple components and APIs for managing all communication channels in one place.

I don't think anyone here has recommended novu, and I quite frankly think it's brilliant. It might be worth having a look.

Run Migration Script for Creating primary and priority Fields: You can access the migration script for creating primary and priority fields by clicking here.

It all starts with an old 400 error that was occurring in Telescope for a while now, first documented here.

Sattelite for the back end

There are a few places to start with this, one is that we have an issue in Telescope that relates to what I think is the session no longer existing in certain situations that results in a 400. This will give me an opportunity to take a look at Telescopes auth flow. I still am kind of unfamiliar with Telescope despite having been in the last OSD course. I know that we use passport SAML in Telescope however and in the new project we will use a different library called SAMLIFY.

The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.

As a good well-established project, Telescope provides a great environment setup guide, which covers most use cases.

It's been a year since I was supposed to work on Telescope for a class. When the war in Ukraine started in February 24th, 2022, I almost fully stopped contributing. Now, this year I am trying to do more, even though it's not my class anymore. Because I wish that I did more back then.

This week, I decided to setup Telescope locally. I had previously contributed to telescope and had set it up already. However, I faced some problems starting it up locally after a shutdown and startup sequence. This was hard to debug since there was no error message, just containers on docker would not start up even after waiting for several minutes. These problems would fix after a restart or just randomly after a few tries. So, I decided to go through the setup again.

Task This week, I try to revisit my setup for running the Telescope project, a single page website that aggregates blog posts.

This week, I finished implementing the feature for filtering out irrelevant feed URLs. Previously, I had added a function for the filtering but had to write the test for it.

The two PRs(1 2) mentioned last time were merged without a hitch. For the one that's about parsing Twitch channel feed URL, the maintainer and I agreed that there should be a follow-up issue opened to expand it to YouTube Channel(s). They also found another bug in the sign-up that should exist as its own issue about the RSS feed URL(s) having incorrect domain. For details about them, please see my last post.