Skip to content

Planned sunset of NTFY plugin

Pinned Announcements
7 3 1.6k 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
  • 4 Votes
    3 Posts
    237 Views
    thanks @DownPW ! this is definitely very helpful.
  • Nodebb vs Wordpress vs Other

    General wordpress nodebb woocomerce business
    4
    2 Votes
    4 Posts
    441 Views
    PrestaShop + modules IA https://www.prestashop.com Magento https://developer.adobe.com/open/magento
  • ANNOUCEMENT: New NTFY Server

    Announcements ntfy push alerts
    9
    1
    7 Votes
    9 Posts
    2k Views
    @crazycells that’s as good a test as any
  • Header Menu After Upgrading V3.1.1

    Solved Customisation header nodebb
    2
    1
    2 Votes
    2 Posts
    750 Views
    @cagatay this relates to a change the css classes used for the brand header meaning it will now float to the left instead of right. If you’d like to retain the original behavior, you can add this css class [data-widget-area="brand-header"] { justify-content: end; display: flex; } Further information here https://community.nodebb.org/topic/17090/manual-build-a-custom-header-in-harmony/19?_=1684069325296
  • NodeBB: Privileges for the Announcement channel

    Solved Configure nodebb
    6
    1
    1 Votes
    6 Posts
    1k Views
    Up to you really
  • Changing Background on NodeBB

    Solved Customisation background image nodebb
    4
    0 Votes
    4 Posts
    1k Views
    @cagatay You’d target the body tag and use the below line of CSS background: url(/assets/customcss/backgrounds/default/default.png) no-repeat center center fixed; Obviously, you need to change the path to suit where your image is being stored. More info around the background property can be found here https://www.w3schools.com/cssref/css3_pr_background.php
  • Plugin reaction Bug

    Solved Customisation plugin nodebb reaction
    15
    1
    0 Votes
    15 Posts
    3k Views
    @DownPW That was going to be my next suggestion
  • [NODEBB] Help for my custom CSS

    Solved Customisation nodebb css bugfix
    237
    49 Votes
    237 Posts
    93k Views
    @baris said: You should change your selectors so it doesn’t look at the entire document. You probably only want to apply fancybox to stuff inside the #content element which is what changes when the user navigates around the page. So use $('#content a').... for your selectors then the forum logo in the header won’t be selected. I modified the JS Fancybox code now and this code and it seem better // --------------------------------------------- // Fancybox Media Reader (Without Website Logo) // --------------------------------------------- if (top.location.pathname !== '/login') { $(window).on('action:posts.loaded', function(data) { console.log("Polling DOM for lazyLoaded images to apply Fancybox"); $(document).ready(function() { $('#content a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); }); }); }); } if (top.location.pathname !== '/login') { $(document).ready(function() { $(window).on('action:ajaxify.end', function(data) { $('#content a').not('.logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); data.preventDefault() // Strip out the images contained inside blockquotes as this looks nasty :) $('#content blockquote img').remove(); }); Fancybox.bind( '#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]', { groupAll: true, } ); }); }); } // Chat fancybox - fires when chat module loaded and AJAX calls new chat $(document).ready(function() { $(window).on('action:chat.loaded', function(data) { // >>> Se limiter au contenu principal uniquement <<< $('#content img').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { var newHref = $(this).attr("src"); $(this).wrap("<a class='fancybox' href='" + newHref + "'/>"); $('#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]').addClass("noanimate"); data.preventDefault(); // Strip out the images contained inside blockquotes as this looks nasty :) $('#content blockquote img').remove(); }); Fancybox.bind( '#content a[href*=".jpg"], #content a[href*=".jpeg"], #content a[href*=".png"], #content a[href*=".gif"], #content a[href*=".webp"]', { groupAll: true, } ); }); }); For the logo, I must use overflow: visible !important; on [component="brand/logo"] /* --- Logo --- */ [component="brand/logo"] { max-height: 50px; width: auto; height: auto; max-width: 100%; display: block; object-fit: contain; object-position: left center; overflow: visible !important; } Better result !!