Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Searching a 40,000-Follower List Without Scrolling: Design Notes From Building It

Disclosure: I'm one of the people who built the tool linked in this post. I'm sharing the design thinking, not selling anything. Some AI assistance was used to draft this and I edited it. A friend asked me a simple question last month: "Does this brand actually follow the creators it says it works with?" The brand had around 40,000 followers. Checking by hand meant scrolling for ages. That tiny…

A friend asked a simple question about a brand's social media following, prompting the creation of a tool to search Instagram followers without scrolling through long lists. The tool was built to address the limitations of manually scrolling through follower lists, which can be time-consuming and expensive. The founder of the tool learned several key lessons while building it, which could be helpful for others looking to create similar tools.

The first lesson is to search at the source when possible. Instead of downloading the entire follower list, use the provider's search endpoint if it's available. This approach reduces the number of requests and can speed up the search process. The second lesson is to cache by the question, not the user. Frequently asked questions should be cached based on the account, search direction (followers or following), and the search term. This approach optimizes cache usage and improves performance.

The third lesson is to make the free allowance something that's affordable and tied to something enforceable. Offer a daily free search limit, but tie it to an expiration time or a per-day limit to prevent abuse. The fourth lesson is to protect the endpoint from bots using cheap methods such as hidden honeypot fields, Cloudflare Turnstile, and per-IP rate limits. These measures help prevent automated abuse and keep the tool running smoothly.

The fifth lesson is to be transparent about the tool's limitations. Clearly state that the tool only works for public accounts, and private accounts may not return all entries. This honesty helps manage user expectations and builds trust. The sixth and final lesson is to prioritize privacy and ethics. Only read public data, avoid building lists for resale or harassment, and never ask for users' platform passwords. Treat results as personal data and follow GDPR guidelines if necessary.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Hafif IDE'lere Dönüş / Back to Lightweight IDEs

Sparky-Family'den yeni bir bakış açısı. A new perspective from Sparky-Family. Splash Code Studio [TR] Hafif IDE'lere Dönüş Yazılım geliştirme araçları her geçen gün ağırlaşıyor.

  • Sparky-Family releases Splash Code Studio as lightweight IDE alternative.
  • Splash Code Studio offers 2GB RAM startup and 30-second startup time.
  • IDE focuses on speed, customization, and offline functionality.

Solana Transaction Fees Explained: Base Fee, Priority Fees and Landing Cheaply

Short version: a transaction on Solana pays a tiny fixed base fee and an optional priority fee. Base fee is a fixed amount of lamports per signature and it goes to the network.

  • Solana transaction fees comprise a base fee and a priority fee
  • Base fee is charged per signature and goes to the network
  • Priority fee compensates block leader and varies by transaction urgency

S3 vs REST Storage: Choose by per-User Generated Image Controls in Node Express

Short answer: store every AI-generated image under a server-built users/{userId}/generations/ prefix, keep objects private, return expiring signed download links, delete known keys during user…

  • Use users/{userId}/generations/ prefix for tenant isolation
  • Implement application-level ownership checks for reads, deletes, and signed links
  • Choose between Infrai library or Amazon S3 based on team's preference

More from Saturday 21 November →