At the beginning of April, I released a new Telegram message parser, which I re-wrote from scratch. It has better support of various Telegram message types, easily extendable, and more thoroughly tested. For you, it means that your Telegram RSS feeds would have better message formatting and less "Notifier doesn’t support such message type" errors. In case you notice some bug, please drop me a line at firstname.lastname@example.org.
I’ve added a comment form to blog posts and the FAQ page. Feel free post comments and ask questions!
I’ve made some internal improvements and added more tests. So in general Notifier should be more stable now.
Also, Notifier.in got a new logo ↑. Thanks to Evgeny Filatov for creating it!
TL;DR: From April 12, 1 PM (UTC) until April 13, 9 AM the integration RSS feeds missed some messages.
On Friday, April 12 around 1 PM (UTC) I accidentally ran an update script in the wrong directory, which resulted in deleting some files with messages.
Fortunately, all files are backed up every night, so I downloaded the latest backup and started restoring the deleted files. I also temporarily disabled all integration RSS feeds because without the missing files they couldn't be rendered correctly. Since I didn't know which files exactly have been deleted, I decided to restore all files from the backup. It took about 4 hours, so by 5:30 PM all files, except the ones created after the latest backup has been made, have been restored. At this point, I also re-activated previously disabled RSS feeds.
After checking which files are still missing it turned out that they're all email messages. So I started restoring them semi-manually from Mailgun, which I use for sending and receving emails. By 9 AM, Saturday (April 13) I was able to restore them all.
What I did to prevent such data losses in the future:
I'm sorry for the inconvenience! Let me know if you have got any questions.
This month Notifier turned 6 months old 🎉 Thanks for using and supporting it! Here are some nice features and improvements that I added in February.
Since the majority of the customers use only RSS integrations I decided to focus more on them. So I'm planning to add more content sources for RSS integrations and to improve the current integrations. Let me know which content sources you'd like to have.
On the other side, I removed the ability to add new non-RSS integrations (e.g. sending notifications to email, webhooks, or Slack). The existing ones will be supported until 1st of May. After that they'll be shut down. If you'd like to continue using them I'd suggest switching to Zapier, which supports a lot of different integrations. Drop me a line if you need help transferring your integrations there.
I added WebSub protocol (former PubSubHubBub) support to RSS feeds. If your RSS reader supports that protocol (e.g. Feedly, Feedbin) new RSS items would appear in the reader immediately.
I also reduced delay in how fast Telegram messages appear in your RSS feeds after they have been posted to a Telegram channel.
Telegram messages in RSS feeds are linked now to their original pages on t.me. So if you'd like to open a Telegram message in your browser or share its URL just click on its title in your RSS reader.
Email messages in RSS feeds have now its sender set. Most RSS readers display it beneath the title. Here is an example from Feedly:
I launched the paid plan for 4 €/month. It allows you to get up to 20,000 notifications per month and add Telegram integrations. More details on the pricing page.
The free plan will remain as well. It allows you to get up to 100 notifications per month. Unfortunately, due to Telegram limitations, I can't support Telegram integration for free anymore. In one week (on January 25) the existing Telegram integrations will be deactivated for accounts without the paid plan.
I also created a page with personal integrations list.
In case you don't see some of your integrations on that page you could add it here.
For RSS integrations you could click on the RSS feed heading in your RSS reader or open URL from the RSS feed's