v1.1

[snoopythe3-from-scratch]

Fixed CVE-2025-55301

Full Changelog:
v1...v1.1

---

This discussion was created from the release v1.1.

[kRxZykRxZy]

The id is what is used for username, the id is used to get the username, the id is in local_storage, username is stored as well but when edited won't affect anything, stored for just informatory purpose

[localpigeons]

Might wanna move to HttpOnly cookies, since localStorage can be vulnerable to XSS.

[kRxZykRxZy]

Might wanna move to HttpOnly cookies, since localStorage can be vulnerable to XSS.

XSS,....... raging I just hate security.... crying

OK, but I'm thinking of creating a new branch and just adding a local backend in it for lots more stuff allowing flask sessions or express sessions which can't be edited

[nouxinf]

Firebase solves literally all of this by handling it by itself

[kRxZykRxZy]

I haven't read into firebase but does it have sessions to store username until needed, e.g when posting, like some browser storage that can't be edited.

[nouxinf]

Yes, the stuff it provides automatically is stuff that is ready and used in production code

[nouxinf]

1.2 can be when firebase is added.

[kRxZykRxZy]

Done!

[kRxZykRxZy]

@snoopythe3-from-scratch can you release v 1.2

[snoopythe3-from-scratch]

Ok