notification counter doesn't go away
-
I see the notification, close the browser, open it again, there that 1 is again. I look at the notifications and there is nothing.
-
@sockpuppet7 observed.
-
My websocket's ability to notify has been fucked since the last update, the only way I can get it to update is by changing topics.
-
@Tsaukpaetra I'm already convinced websocks are horrible tech that doesn't work. Discord on my phone is the same, sometimes it breaks and the only way to get it back working is to close it (as looking at the android tasks and swiping it to really kill it) and reopening.
-
@sockpuppet7 said in notification counter doesn't go away:
websocks
-
@sockpuppet7 said in notification counter doesn't go away:
@Tsaukpaetra I'm already convinced websocks are horrible tech that doesn't work. Discord on my phone is the same, sometimes it breaks and the only way to get it back working is to close it (as looking at the android tasks and swiping it to really kill it) and reopening.
I've never experienced anything like that.
-
@sockpuppet7 said in notification counter doesn't go away:
I see the notification, close the browser, open it again, there that 1 is again. I look at the notifications and there is nothing.
Yeah, I gave up on it a long time ago and just "Mark all notifications read" in each tab until it seems to stick.
-
@pie_flavor said in notification counter doesn't go away:
@sockpuppet7 said in notification counter doesn't go away:
@Tsaukpaetra I'm already convinced websocks are horrible tech that doesn't work. Discord on my phone is the same, sometimes it breaks and the only way to get it back working is to close it (as looking at the android tasks and swiping it to really kill it) and reopening.
I've never experienced anything like that.
You need to use a bad mobile connection to suffer the full extension of crappy tech. These badly coded websocket based applications die when the ISP/Phone close the connection. Not sure how gracefully this closing happens, but anyone with a clue about networking would manage that.
-
@sockpuppet7 This happens to me on a regular basis when I'm on TDWTF on mobile. Maybe it's because I'm on Project Fi (which is a VMNO that hybridizes a couple carriers)--if it's switching backbone carriers (which is transparent to the user) that might break the websocket and pop up that annoying "your connection was lost" toaster. As does putting the phone to sleep, changing from WiFi to LTE (or vice versa), changing access points, and about a dozen other random things.
-
@sockpuppet7 said in notification counter doesn't go away:
@pie_flavor said in notification counter doesn't go away:
@sockpuppet7 said in notification counter doesn't go away:
@Tsaukpaetra I'm already convinced websocks are horrible tech that doesn't work. Discord on my phone is the same, sometimes it breaks and the only way to get it back working is to close it (as looking at the android tasks and swiping it to really kill it) and reopening.
I've never experienced anything like that.
You need to use a bad mobile connection to suffer the full extension of crappy tech. These badly coded websocket based applications die when the ISP/Phone close the connection. Not sure how gracefully this closing happens, but anyone with a clue about networking would manage that.
The webchat stops working when you stop having an internet connection? Dang, I see what you mean - these apps really are shit.
Come on. Seriously?
-
@pie_flavor said in notification counter doesn't go away:
The webchat stops working when you stop having an internet connection? Dang, I see what you mean - these apps really are shit.
Come on. Seriously?No, just poorly coded websocket based chats stop working when the connection breaks. That doesn't mean I'm without an internet connection, any decent software just reconnect without it even being noticed by the user.
-
@sockpuppet7 Maybe don't constantly break the connection again. Also, Discord works just fine for me while walking across school campus, on wifi, where every ten feet the connection breaks.
-
@pie_flavor said in notification counter doesn't go away:
Maybe don't constantly break the connection again.
Great advice. Thanks for solving the problem. Dunno how it never crossed my mind.
-
@sockpuppet7 said in notification counter doesn't go away:
Dunno how it never crossed my mind.
Couldn't stay connected long enough for it to be transmitted. :P
-
@Tsaukpaetra said in notification counter doesn't go away:
My websocket's ability to notify has been fucked since the last update, the only way I can get it to update is by changing topics.
Thread drift finally has a purpose!
