Ron (TeRON)
@teronintech.bsky.social
Full-Stack Software Engineer | Husband | Dad | Cyclist 🚴🏿 | HomeLab | #100Devs | Torc Community
https://teronbullock.com/links/
https://teronbullock.com/links/
End.
This refactor improves robustness & scalability by shifting trust away from client controlled data & enforcing authorization at the API layer.
This refactor improves robustness & scalability by shifting trust away from client controlled data & enforcing authorization at the API layer.
January 14, 2026 at 5:55 AM
End.
This refactor improves robustness & scalability by shifting trust away from client controlled data & enforcing authorization at the API layer.
This refactor improves robustness & scalability by shifting trust away from client controlled data & enforcing authorization at the API layer.
3. Bearer tokens can’t be easily manipulated or altered by code, making them far more secure and reliable for authenticating users.
On the backend, I changed all controller functions to verify auth via the token. Users can now only interact w/ their own data.
On the backend, I changed all controller functions to verify auth via the token. Users can now only interact w/ their own data.
January 14, 2026 at 5:54 AM
3. Bearer tokens can’t be easily manipulated or altered by code, making them far more secure and reliable for authenticating users.
On the backend, I changed all controller functions to verify auth via the token. Users can now only interact w/ their own data.
On the backend, I changed all controller functions to verify auth via the token. Users can now only interact w/ their own data.
2. The app was using user slugs along w/ tokens in the the fetch request. This created redundancy (since the token contained the user ID) & potential security risks (ie. unauthorized data access | user impersonation). By using header-based Bearer tokens, I eliminate these issues.
January 14, 2026 at 5:54 AM
2. The app was using user slugs along w/ tokens in the the fetch request. This created redundancy (since the token contained the user ID) & potential security risks (ie. unauthorized data access | user impersonation). By using header-based Bearer tokens, I eliminate these issues.
