Skip to content

Instantly share code, notes, and snippets.

@luckysitara

luckysitara/erwr

Last active November 1, 2025 07:30
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save luckysitara/90b3c5587a6137831658a92ad9826166 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save luckysitara/90b3c5587a6137831658a92ad9826166 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
erwr
location wasn't included in the ip analysis output( and also if the analysis return the latitude and longitude of the location is there a way we can add a map feature using google map to view the location? ) and the result instead of being displayed in the same page can have a different page for it just like pii intelligence result page
https://v0.app/chat/sentinel-6pqhUTAgEUc
AIzaSyCoNJkO0GhoeY2uy6NPzxeVF0GxZvy33qI
@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

INFO: 127.0.0.1:60036 - "POST /api/auth/login HTTP/1.1" 200 OK
INFO: 127.0.0.1:60036 - "OPTIONS /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:60036 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:60036 - "OPTIONS /api/dashboard/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:60044 - "OPTIONS /api/cases/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60050 - "OPTIONS /api/users/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60044 - "GET /api/dashboard/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:60044 - "GET /api/dashboard/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:60036 - "GET /api/users/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60050 - "GET /api/cases/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60044 - "GET /api/users/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60050 - "GET /api/cases/ HTTP/1.1" 200 OK
INFO: 127.0.0.1:60058 - "GET /api/social-intel/analytics HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60052 - "GET /api/social-intel/analytics HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60058 - "GET /api/social-intel/twitter/threats HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60052 - "GET /api/social-intel/twitter/threats HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60058 - "GET /api/social-intel/news/articles HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60052 - "GET /api/social-intel/news/articles HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60058 - "GET /api/social-intel/alerts HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:60052 - "GET /api/social-intel/alerts HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:57382 - "GET /api/social-intel/analytics HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:57382 - "GET /api/social-intel/twitter/threats HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:57382 - "GET /api/social-intel/news/articles HTTP/1.1" 403 Forbidden
INFO: 127.0.0.1:57382 - "GET /api/social-intel/alerts HTTP/1.1" 403 Forbidden

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

✓ Starting...
✓ Ready in 1988ms
○ Compiling /dark-web ...
✓ Compiled /dark-web in 1770ms (723 modules)
✓ Compiled /social-intelligence in 297ms (734 modules)
✓ Compiled /api/social-intel/analytics in 54ms (409 modules)
GET /api/social-intel/analytics 401 in 101ms
GET /api/social-intel/analytics 401 in 101ms
✓ Compiled /api/social-intel/twitter/threats in 83ms (409 modules)
✓ Compiled (411 modules)
GET /api/social-intel/twitter/threats 401 in 112ms
GET /api/social-intel/twitter/threats 401 in 112ms
✓ Compiled /api/social-intel/news/articles in 67ms (411 modules)
✓ Compiled (413 modules)
GET /api/social-intel/news/articles 401 in 99ms
GET /api/social-intel/news/articles 401 in 99ms
✓ Compiled /api/social-intel/alerts in 62ms (413 modules)
✓ Compiled (415 modules)
GET /api/social-intel/alerts 401 in 100ms
GET /api/social-intel/alerts 401 in 100ms
✓ Compiled in 58ms (415 modules)
GET /api/social-intel/analytics 401 in 35ms
GET /api/social-intel/twitter/threats 401 in 8ms
GET /api/social-intel/news/articles 401 in 7ms
GET /api/social-intel/alerts 401 in 10ms
✓ Compiled /api/social-intel/search in 74ms (417 modules)
GET /api/social-intel/search?q=wetywre 401 in 104ms
✓ Compiled in 86ms (417 modules)
GET /api/social-intel/search?q=wetywre 401 in 31ms
GET /api/social-intel/search?q=wetywre 401 in 4ms
GET /api/social-intel/analytics 401 in 5ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 4ms
GET /api/social-intel/alerts 401 in 3ms
GET /api/social-intel/analytics 401 in 4ms
GET /api/social-intel/twitter/threats 401 in 5ms
GET /api/social-intel/news/articles 401 in 4ms
GET /api/social-intel/alerts 401 in 2ms

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

(nip) ┌─[venom@parrot]─[~/nip/backend]
└──╼ $uvicorn app.main:app --host 0.0.0.0 --port 8080 --reload
INFO: Will watch for changes in these directories: ['/home/venom/nip/backend']
INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
INFO: Started reloader process [40315] using WatchFiles
INFO: Started server process [40317]
INFO: Waiting for application startup.
INFO: Application startup complete.

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

✓ Starting...
✓ Ready in 1838ms
✓ Compiled /api/social-intel/analytics in 234ms (56 modules)
GET /api/social-intel/analytics 401 in 280ms
✓ Compiled /api/social-intel/twitter/threats in 66ms (56 modules)
✓ Compiled (58 modules)
GET /api/social-intel/twitter/threats 401 in 73ms
✓ Compiled /api/social-intel/news/articles in 43ms (58 modules)
✓ Compiled (60 modules)
GET /api/social-intel/news/articles 401 in 59ms
✓ Compiled /api/social-intel/alerts in 39ms (60 modules)
✓ Compiled (62 modules)
GET /api/social-intel/alerts 401 in 58ms
✓ Compiled in 38ms (62 modules)
GET /api/social-intel/analytics 401 in 28ms
GET /api/social-intel/twitter/threats 401 in 6ms
GET /api/social-intel/news/articles 401 in 6ms
GET /api/social-intel/alerts 401 in 7ms
GET /api/social-intel/analytics 401 in 14ms
GET /api/social-intel/twitter/threats 401 in 9ms
GET /api/social-intel/news/articles 401 in 9ms
GET /api/social-intel/alerts 401 in 6ms
GET /api/social-intel/analytics 401 in 10ms
GET /api/social-intel/twitter/threats 401 in 9ms
GET /api/social-intel/news/articles 401 in 7ms
GET /api/social-intel/alerts 401 in 11ms
GET /api/social-intel/analytics 401 in 6ms
GET /api/social-intel/twitter/threats 401 in 10ms
GET /api/social-intel/news/articles 401 in 5ms
GET /api/social-intel/alerts 401 in 4ms
○ Compiling /social-intelligence ...
✓ Compiled /social-intelligence in 1873ms (771 modules)
GET /social-intelligence 200 in 1985ms
GET /api/social-intel/analytics 200 in 27ms
GET /api/social-intel/analytics 200 in 28ms
GET /api/social-intel/twitter/threats 200 in 10ms
GET /api/social-intel/twitter/threats 200 in 11ms
GET /api/social-intel/news/articles 200 in 8ms
GET /api/social-intel/news/articles 200 in 8ms
GET /api/social-intel/alerts 200 in 8ms
GET /api/social-intel/alerts 200 in 8ms
GET /api/social-intel/analytics 401 in 7ms
GET /api/social-intel/twitter/threats 401 in 5ms
GET /api/social-intel/news/articles 401 in 6ms
GET /api/social-intel/alerts 401 in 4ms
GET /social-intelligence 200 in 34ms
GET /api/social-intel/analytics 200 in 13ms
GET /api/social-intel/analytics 200 in 15ms
GET /api/social-intel/twitter/threats 200 in 8ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 6ms
GET /api/social-intel/news/articles 200 in 8ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 401 in 7ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 3ms
GET /api/social-intel/alerts 401 in 3ms
GET /api/social-intel/analytics 401 in 5ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 3ms
GET /api/social-intel/alerts 401 in 4ms
GET /api/social-intel/analytics 200 in 8ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 7ms
GET /api/social-intel/analytics 401 in 5ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 5ms
GET /api/social-intel/alerts 401 in 6ms
GET /api/social-intel/analytics 401 in 4ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 3ms
GET /api/social-intel/alerts 401 in 3ms
GET /api/social-intel/analytics 200 in 10ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 6ms
GET /api/social-intel/alerts 200 in 7ms
GET /api/social-intel/analytics 401 in 5ms
GET /api/social-intel/twitter/threats 401 in 3ms
GET /api/social-intel/news/articles 401 in 3ms
GET /api/social-intel/alerts 401 in 5ms
✓ Compiled /api/social-intel/search in 151ms (409 modules)
Backend responded with 422: {"detail":[{"type":"missing","loc":["query","query"],"msg":"Field required","input":null,"url":"https://errors.pydantic.dev/2.5/v/missing"}]}
Search API error: Error: Backend responded with 422
at GET (webpack-internal:///(rsc)/./app/api/social-intel/search/route.ts:39:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
GET /api/social-intel/search?q=gfffffffffffhg 500 in 191ms
✓ Compiled in 80ms (409 modules)
GET /api/social-intel/analytics 401 in 28ms
GET /api/social-intel/twitter/threats 401 in 4ms
GET /api/social-intel/news/articles 401 in 7ms
GET /api/social-intel/alerts 401 in 7ms
GET /api/social-intel/analytics 200 in 11ms
GET /api/social-intel/twitter/threats 200 in 12ms
GET /api/social-intel/news/articles 200 in 7ms
GET /api/social-intel/alerts 200 in 5ms
GET /api/social-intel/analytics 401 in 3ms
GET /api/social-intel/twitter/threats 401 in 7ms
GET /api/social-intel/news/articles 401 in 7ms
GET /api/social-intel/alerts 401 in 6ms
Backend responded with 422: {"detail":[{"type":"missing","loc":["query","query"],"msg":"Field required","input":null,"url":"https://errors.pydantic.dev/2.5/v/missing"}]}
Search API error: Error: Backend responded with 422
at GET (webpack-internal:///(rsc)/./app/api/social-intel/search/route.ts:39:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
GET /api/social-intel/search?q=gfffffffffffhg 500 in 13ms
GET /api/social-intel/analytics 200 in 7ms
GET /api/social-intel/twitter/threats 200 in 8ms
GET /api/social-intel/news/articles 200 in 19ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 401 in 7ms
GET /api/social-intel/twitter/threats 401 in 5ms
GET /api/social-intel/news/articles 401 in 6ms
GET /api/social-intel/alerts 401 in 4ms
GET /api/social-intel/analytics 200 in 6ms
GET /api/social-intel/twitter/threats 200 in 6ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 200 in 12ms
GET /api/social-intel/twitter/threats 200 in 7ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 401 in 10ms
GET /api/social-intel/twitter/threats 401 in 6ms
GET /api/social-intel/news/articles 401 in 6ms
GET /api/social-intel/alerts 401 in 4ms
GET /api/social-intel/analytics 401 in 4ms
GET /api/social-intel/twitter/threats 401 in 3ms
GET /api/social-intel/news/articles 401 in 3ms
GET /api/social-intel/alerts 401 in 3ms
GET /api/social-intel/analytics 200 in 17ms
GET /api/social-intel/twitter/threats 200 in 8ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 401 in 10ms
GET /api/social-intel/twitter/threats 401 in 12ms
GET /api/social-intel/news/articles 401 in 6ms
GET /api/social-intel/alerts 401 in 3ms
Backend responded with 422: {"detail":[{"type":"missing","loc":["query","query"],"msg":"Field required","input":null,"url":"https://errors.pydantic.dev/2.5/v/missing"}]}
Search API error: Error: Backend responded with 422
at GET (webpack-internal:///(rsc)/./app/api/social-intel/search/route.ts:39:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
GET /api/social-intel/search?q=gfffffffffffhg 500 in 22ms
GET /api/social-intel/analytics 401 in 5ms
GET /api/social-intel/twitter/threats 401 in 8ms
GET /api/social-intel/news/articles 401 in 7ms
GET /api/social-intel/alerts 401 in 4ms
Backend responded with 422: {"detail":[{"type":"missing","loc":["query","query"],"msg":"Field required","input":null,"url":"https://errors.pydantic.dev/2.5/v/missing"}]}
Search API error: Error: Backend responded with 422
at GET (webpack-internal:///(rsc)/./app/api/social-intel/search/route.ts:39:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
GET /api/social-intel/search?q=gfffffffffffhg 500 in 21ms
GET /api/social-intel/analytics 200 in 12ms
GET /api/social-intel/twitter/threats 200 in 6ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 8ms
GET /api/social-intel/analytics 401 in 8ms
GET /api/social-intel/twitter/threats 401 in 12ms
GET /api/social-intel/news/articles 401 in 12ms
GET /api/social-intel/alerts 401 in 8ms

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

INFO: Application shutdown complete.
INFO: Finished server process [41262]
INFO: Started server process [41448]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: 127.0.0.1:56592 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:56612 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:56602 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:56592 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:56602 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:56612 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:56602 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:56602 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:56602 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:56612 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:46512 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:46512 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:46548 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46548 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:46532 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:44474 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:44474 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:44474 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:44474 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:59978 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:59978 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:59978 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:59978 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:59982 - "OPTIONS /api/social-intel/twitter/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:59982 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:39820 - "POST /api/social-intel/search HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:55122 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:55122 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:55122 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:55122 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:55138 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:55138 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:37268 - "OPTIONS /api/social-intel/news/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:37280 - "POST /api/social-intel/search HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:37268 - "POST /api/social-intel/news/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:37280 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:37280 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:37280 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:37280 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:46630 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46630 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:46630 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:46630 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:37270 - "POST /api/social-intel/news/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:37764 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:37764 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:37764 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:37764 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:34238 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34238 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34238 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:34238 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:34254 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:34254 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:34254 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:57026 - "POST /api/social-intel/search HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:57026 - "POST /api/social-intel/search HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:45560 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:45560 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:45560 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 422 Unprocessable Entity
INFO: 127.0.0.1:45572 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:45572 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:45572 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:45572 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

└──╼ $npm run dev

[email protected] dev
next dev

▲ Next.js 14.2.31

✓ Starting...
✓ Ready in 1847ms
○ Compiling / ...
✓ Compiled / in 1815ms (722 modules)
GET / 200 in 1932ms
✓ Compiled /social-intelligence in 477ms (743 modules)
✓ Compiled /api/social-intel/analytics in 86ms (413 modules)
GET /api/social-intel/analytics 200 in 147ms
GET /api/social-intel/analytics 200 in 153ms
✓ Compiled /api/social-intel/twitter/threats in 100ms (413 modules)
✓ Compiled (415 modules)
GET /api/social-intel/twitter/threats 200 in 111ms
GET /api/social-intel/twitter/threats 200 in 123ms
✓ Compiled /api/social-intel/news/articles in 82ms (415 modules)
✓ Compiled (417 modules)
GET /api/social-intel/news/articles 200 in 113ms
GET /api/social-intel/news/articles 200 in 119ms
✓ Compiled /api/social-intel/alerts in 67ms (417 modules)
✓ Compiled (419 modules)
GET /api/social-intel/alerts 200 in 111ms
GET /api/social-intel/alerts 200 in 119ms
✓ Compiled in 64ms (419 modules)
GET /api/social-intel/analytics 200 in 34ms
GET /api/social-intel/twitter/threats 200 in 8ms
GET /api/social-intel/news/articles 200 in 8ms
GET /api/social-intel/alerts 200 in 7ms
✓ Compiled /api/social-intel/twitter/start-monitoring in 78ms (421 modules)
Backend responded with 503: {"detail":"Twitter API not configured"}
Twitter monitoring API error: Error: Backend responded with 503
at POST (webpack-internal:///(rsc)/./app/api/social-intel/twitter/start-monitoring/route.ts:30:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
POST /api/social-intel/twitter/start-monitoring 500 in 115ms
✓ Compiled in 92ms (421 modules)
GET /api/social-intel/analytics 200 in 28ms
GET /api/social-intel/twitter/threats 200 in 10ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 18ms
✓ Compiled /api/social-intel/search in 92ms (423 modules)
GET /api/social-intel/search?q=abia 200 in 127ms
✓ Compiled in 72ms (423 modules)
GET /api/social-intel/search?q=abia 200 in 33ms
GET /api/social-intel/analytics 200 in 18ms
GET /api/social-intel/twitter/threats 200 in 17ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 8ms
✓ Compiled /api/social-intel/news/start-monitoring in 68ms (425 modules)
✓ Compiled in 89ms (425 modules)
GET /api/social-intel/search?q=abia 200 in 29ms
POST /api/social-intel/news/start-monitoring 200 in 17331ms
GET /api/social-intel/analytics 200 in 11ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 16ms
GET /api/social-intel/alerts 200 in 7ms
POST /api/social-intel/news/start-monitoring 200 in 12470ms
GET /api/social-intel/analytics 200 in 10ms
GET /api/social-intel/twitter/threats 200 in 10ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 7ms
GET /api/social-intel/analytics 200 in 10ms
GET /api/social-intel/twitter/threats 200 in 7ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 6ms
Backend responded with 503: {"detail":"Twitter API not configured"}
Twitter monitoring API error: Error: Backend responded with 503
at POST (webpack-internal:///(rsc)/./app/api/social-intel/twitter/start-monitoring/route.ts:30:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:57228
at async eT.execute (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:46851)
at async eT.handle (/home/venom/nip/frontend/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:58760)
at async doRender (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1366:42)
at async cacheEntry.responseCache.get.routeKind (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1588:28)
at async DevServer.renderToResponseWithComponentsImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1496:28)
at async DevServer.renderPageComponent (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1924:24)
at async DevServer.renderToResponseImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:1962:32)
at async DevServer.pipeImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:922:25)
at async NextNodeServer.handleCatchallRenderRequest (/home/venom/nip/frontend/node_modules/next/dist/server/next-server.js:272:17)
at async DevServer.handleRequestImpl (/home/venom/nip/frontend/node_modules/next/dist/server/base-server.js:818:17)
at async /home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:339:20
at async Span.traceAsyncFn (/home/venom/nip/frontend/node_modules/next/dist/trace/trace.js:154:20)
at async DevServer.handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
at async invokeRender (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:179:21)
at async handleRequest (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:359:24)
at async requestHandlerImpl (/home/venom/nip/frontend/node_modules/next/dist/server/lib/router-server.js:383:13)
at async Server.requestListener (/home/venom/nip/frontend/node_modules/next/dist/server/lib/start-server.js:141:13)
POST /api/social-intel/twitter/start-monitoring 500 in 11ms
GET /api/social-intel/analytics 200 in 15ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 10ms
GET /api/social-intel/alerts 200 in 7ms
GET /api/social-intel/search?q=enugu 200 in 22ms
GET /api/social-intel/analytics 200 in 14ms
GET /api/social-intel/twitter/threats 200 in 8ms
GET /api/social-intel/news/articles 200 in 8ms
GET /api/social-intel/alerts 200 in 7ms
GET /api/social-intel/analytics 200 in 11ms
GET /api/social-intel/twitter/threats 200 in 9ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 6ms
GET /api/social-intel/analytics 200 in 9ms
GET /api/social-intel/twitter/threats 200 in 6ms
GET /api/social-intel/news/articles 200 in 9ms
GET /api/social-intel/alerts 200 in 8ms

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

──╼ $uvicorn app.main:app --host 0.0.0.0 --port 8080 --reload
INFO: Will watch for changes in these directories: ['/home/venom/nip/backend']
INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
INFO: Started reloader process [42464] using WatchFiles
INFO: Started server process [42466]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: 127.0.0.1:58126 - "OPTIONS /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:58126 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:58126 - "GET /api/users/me HTTP/1.1" 200 OK
INFO: 127.0.0.1:34992 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34998 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34992 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34998 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:34992 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:34998 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:34992 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:34998 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:51292 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:51292 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:51292 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:51292 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:57940 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 503 Service Unavailable
INFO: 127.0.0.1:47218 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:47218 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:47218 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:47218 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:47222 - "POST /api/social-intel/search?query=abia HTTP/1.1" 200 OK
INFO: 127.0.0.1:43768 - "POST /api/social-intel/search?query=abia HTTP/1.1" 200 OK
INFO: 127.0.0.1:36744 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:36744 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:36744 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:36744 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:35778 - "POST /api/social-intel/search?query=abia HTTP/1.1" 200 OK
INFO: 127.0.0.1:36760 - "POST /api/social-intel/news/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:36760 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:36760 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:36760 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:36760 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:45430 - "POST /api/social-intel/news/start-monitoring HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:35122 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:50416 - "POST /api/social-intel/twitter/start-monitoring HTTP/1.1" 503 Service Unavailable
INFO: 127.0.0.1:50700 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:50700 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:50700 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:50700 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:50710 - "POST /api/social-intel/search?query=enugu HTTP/1.1" 200 OK
INFO: 127.0.0.1:57972 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:57972 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:57972 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:57972 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:57982 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:57982 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:57982 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:57982 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK
INFO: 127.0.0.1:55794 - "GET /api/social-intel/stats HTTP/1.1" 200 OK
INFO: 127.0.0.1:55794 - "GET /api/social-intel/twitter/threats HTTP/1.1" 200 OK
INFO: 127.0.0.1:55794 - "GET /api/social-intel/news/articles HTTP/1.1" 200 OK
INFO: 127.0.0.1:55794 - "GET /api/social-intel/alerts HTTP/1.1" 200 OK

@luckysitara
Copy link
Author

luckysitara commented Aug 31, 2025

Screenshot at 2025-08-31 14-14-15

@luckysitara
Copy link
Author

luckysitara commented Sep 4, 2025

https://v0.app/chat/back-sxlAWXLrUvN

@luckysitara
Copy link
Author

luckysitara commented Sep 4, 2025

Screenshot at 2025-09-04 13-34-50

@luckysitara
Copy link
Author

luckysitara commented Sep 10, 2025

https://v0.app/chat/remix-of-intel-x-clone-825tOROA60Y
https://v0.app/chat/remix-of-tool-UMT37VpJWCj

@luckysitara
Copy link
Author

luckysitara commented Sep 11, 2025

Persist cookies between sessions to avoid repeated logins, using a library like selenium-wire or browsercookie.
Rotate user agents using a library like fake-useragent.
Use a headless browser with stealth capabilities (e.g., undetected-chromedriver) to further reduce detection risks.

@luckysitara
Copy link
Author

luckysitara commented Sep 13, 2025

https://v0.app/chat/remix-of-remix-0sg8NT199Gc

@9ightven0m
Copy link

9ightven0m commented Oct 30, 2025

https://v0.app/chat/dope-TPq202FDqyd?ref=IVT3GF

@9ightven0m
Copy link

9ightven0m commented Oct 30, 2025

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

@luckysitara
Copy link
Author

luckysitara commented Oct 31, 2025

Build a complete Solana wallet analysis platform called Piflepath inspired by Solscan.io with the following features:

Brand & Design

  • Brand name: Piflepath
  • Use Solscan-inspired color scheme: Deep purple (#9945ff), cyan (#00d4ff), neon green (#14f195), and dark backgrounds
  • Modern, professional, data-focused UI matching Solscan.io aesthetic
  • Responsive design optimized for mobile and desktop

Authentication & Wallet Connection

  • Solana wallet connection using Phantom, Solflare, and other popular wallets
  • Simplified "Connect Wallet" button with dropdown menu for wallet selection
  • Use Solflare/Phantom wallet address as user identifier
  • Wallet authentication for accessing dashboard and API features

Core Features

1. Wallet Search & Analysis

  • Input field for searching any Solana wallet address
  • Real-time validation of Solana base58 addresses (32-44 characters)
  • Integration with Solscan API endpoints to fetch real wallet data
  • Display wallet analysis on landing page without requiring login

2. Wallet Details Display(Similar to Solscan.io)

  • Balance Overview: Show SOL balance with 24h change percentage

  • Token Holdings: Display all SPL tokens in wallet with prices and value changes

  • Transaction History: Show recent transactions with:

  • Transaction type (send, receive, swap, stake)

  • Amount and token involved

  • Timestamps and status

  • Links to view on blockchain explorer

  • Portfolio Analytics:

  • 7-day trading volume chart

  • Portfolio allocation pie chart

  • Token breakdown by percentage

  • Transaction type distribution

  • Summary Stats: Total balance, token count, transaction count

3. Dashboard (For Connected Users)

  • Show wallet statistics and holdings
  • Quick access to analyze other wallets
  • Export wallet report functionality
  • Real-time portfolio performance

4. Subscription & Monetization

  • Three subscription tiers:

  • Free: Limited API calls, basic wallet analysis

  • Pro: 0.5 SOL/month, higher API rate limits, advanced analytics

  • Enterprise: 2 SOL/month, unlimited API calls, priority support

  • Solana blockchain payments (using connected wallet for payment)

  • Subscription management dashboard showing active plan and usage

5. API Keys & Developer Features

  • Generate API keys for developers to use Piflepath API
  • Display API documentation with example requests
  • Track API usage and rate limits per key
  • Show remaining credits/requests

Backend & Data

Database Schema

  • users table: Wallet address, subscription tier, created_at
  • subscription_plans table: Plan name, price in SOL, features, limits
  • user_subscriptions table: User, active plan, renewal date
  • api_keys table: User, key, created_at, last_used
  • usage_tracking table: API key, requests count, date
  • payments table: User, amount in SOL, transaction hash, status

API Integration

  • Create backend proxy to Solscan API endpoints:

  • /api/wallet/fetch - Get wallet balance and token holdings

  • /api/wallet/transactions - Get transaction history

  • /api/wallet/tokens - Get detailed token information

  • /api/wallet/analytics - Get portfolio analytics data

  • Handle CORS issues with server-side API proxying

  • Implement error handling and rate limiting

Pages & Components

  1. Landing Page:

  2. Hero section with wallet search integration

  3. Feature showcase with Solscan-inspired cards

  4. Pricing section with SOL-based plans

  5. How-it-works section

  6. Call-to-action buttons

  7. Dashboard Page (Protected):

  8. Wallet statistics cards

  9. Token holdings list

  10. Transaction history with filters and sorting

  11. Portfolio analytics charts

  12. API key management section

  13. Wallet Analysis Page:

  14. Full wallet details display (transaction history, tokens, analytics)

  15. Export functionality

  16. Share wallet analysis link

  17. Subscription Page:

  18. Plan comparison table

  19. Upgrade/downgrade options

  20. Solana payment integration for plan changes

  21. Settings Page:

  22. API key management (create, revoke, view usage)

  23. Account settings and wallet management

Technical Stack

  • Framework: Next.js 16 (App Router)
  • Frontend: React 19 with TypeScript
  • Styling: Tailwind CSS v4 with custom theme
  • Authentication: Solana wallet adapters
  • Charts: Recharts for analytics visualization
  • API: Server-side fetching with error handling
  • Database: Supabase (PostgreSQL)
  • Payments: Solana blockchain direct transfers

Key Features Summary

✅ Search any Solana wallet and view analysis
✅ Real-time transaction history and token holdings
✅ Portfolio analytics with interactive charts
✅ Solana wallet authentication
✅ SOL-based subscription plans
✅ Developer API with keys and rate limiting
✅ Responsive design matching Solscan aesthetic
✅ Complete dashboard with statistics
✅ Export and share wallet reports

@luckysitara
Copy link
Author

luckysitara commented Nov 1, 2025

https://forms.office.com/pages/responsepage.aspx?id=mXx1gcqE8Ui4kVed91pA_IIXipSSNbxCsRaLuZdb4XVURUc2VzZWWTZRNFdNNUlOUTI5Vkw0NEFOUy4u&route=shorturl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment