[Omniscient]

problem is , notif doesn't go away even if it's already viewed.

🔐 loading encrypted image…

Oh wait, I think what you're saying is that the notifications still show. Yes, always been that way. I thought you were talking about the bell count.

Let me understand what you're saying. Even if the bell count is zero, if you open the notification box you'll see the previous notifications. I think I have it showing 20-25 notices.

If you're saying the count is wrong that's potentially because of a js glitch while I was working. Can you try and click the MARK READ button?

[Scrub]

You're a tool

Scrub

You stink Omniscient

The tag worked but when I clicked reply it still shows the notification is new

[Omniscient]

You stink Omniscient

The tag worked but when I clicked reply it still shows the notification is new

I must be getting tired, but I don't feel tired.

What do you mean?

[Wake]

So glad the bell is back, what a beautiful little bell.

[Scrub]

Oh wait, I think what you're saying is that the notifications still show.  Yes, always been that way.  I thought you were talking about the bell count.

Let me understand what you're saying. Even if the bell count is zero, if you open the notification box you'll see the previous notifications.  I think I have it showing 20-25 notices.

If you're saying the count is wrong that's potentially because of a js glitch while I was working. Can you try and click the MARK READ button?

I see you said it’s always been this way, but before I’d be able to click the notification it bring me to the post or whatever and then it would mark itself as read because I clicked it. Currently if I click it, it still shows as new

[Omniscient]

I see you said it’s always been this way, but before I’d be able to click the notification it bring me to the post or whatever and then it would mark itself as read because I clicked it. Currently if I click it, it still shows as new

I'll have to review behavior. It's likely not exact to previous. This is almost entirely coded from scratch.

And I now understand what you mean.

[Scrub]

I'll have to review behavior. It's likely not exact to previous. This is almost entirely coded from scratch.

And I now understand what you mean.

Not to add to the confusion, but now 1 of my notifications marked itself as read but 2 have not lmao.


I can always take a screen record if you need me to.

[Omniscient]

I'll resume fixes in the morning.

[Motusora]

Oh wait, I think what you're saying is that the notifications still show. Yes, always been that way. I thought you were talking about the bell count.

Let me understand what you're saying. Even if the bell count is zero, if you open the notification box you'll see the previous notifications. I think I have it showing 20-25 notices.

If you're saying the count is wrong that's potentially because of a js glitch while I was working. Can you try and click the MARK READ button?

even if the bell count is 0 , i still can't click it .
that's what i mean.

when i click ctrl+f5 , bell count re-appears but wont disappear even if i viewed them already.


Scrub mention test

[Scrub]

even if the bell count is 0 , i still can't click it .
that's what i mean.

when i click ctrl+f5 , bell count re-appears but wont disappear even if i viewed them already.


Scrub  mention test

The mention works fine and I can click the notifications on mobile no issue, it just doesn’t auto read them when I click on them, (well 1 did randomly but now I have a total of 3 new notifications)


I’m just happy these are back.

[Omniscient]

even if the bell count is 0 , i still can't click it .
that's what i mean.

when i click ctrl+f5 , bell count re-appears but wont disappear even if i viewed them already.


Scrub mention test

any scripts on your browser?

anyone else experiencing this?

[Motusora]

any scripts on your browser?

anyone else experiencing this?

i dont have any scripts in my browser.
same issue either i use pc or mac


same chrome browser tho

[CL1B]

If from scratch; Keys -> Browser Subscription -> Service worker -> Push API

No caching, no socket, no nothing.

This is the standard because you don't deal with the UX hassle you see mentioned earlier, assuming the way these sit in the DB in the db is efficient. I don't see older notifications in mine so if you still have room I'd make sure it's as simple as possible and is the single source of truth

AI is known to overcomplicate this especially if prompted wrong, time cutting is having it make one in typescript -> ux and edge case audit -> port to whatever syntax you want afterwards. Why? TS in agentic webdev yields better overall code for a bunch of reasons, it forces bugs to prevail earlier due to the syntax and how those compile (similar to rust)

[Scrub]

any scripts on your browser? 

anyone else experiencing this?

No scripts running bro.

[Omniscient]

Made some adjustments. Hoping that it fixes the issues with clicked notifications being marked read. I have to test but I have to get some new notices.