f8072ab339
Logs into a real Telegram account via MTProto (GramJS) rather than a bot, so it can read any public channel's history. API ID/hash and the login session are entered through the admin Connections panel and stored encrypted at rest (new storage/crypto.ts AES-256-GCM helper) rather than via .env. Messages render as their own TelegramCard (same treatment as tweets) and open the original message on Telegram instead of an internal article page; attached media/albums are downloaded and self-hosted at ingestion time since Telegram has no public hotlinkable media URL. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014c1L8ghNBFjfiH64UMViP8
30 lines
784 B
JSON
30 lines
784 B
JSON
{
|
|
"name": "homefeed-backend",
|
|
"version": "1.0.0",
|
|
"description": "Homefeed backend — ingestion, clustering, synthesis, and the public/admin API",
|
|
"type": "module",
|
|
"main": "dist/index.js",
|
|
"scripts": {
|
|
"dev": "tsx watch --env-file=.env src/index.ts",
|
|
"build": "tsc",
|
|
"start": "node --experimental-sqlite dist/index.js",
|
|
"typecheck": "tsc --noEmit"
|
|
},
|
|
"license": "UNLICENSED",
|
|
"dependencies": {
|
|
"@fastify/cookie": "^11.1.2",
|
|
"@fastify/cors": "^11.3.0",
|
|
"@mozilla/readability": "^0.6.0",
|
|
"fastify": "^5.10.0",
|
|
"jsdom": "^29.1.1",
|
|
"rss-parser": "^3.13.0",
|
|
"telegram": "^2.26.22"
|
|
},
|
|
"devDependencies": {
|
|
"@types/jsdom": "^28.0.3",
|
|
"@types/node": "^26.1.1",
|
|
"tsx": "^4.23.0",
|
|
"typescript": "^7.0.2"
|
|
}
|
|
}
|