PieFed 2025 Roadmap prioritisation

169 readers

1 users here now

A temporary community to vote on priorities for 2025

founded 4 months ago

Real-time notification bell (piefed.social)

submitted 3 months ago by rimu@piefed.social to c/piefed_2025@piefed.social

7 comments fedilink hide all child comments

The notification icon (the bell) isn’t showing notifications are waiting unless the screen is refreshed. It would be nice if it were more actively checking notification status.

you are viewing a single comment's thread
view the rest of the comments

[–] rimu@piefed.social 0 points 3 months ago (6 children)

Might need websockets for this?

[–] wjs018@piefed.social 1 points 3 months ago (1 children)

Could it be done with htmx? hx-trigger can be set to fire at fixed intervals (docs, see Polling).

[–] rimu@piefed.social 1 points 3 months ago (1 children)

That would be simple to code but very bad for scalability. Each user would constantly be keeping a connection open, tying up a thread on the server. Just a few dozen concurrent users would bring a server to it's knees.

WSGI (flask) isn't great at coping with lots of simultaneous open connections so we might need to make a separate mini-project using a different framework/stack/language. This would involve a significant increase in dependencies and more complexity for deployment so we'd have to really really want to do it.

Personally it seems like this feature was added to mainstream social media purely to increase addiction and farm engagement so I'm pretty lukewarm about that and don't feel the lack of it in PieFed. Getting away from that crap is kinda the whole point of the fediverse, to me.

[–] rimu@piefed.social 1 points 3 months ago

I guess it's the content of the notifications rather than the timing of their delivery is what makes them a dark pattern so perhaps I need to chill out about that.

load more comments (4 replies)