1
π Feature: Block or make it harder to scrape data
Source: appwrite/appwrite#11522 · opened by @DankMemeGuy
π Feature description The issue when using AppWrite for the backend, with client-side rendering (CSR) is that when using Chrome's inspect tools and looking at the Network tab, you can view the API links, and view the JSON payloads. The issue for that is this can promote easy data scraping. I cannot find a way to prevent this right now other than to just use server-side rendering (SSR). Rate limiting is not sufficient as the user could use proxies, and possibly alter the API links itself to allow for more data per JSON payload then intended. However, on the AppWrite development side, there should be a feature that encrypts the JSON payload from the API links. The encryption key could be stored in a min.js JS file on the client side that does the decryption, and sure this isn't bullet proof, but at least this would disincentivize rookie scrapers from pillaging the website. Another solution could just be to obfuscate the JSON payloads as they are sent from the serveβ¦
No pledges yet. Be the first to back this.
Comments
Similar requests
Disable ClamAV by default
1 vote · 0 comments
π Enhancement: Make migrations not block everything during the process
3 votes · 0 comments
Custom rate limit for database collection access per user
5 votes · 0 comments
Serverless / Decentralized Appwrite; Specifically, a low-latency Primary Database Cluster or Blockchain serving distinct Appwrite installations and Frontends
1 vote · 0 comments
Use email OTP for password reset and email verification.
2 votes · 0 comments
No comments yet.