Instagram for AI Mobile Apps

or

Social

athreat@athreat
### Task 1: Set Up Project Structure
- **Objective**: Initialize the "Thunder Snooper" app/sim project.
- **Actions**: 
  - Create a new project using **React** for the frontend and **Node.js** with **Express.js** for the backend.
  - Set up **MongoDB** for data storage and **Redis** for caching API responses.
  - Install dependencies: **npm install react react-dom express mongoose redis axios**.
  - Configure a basic folder structure: /client (React), /server (Node.js), /config (database settings).
- **Deliverable**: A working project skeleton with a "Hello World" page on localhost:3000.

### Task 2: Implement Phone Number Search Module
- **Objective**: Build a module to retrieve geolocation, carrier, and owner’s name from a phone number.
- **Actions**: 
  - Create a React component (e.g., PhoneSearch.js) with an input field for phone numbers.
  - Integrate APIs from Truecaller, Advanced Background Checks, Best Phone Lookup, CarrierLookup, CNAM, Data24-7, Infobel, NANPA, Numberway, Pipl, Reverse Phone Lookup, Slydial, SpyDialer, SpyTox, Superpages, Sync.ME, That’s Them, True People Search, US Phonebook, White Pages, and WhoCalled using **Axios**.
  - Handle API rate limits with a queue system and store results in MongoDB.
  - Display results in a table format on the frontend.
- **Deliverable**: A functional phone number search tool returning sample data (e.g., geolocation: "123 Main St", carrier: "AT&T", name: "John Doe") on localhost:3000/search.

### Task 3: Develop Anonymous Messaging System
- **Objective**: Enable real-time anonymous messaging to the target phone number.
- **Actions**: 
  - Set up **Socket.IO** on the backend to handle real-time communication.
  - Create a messaging interface in React (e.g., MessagePanel.js) with send/receive functionality.
  - Encrypt messages using **CryptoJS** with AES-256 and mask user identity.
  - Integrate Truecaller.com and Getcontact for contact validation via API calls.
  - Store message logs in MongoDB with encrypted fields.
- **Deliverable**: A working chat interface on localhost:3000/message that sends/receives encrypted messages anonymously.

### Task 4: Build Deep Dive Investigation Engine
- **Objective**: Create a comprehensive search engine for detailed owner information.
- **Actions**: 
  - Develop a DeepDive.js component to aggregate data from:
    - **People Search**: Pipl, Spokeo, PeekYou, Find People for Free, Qwant, FastPeopleSearch, Canada Phone Directory, 411 US Phone Directory, 192.com, Fold3, FamilyTreeNow, Cluster Maps.
    - **Username Search**: Know’em?, NameCheckup, Lullar Com, Namevine, Username Search, Free Username Search, Usersherlock, WhatsMyName Web.
    - **Company Data**: SEC.gov EDGAR, us-info.com, California Secretary of State, OpenCorporates, Corporation Wiki, Companies House, littleSis, Track Hedge Funds, Crosslinked, Inspy, SocialPwned, HM Revenue & Customs, Partnerpoint.
    - **Web Scraping**: ParseHub, opsdisk/metagoofil (use **Puppeteer** for scraping).
    - **Email Tools**: theHarvester, Hunter, Email Permutator, IP2Location, ProoFy, khast3x/h8mail, m4110k/Infoga, Hashcast.axur.com, Spybot Identity Monitor, GHunt, Epieos (use **Nodemailer** for validation).
    - **Location Services**: ipapi (use **Geolocation API**).
  - Implement a confirmation modal using **React-Bootstrap** if multiple owners are detected.
  - Store findings in MongoDB and fetch results dynamically.
- **Deliverable**: A Deep Dive interface on localhost:3000/deepdive returning sample data (e.g., friends: "Jane Doe", workplace: "Tech Corp") with owner confirmation if needed.

### Task 5: Implement Data Export Feature
- **Objective**: Enable saving investigation data as images or PDFs.
- **Actions**: 
  - Integrate **html2canvas** to capture the results table as an image.
  - Use **jsPDF** to generate PDFs from the captured data.
  - Create a download button in React (e.g., ExportButton.js) that opens results in a browser tab for saving.
  - Ensure exported files include timestamps and case IDs.
- **Deliverable**: A functional export button on localhost:3000/export generating a sample image/PDF with data.

### Task 6: Ensure Security and Authentication
- **Objective**: Secure the app with encryption and authentication.
- **Actions**: 
  - Implement **bcrypt** for password hashing and **JWT** for user authentication on the backend.
  - Add **express-rate-limit** to prevent API abuse (e.g., 100 requests/hour).
  - Encrypt sensitive data (e.g., phone numbers, messages) in MongoDB.
- **Deliverable**: A secure login page on localhost:3000/login with rate-limited API access.

### Task 7: Set Up Iterative Link Integration
- **Objective**: Prepare the search function for future link additions.
- **Actions**: 
  - Create a dynamic API endpoint (e.g., /add-link) to accept new links from prompts.
  - Update the Deep Dive engine to parse and integrate new links using **Puppeteer**.
  - Test with a dummy link (e.g., "https://example.com").
- **Deliverable**: A working endpoint on localhost:5000/add-link that logs and processes a sample link.

### Next Phases (Post-Functionality):
- **Graphics**: Implement HD lightning effects with **Three.js** and **PixiJS**, using GSAP for transitions.
- **Additional Features**: Add Reverse Image Search, Blur Processing, and Data Analytics.

**General Instructions:**
- Test each module with a 5MB
60
0
0

### Task 1: Set Up Project Structure - **Objective**: Initialize the "Thunder Snooper" app/sim project. - **Actions**: - Create a new project using **React** for the frontend and **Node.js** with **Express.js** for the backend. - Set up **MongoDB** for data storage and **Redis** for caching API responses. - Install dependencies: **npm install react react-dom express mongoose redis axios**. - Configure a basic folder structure: /client (React), /server (Node.js), /config (database settings). - **Deliverable**: A working project skeleton with a "Hello World" page on localhost:3000. ### Task 2: Implement Phone Number Search Module - **Objective**: Build a module to retrieve geolocation, carrier, and owner’s name from a phone number. - **Actions**: - Create a React component (e.g., PhoneSearch.js) with an input field for phone numbers. - Integrate APIs from Truecaller, Advanced Background Checks, Best Phone Lookup, CarrierLookup, CNAM, Data24-7, Infobel, NANPA, Numberway, Pipl, Reverse Phone Lookup, Slydial, SpyDialer, SpyTox, Superpages, Sync.ME, That’s Them, True People Search, US Phonebook, White Pages, and WhoCalled using **Axios**. - Handle API rate limits with a queue system and store results in MongoDB. - Display results in a table format on the frontend. - **Deliverable**: A functional phone number search tool returning sample data (e.g., geolocation: "123 Main St", carrier: "AT&T", name: "John Doe") on localhost:3000/search. ### Task 3: Develop Anonymous Messaging System - **Objective**: Enable real-time anonymous messaging to the target phone number. - **Actions**: - Set up **Socket.IO** on the backend to handle real-time communication. - Create a messaging interface in React (e.g., MessagePanel.js) with send/receive functionality. - Encrypt messages using **CryptoJS** with AES-256 and mask user identity. - Integrate Truecaller.com and Getcontact for contact validation via API calls. - Store message logs in MongoDB with encrypted fields. - **Deliverable**: A working chat interface on localhost:3000/message that sends/receives encrypted messages anonymously. ### Task 4: Build Deep Dive Investigation Engine - **Objective**: Create a comprehensive search engine for detailed owner information. - **Actions**: - Develop a DeepDive.js component to aggregate data from: - **People Search**: Pipl, Spokeo, PeekYou, Find People for Free, Qwant, FastPeopleSearch, Canada Phone Directory, 411 US Phone Directory, 192.com, Fold3, FamilyTreeNow, Cluster Maps. - **Username Search**: Know’em?, NameCheckup, Lullar Com, Namevine, Username Search, Free Username Search, Usersherlock, WhatsMyName Web. - **Company Data**: SEC.gov EDGAR, us-info.com, California Secretary of State, OpenCorporates, Corporation Wiki, Companies House, littleSis, Track Hedge Funds, Crosslinked, Inspy, SocialPwned, HM Revenue & Customs, Partnerpoint. - **Web Scraping**: ParseHub, opsdisk/metagoofil (use **Puppeteer** for scraping). - **Email Tools**: theHarvester, Hunter, Email Permutator, IP2Location, ProoFy, khast3x/h8mail, m4110k/Infoga, Hashcast.axur.com, Spybot Identity Monitor, GHunt, Epieos (use **Nodemailer** for validation). - **Location Services**: ipapi (use **Geolocation API**). - Implement a confirmation modal using **React-Bootstrap** if multiple owners are detected. - Store findings in MongoDB and fetch results dynamically. - **Deliverable**: A Deep Dive interface on localhost:3000/deepdive returning sample data (e.g., friends: "Jane Doe", workplace: "Tech Corp") with owner confirmation if needed. ### Task 5: Implement Data Export Feature - **Objective**: Enable saving investigation data as images or PDFs. - **Actions**: - Integrate **html2canvas** to capture the results table as an image. - Use **jsPDF** to generate PDFs from the captured data. - Create a download button in React (e.g., ExportButton.js) that opens results in a browser tab for saving. - Ensure exported files include timestamps and case IDs. - **Deliverable**: A functional export button on localhost:3000/export generating a sample image/PDF with data. ### Task 6: Ensure Security and Authentication - **Objective**: Secure the app with encryption and authentication. - **Actions**: - Implement **bcrypt** for password hashing and **JWT** for user authentication on the backend. - Add **express-rate-limit** to prevent API abuse (e.g., 100 requests/hour). - Encrypt sensitive data (e.g., phone numbers, messages) in MongoDB. - **Deliverable**: A secure login page on localhost:3000/login with rate-limited API access. ### Task 7: Set Up Iterative Link Integration - **Objective**: Prepare the search function for future link additions. - **Actions**: - Create a dynamic API endpoint (e.g., /add-link) to accept new links from prompts. - Update the Deep Dive engine to parse and integrate new links using **Puppeteer**. - Test with a dummy link (e.g., "https://example.com"). - **Deliverable**: A working endpoint on localhost:5000/add-link that logs and processes a sample link. ### Next Phases (Post-Functionality): - **Graphics**: Implement HD lightning effects with **Three.js** and **PixiJS**, using GSAP for transitions. - **Additional Features**: Add Reverse Image Search, Blur Processing, and Data Analytics. **General Instructions:** - Test each module with a 5MB

kamtothebambam@kamtothebambam
Create a video-sharing app that supports both short-form and long-form video content. The app should have the following features:

1.  **Dual Home Feeds:**
    *   The app should open to a tabbed interface.
    *   **"Shorts" Tab:** A full-screen, vertical, auto-playing feed for discovering short videos. Users can swipe up and down to navigate between videos.
    *   **"Videos" Tab:** A browsable feed for long-form content, displaying videos as a list or grid with a thumbnail, title, creator name, and view count.

2.  **Video Player Experience:**
    *   **Shorts Player:** The UI for liking, commenting, and sharing should be overlaid on the video.
    *   **Long-Form Player:** Tapping a long-form video opens a dedicated player screen with standard video controls (play/pause, timeline scrubber), video title, description, and a comments section below.

3.  **Video Creation and Upload:**
    *   A prominent button for users to create content.
    *   When uploading, the user must specify if the video is "Short" or "Long-Form."
    *   Users can upload from their device library or record directly in the app. The video in the attachment `https://user-images.githubusercontent.com/12345/67890.mov` is a good example of the type of video content to expect.
    *   Users must add a title to their video. A description is optional.

4.  **User Interaction:**
    *   Users can like and comment on all videos.
    *   Users can follow creators.
    *   The "Shorts" feed should prioritize content from followed creators and recommend new content.

5.  **Creator Profile Page:**
    *   Accessible by tapping a creator's username.
    *   The profile should have separate, tabbed sections displaying grids of the user's "Shorts" and "Long-Form" videos.

All videos, comments, likes, and follower relationships should be stored persistently in a database and linked to the correct users.
37
0
0

Create a video-sharing app that supports both short-form and long-form video content. The app should have the following features: 1. **Dual Home Feeds:** * The app should open to a tabbed interface. * **"Shorts" Tab:** A full-screen, vertical, auto-playing feed for discovering short videos. Users can swipe up and down to navigate between videos. * **"Videos" Tab:** A browsable feed for long-form content, displaying videos as a list or grid with a thumbnail, title, creator name, and view count. 2. **Video Player Experience:** * **Shorts Player:** The UI for liking, commenting, and sharing should be overlaid on the video. * **Long-Form Player:** Tapping a long-form video opens a dedicated player screen with standard video controls (play/pause, timeline scrubber), video title, description, and a comments section below. 3. **Video Creation and Upload:** * A prominent button for users to create content. * When uploading, the user must specify if the video is "Short" or "Long-Form." * Users can upload from their device library or record directly in the app. The video in the attachment `https://user-images.githubusercontent.com/12345/67890.mov` is a good example of the type of video content to expect. * Users must add a title to their video. A description is optional. 4. **User Interaction:** * Users can like and comment on all videos. * Users can follow creators. * The "Shorts" feed should prioritize content from followed creators and recommend new content. 5. **Creator Profile Page:** * Accessible by tapping a creator's username. * The profile should have separate, tabbed sections displaying grids of the user's "Shorts" and "Long-Form" videos. All videos, comments, likes, and follower relationships should be stored persistently in a database and linked to the correct users.

Β© 2025 aSim. All rights reserved.