Skip to content

Planned sunset of NTFY plugin

Pinned Announcements
7 3 1.8k 1
  • Those of you who regularly visit the NodeBB forums have problably noticed this

    https://community.nodebb.org/topic/18279/native-push-notifications-support-for-nodebb

    And as a result, this new commit

    https://github.com/NodeBB/NodeBB/commit/aa060d31d130cd54d18cd8dc2f25ba7de58f4fea

    @julian now has the native push notifications working, and as a result, Sudonix now has them also - see screenshot of how to enable this feature here

    33abbae1-28b3-4f05-b462-e19eccc8aaf9-image.png

    As you can see, you need to enable the notification before it will work. There is a test button located underneath the slider switch (although not present in this screenshot) and this will enable you to test to make sure it is working.

    Quoting Julian

    I’m particularly excited about this new development because it opens the door for richer integration between NodeBB and the push notifications themselves.

    With (probably) every iteration prior, when you clicked on the notification, it likely opened a new window. With direct access to the Push API and service worker, we can now accurately detect whether the site is already open (in another tab), and open it there.

    In the future, we’ll also be able to add in things like icons, pictures, and custom actions, right from the notification itself.

    One particular nice-to-have is the ability to update notifications. Being able to merge notifications (like they already do in NodeBB) or potentially rescind notifications would be a nice step forward in usability as well.

    This works very well in my testing - however, if you use NordVPN, it does not work at all unless you disable the VPN. I have an open ticket with them presently to see if there is in fact any workaround.

    I have taken the decision to now disable nodebb-plugin-ntfy as with the 4.0 train, this plugin is considered legacy.

  • phenomlabundefined phenomlab pinned this topic on
  • Those of you who regularly visit the NodeBB forums have problably noticed this

    https://community.nodebb.org/topic/18279/native-push-notifications-support-for-nodebb

    And as a result, this new commit

    https://github.com/NodeBB/NodeBB/commit/aa060d31d130cd54d18cd8dc2f25ba7de58f4fea

    @julian now has the native push notifications working, and as a result, Sudonix now has them also - see screenshot of how to enable this feature here

    33abbae1-28b3-4f05-b462-e19eccc8aaf9-image.png

    As you can see, you need to enable the notification before it will work. There is a test button located underneath the slider switch (although not present in this screenshot) and this will enable you to test to make sure it is working.

    Quoting Julian

    I’m particularly excited about this new development because it opens the door for richer integration between NodeBB and the push notifications themselves.

    With (probably) every iteration prior, when you clicked on the notification, it likely opened a new window. With direct access to the Push API and service worker, we can now accurately detect whether the site is already open (in another tab), and open it there.

    In the future, we’ll also be able to add in things like icons, pictures, and custom actions, right from the notification itself.

    One particular nice-to-have is the ability to update notifications. Being able to merge notifications (like they already do in NodeBB) or potentially rescind notifications would be a nice step forward in usability as well.

    This works very well in my testing - however, if you use NordVPN, it does not work at all unless you disable the VPN. I have an open ticket with them presently to see if there is in fact any workaround.

    I have taken the decision to now disable nodebb-plugin-ntfy as with the 4.0 train, this plugin is considered legacy.

    @phenomlab That is awesome that they integrated that feature. Now it will be even more awesome if they fix it so it will go through your VPN.

  • @phenomlab That is awesome that they integrated that feature. Now it will be even more awesome if they fix it so it will go through your VPN.

    @Madchatthew yes, but this isn’t a NodeBB issue - more of a NordVPN one. And the response I got from them was lacklustre to say the least.

    We’ll do our best to help, but, to solve this faster, we need some additional information. Can you please let us know:

    The device and operating system you are using with our service (Windows/Android/macOS/iOS/Linux);

    The country you are currently in;

    If you’re using the >latest version< of our application and if not - have you tried updating the application;

    Your Internet Service Provider and the network that you are connecting from (home/public);

    If you’re getting any error message(s), please attach a >screenshot< to the reply;

    Have you tried any troubleshooting steps so far? If you have, could you clarify which ones?

    Let us know if you’re using any type of antivirus, ad blocker, or different VPN software alongside NordVPN, as they might be interfering with our service.

    Looking forward to hearing from you!

  • @Madchatthew yes, but this isn’t a NodeBB issue - more of a NordVPN one. And the response I got from them was lacklustre to say the least.

    We’ll do our best to help, but, to solve this faster, we need some additional information. Can you please let us know:

    The device and operating system you are using with our service (Windows/Android/macOS/iOS/Linux);

    The country you are currently in;

    If you’re using the >latest version< of our application and if not - have you tried updating the application;

    Your Internet Service Provider and the network that you are connecting from (home/public);

    If you’re getting any error message(s), please attach a >screenshot< to the reply;

    Have you tried any troubleshooting steps so far? If you have, could you clarify which ones?

    Let us know if you’re using any type of antivirus, ad blocker, or different VPN software alongside NordVPN, as they might be interfering with our service.

    Looking forward to hearing from you!

    @phenomlab Ooohhh you got the ole classic response of tell us everything about your system and internet access along with when everything was made and who programmed and designed it and after we have all of that information it won’t be our software but whatever software you are using or your internet connection because your grandma’s third cousins borther’s aunt’s nephew didn’t put enough gas in the car and then had to thumb it home to get the gas container and go to the gas station to fill it up and by the time they get back to the car to fill the tank, someone had come along and jacked the car up and stole the tires and took the sparkplugs and cables out along with the carberater and oil filter.

    Cause heaven forbid they just ask what protocol are you using to send those notifications and lets check our software to see why it might be doing that so we can change the function and make it work.

  • @phenomlab Ooohhh you got the ole classic response of tell us everything about your system and internet access along with when everything was made and who programmed and designed it and after we have all of that information it won’t be our software but whatever software you are using or your internet connection because your grandma’s third cousins borther’s aunt’s nephew didn’t put enough gas in the car and then had to thumb it home to get the gas container and go to the gas station to fill it up and by the time they get back to the car to fill the tank, someone had come along and jacked the car up and stole the tires and took the sparkplugs and cables out along with the carberater and oil filter.

    Cause heaven forbid they just ask what protocol are you using to send those notifications and lets check our software to see why it might be doing that so we can change the function and make it work.

    @Madchatthew Brilliant. This really made me chuckle. So true, and definitely the default response.

  • phenomlabundefined phenomlab referenced this topic on
  • Those of you who regularly visit the NodeBB forums have problably noticed this

    https://community.nodebb.org/topic/18279/native-push-notifications-support-for-nodebb

    And as a result, this new commit

    https://github.com/NodeBB/NodeBB/commit/aa060d31d130cd54d18cd8dc2f25ba7de58f4fea

    @julian now has the native push notifications working, and as a result, Sudonix now has them also - see screenshot of how to enable this feature here

    33abbae1-28b3-4f05-b462-e19eccc8aaf9-image.png

    As you can see, you need to enable the notification before it will work. There is a test button located underneath the slider switch (although not present in this screenshot) and this will enable you to test to make sure it is working.

    Quoting Julian

    I’m particularly excited about this new development because it opens the door for richer integration between NodeBB and the push notifications themselves.

    With (probably) every iteration prior, when you clicked on the notification, it likely opened a new window. With direct access to the Push API and service worker, we can now accurately detect whether the site is already open (in another tab), and open it there.

    In the future, we’ll also be able to add in things like icons, pictures, and custom actions, right from the notification itself.

    One particular nice-to-have is the ability to update notifications. Being able to merge notifications (like they already do in NodeBB) or potentially rescind notifications would be a nice step forward in usability as well.

    This works very well in my testing - however, if you use NordVPN, it does not work at all unless you disable the VPN. I have an open ticket with them presently to see if there is in fact any workaround.

    I have taken the decision to now disable nodebb-plugin-ntfy as with the 4.0 train, this plugin is considered legacy.

    @phenomlab said in Planned sunset of NTFY plugin:

    Those of you who regularly visit the NodeBB forums have problably noticed this

    Interesting my friend, long may NodeBB & Sudonix continue to thrive 😬.

  • I’ve noticed that I’m the only one subscribed to the push notifications on this site. If you were using NTFY previously, and have noticed that you’ve not had any alerts for a while, it’s because this feature has been disabled.

    You’ll now need to use the push notification to replace NTFY as mentioned in the first post.


Related Topics
  • Threaded post support for NodeBB

    Let's Build It threading nodebb
    146
    3
    50 Votes
    146 Posts
    69k Views
    Updated git for above change https://github.com/phenomlab/nodebb-harmony-threading/commit/14a4e277521d83d219065ffb14154fd5f5cfac69
  • SEO and Nodebb

    Performance nodebb seo
    2
    2 Votes
    2 Posts
    971 Views
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • Can you adjust Admin settings on your NodeBB?

    Bugs nodebb
    5
    0 Votes
    5 Posts
    1k Views
    @Panda as, yes, now I understand and that makes 100% sense. It means those who get down voted can still have an opinion and use common services. And yes, you’re right. Rather than down vote, just ignore if you don’t agree.
  • NodeBB: updating Admin details not working

    Solved Configure nodebb admin
    17
    3 Votes
    17 Posts
    3k Views
    @mventures Ok. No issues
  • Unable to install User Level plugin

    Solved Announcements
    6
    1
    2 Votes
    6 Posts
    1k Views
    @Sampo2910 said in Ranking system revisited: Yes that worked Good @Sampo2910 said in Ranking system revisited: How to go about getting the ‘labels’ or is that an automatic thing within the plugin. That should be automatic as you get upvoted etc. Best way to test is to create another user, login with that session using an incognito browser, and upvote each other with test posts
  • fading in /tags page

    Solved Customisation nodebb
    32
    1
    30 Votes
    32 Posts
    9k Views
    Fix working perfectly
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    11k Views
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 1645128773854-47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • [NodeBB] username cards

    Solved Customisation nodebb
    8
    5 Votes
    8 Posts
    2k Views
    @phenomlab Aha…nice to know. As always thank you for the reply and information.