cookies vs back-end settings

[kent_dorfman766]

So this is gonna come off as nitpicking, but it's not just yinz that do this so think of my issue as a chance to blaze the way in doing things the right way. Way too many sites store user client preferences as client browser cookies, instead of on the backend under a user database. The savvy web browser usually has cookies very much restricted and deletes them between sessions so website preferences stored as cookies are reset every session. I'd strongly argue that while EASIER to implement, cookie based user preferences are not the proper way to store client preferences. This comes up on here because of the "we want to do push notifications to your browser" notice that I've disabled more than once but always comes back.

 

[Phishfry]

"we want to do push notifications to your browser"

That is an annoying bit isn't it. The settings don't seem to stick. I only see it when logged in. Why the setting cannot be disabled I dunno.

 

[cracauer@]

Theme selection is deliberately kept client side in many forum packages so that the same user can have different themes on different computers.

 

[Espionage724]

I'd rather store less stuff about users and leave settings cookie-side

This comes up on here because of the "we want to do push notifications to your browser" notice that I've disabled more than once but always comes back.

That serves as a reminder for me to disable browser-side notifications (the bottom bar is annoying on various websites on fresh Firefox installs)

 

[SirDice]

Push notifications can be blocked in your browser. That's stored in the browser settings, not in a cookie. On Firefox that's under "Settings" -> "Privacy & Security" -> "Permissions" -> "Notifications"