Notification System

[Guest deleted34304850]

Since the new notification system went live, I have received a couple of notifications related to new games, but nothing else.

Tonight, I have two notifications for a mod I am tracking, called CVC Dead Wasteland for Fallout 4.

The first notification says a new article has been added. If I click the notification I get a message suggesting the article isn't found. This may be true - it could be the article was taken down. I have no way of knowing.

The second notification tells me files have been added. If I click this notification, I get a very brief error message that tells me "Connection Error - try reloading the notifications". This message only appears very briefly before I am sent to the mod's files page.

Aside from these two notifications, I have received nothing else.

I can see this on Firefox.

When I use the site under Chrome I do not see the error message at all, and I am passed to the mod page without issue. What I also see on Chrome is the number of unread notifications goes down by one. This doesn't happen on Firefox, due, probably, to the error message that appears.

I hope this helps you guys trying to figure this puzzle out.

If I can provide more information, let me know what you need.

[Guest deleted34304850]

no feedback, or anything? thought you wanted feedback ony your newly delivered feature-free, bug-rich "mvp" offering?

well wasn't this a waste of time.

my mistake.

[Pickysaurus]

Sorry you didn't get a reply sooner. Yes, we know about the error you mentioned. It's a bug in Firefox that it doesn't look like Mozilla is planning to fix any time soon (it's been open on their bug tracker for a long time now). All other browsers handle the links/network requests properly.

[Guest deleted34304850]

Then make your code work with all browsers. And test it.

 

Not the first time this has happened, (see the issues where download buttons wouldn't work on some browsers) and it probably won't be the last because your devs are continually guilty of very bad practice.

 

the browser choice should not be a deciding factor in how your site works, and the code should adapt to the browser being used. Claiming bugs in browsers are the root cause is disengenuous. Of course browsers have bugs in them, that's why they are continually updated. Your devs need to be able to anticipate and work seamlessly across all the market share browsers, and saying "oh it works in Chrome" isn't a good answer.

 

look at other websites out there - does amazon suffer this? how about ebay? how about news sites? how about any other massive websites? no site i use away from this one breaks like this.

 

what happens in your next "upgrade" when it won't work in Chrome? Do you just down tools and wait for it to be fixed?

 

One other thing to note here, this bug in the Mozilla code base you're assigning the latest root cause to (after cookies and users not enabling notifications) is five years old. Five YEARS! Not five minutes, not five days, not five months, five YEARS old.

 

This entire farce is 100% on the back of your devs and what they delivered.

Edited March 27, 2021 by 1ae0bfb8

[Pickysaurus]

Then make your code work with all browsers. And test it.

 

Not the first time this has happened, (see the issues where download buttons wouldn't work on some browsers) and it probably won't be the last because your devs are continually guilty of very bad practice.

 

the browser choice should not be a deciding factor in how your site works, and the code should adapt to the browser being used. Claiming bugs in browsers are the root cause is disengenuous. Of course browsers have bugs in them, that's why they are continually updated. Your devs need to be able to anticipate and work seamlessly across all the market share browsers, and saying "oh it works in Chrome" isn't a good answer.

 

look at other websites out there - does amazon suffer this? how about ebay? how about news sites? how about any other massive websites? no site i use away from this one breaks like this.

 

what happens in your next "upgrade" when it won't work in Chrome? Do you just down tools and wait for it to be fixed?

 

One other thing to note here, this bug in the Mozilla code base you're assigning the latest root cause to (after cookies and users not enabling notifications) is five years old. Five YEARS! Not five minutes, not five days, not five months, five YEARS old.

 

This entire farce is 100% on the back of your devs and what they delivered.

 

You do make some valid points. I'm not saying the blame lies with Mozilla, that is simply the cause of the bug you are seeing.

 

I agree we could've done more testing, but your comparison to Amazon/eBay/other big sites might not really be all that fair. I'm flattered you consider us to be on that level, but remember that Nexus Mods is still a relatively small fish. We're not a huge billion-dollar enterprise with hundreds of developers and a fully staffed QA team. We have a pretty small team and we do rely a lot of on the community to help us track down bugs. We're reviewing our process from design to release to make sure we are more thorough in manual testing for future releases.

[Guest deleted34304850]

it's not about the number of people though. that isn't the point. its about following best practice. which, it seems, based on evidence of a few site-related issues, including the notification system, isn't done.

 

 

if you write code that ignores certain industry wide standards and go for a browser-specific fix - you end up like microsoft when they were so far ingrained into their drive to use their own standards and try to influence the rest of the world, that they caused people to retain and continue to use internet explorer to access their content, including downloading patches.

 

basically - if you want to use our content (and you need to) then internet explorer is the one for you.

 

if you develop knowingly ignoring certain browser limitations, including five year old bugs in the code, that render your code broken once its deployed, then that is not the fault of the end user, or the team behind the browser. they've done their bit in publishing the bug, and its on developers to know and work around such limitations.

 

there has been a lot of mis-information bandied about through this update, where people were cited for cleaning cookies, were turning off notifications and now, browser bugs all conspiring to break your system.

 

the truth is that this system has been poorly developed, has missed the mark on end user requirements, has been implemented with no recourse as to backing it out and returning to the previous system that worked until this one is fixed, and has obviously not been tested sufficiently.

 

it's way too late to do anything about it now, except to fix forward and hope that one day in the future you give the users what they already had, rather than a lot of things they never asked for but are forced to endure because the implementation has been so poor.

 

in another post, since deleted, i opined that this change could have the unintended consequence of mod authors and users who want to help support their work simply using this platform as a hosting site and moving all support/social aspects off to discord or similar. it already happens with several well known mods and mod authors, this may simply open the door to everyone else, because right now, what you have delivered doesn't in any way, shape or form, match the description of the update you put up.

 

i hope i'm wrong on that as i don't use any social media at all, but that is a genuine concern to me, and should be to nexusmods as well.

[XanderVirtus]

Just found this topic. This is still not working, yet many people using firefox I think?

[Guest deleted34304850]

it won't get fixed. the reasons for why are in my posts above.

[XanderVirtus]

it won't get fixed. the reasons for why are in my posts above.

I just read it, thanks for posting!