1. Home
  2. Detail

@user15702152263631:

шоира
шоира
Open In TikTok:
Region: UZ
Sunday 25 June 2023 13:53:33 GMT
300
39
2
0

Music

Download

No Watermark .mp4 (2.98MB) No Watermark(HD) .mp4 (2.98MB) Watermark .mp4 (3.13MB) Music .mp3

Comments

user15702152263631
шоира :
мани кайнонажоним!
2023-06-28 05:50:19
1
user4392667704172
Хусен :
🥰🥰🥰
2023-06-25 13:57:15
0
To see more videos from user @user15702152263631, please go to the Tikwm homepage.

Other Videos

#mukenasilkmotif
#mukenasilkmotif
#bismillah #alhamdulillah #astaghfirullah #muslim #4u
#bismillah #alhamdulillah #astaghfirullah #muslim #4u




#MLBB10TH #ALLINMLBB
#MLBB10TH #ALLINMLBB
Ok so here’s what happened… I’m using Supabase as the backend and I have row-level security set up so that users can only access and update their own data (very standard, very secure) In addition to this because the AI is really expensive, I have rate limits and they are at a per-user level so I can raise them for an individual user The problem is I was storing the rate limits on the user table itself 🤦‍♂️ And because of the way my RLS was set up, users could in theory modify their own rate limits if they hit the backend endpoints directly The solution was to make these specific rate limit columns read-only or even better just store them on a completely different table This was a super rookie mistake and I’m really thankful that the person who reported it didn’t do anything bad 🙏 But wanted to share this because I think it’s a pretty common thing people are overlooking, especially if they're using Supabase #softwaredeveloper #coding #appdesign
Ok so here’s what happened… I’m using Supabase as the backend and I have row-level security set up so that users can only access and update their own data (very standard, very secure) In addition to this because the AI is really expensive, I have rate limits and they are at a per-user level so I can raise them for an individual user The problem is I was storing the rate limits on the user table itself 🤦‍♂️ And because of the way my RLS was set up, users could in theory modify their own rate limits if they hit the backend endpoints directly The solution was to make these specific rate limit columns read-only or even better just store them on a completely different table This was a super rookie mistake and I’m really thankful that the person who reported it didn’t do anything bad 🙏 But wanted to share this because I think it’s a pretty common thing people are overlooking, especially if they're using Supabase #softwaredeveloper #coding #appdesign

About

Legal