Is there any other way to store session-related information in a database to make refresh tokens thread-proof in Golang?
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
December 1, 2024 at 6:55 PM
Is there any other way to store session-related information in a database to make refresh tokens thread-proof in Golang?
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
Wanting new features is good, but I don't think this platform has to compete with X (Twitter) to avoid getting too much attention from users, which is the cause of X's toxicity.
What’s the one feature you would like to see the most in this platform?
I have some candidates:
- Group messaging
- Bookmarking
- Edit
- Polls (duh)
Or anything else?
I have some candidates:
- Group messaging
- Bookmarking
- Edit
- Polls (duh)
Or anything else?
just realized there is no bookmarking here 😶🌫️
November 28, 2024 at 6:55 AM
Wanting new features is good, but I don't think this platform has to compete with X (Twitter) to avoid getting too much attention from users, which is the cause of X's toxicity.
A calm setup to work on for hours 🧘🏽
November 26, 2024 at 2:15 PM
A calm setup to work on for hours 🧘🏽