Rᴇɴᴅʏ Pʀᴏɪᴇᴄᴛs
224 subscribers
1.04K photos
29 videos
17 files
743 links
tgcore is open source. Built for production Telegram apps.

https://github.com/TeamKillerX/tgcore/
Download Telegram
Too many methods.
Methods are noise.
Architecture is control.
# Not too many
async def something(**kwargs):
return await FollowAPIReadDocs(kwargs)

# Now you can like this
await something(
chat_id=chat_id,
text=text,
reply_markup={"inline_keyboard": []}
)

Abstraction beats methods.
Developer call method.
Architect define structure.
Developers read docs.
Architect writes the docs.
❤1
Mereka masih coding.
Gua udah jadi sistemnya.
They're looking for parameters.
I'm the one who defines the structure. 💀

Final form
This channel automatically deletes zombie accounts by telegram 💀
Telegram Bot API: new feature released
Me: was asleep
Me 10 minutes later: already deployed.
Engineer: Fixing bugs.
Architect: Creating constraints.
If you use InlineKeyboardMarkup([])

Or JSON:
reply_markup={"inline_keyboard": []}

Because it's too much

Try to see if you can do it like this:
KeyboardBuilder().url("Custom Name", "https://google.com").build()

Clean, no need to say much more.
TGCore TS Client • Production Ready

Docs: https://tgcore.ryzenths.dpdns.org/

Web: https://services-pro.ryzenths.dpdns.org

Install:
npm install @xtsea/tgcore-ts

Usage:
import { Client } from "@xtsea/tgcore-ts"

const tg = new Client({
api_key: process.env.R_API_KEY,
base_url: "https://tgcore.ryzenths.dpdns.org"
})

• Service migrated to new URL
• Production stable
• No configuration issues
• Enterprise-ready
import { tgcore } from "@xtsea/tgcore-ts"

const tg = tgcore({
api_key: "api key here"
})

const result = await tg.orweb
.pinterest()
.query("Coding")
.limit(10)
.execute()

if (!result.ok) return null

return result.data
Integration with other applications

tgcore-ts is not a bot framework.

It is a Telegram API client SDK designed for:
• automation
• monitoring
• microservices
• web applications

Supported environments:
• Next.js
• Express / Fastify API
• Cloudflare Workers
• Server monitoring systems
• AI services / automation
• Microservices

Examples:
app.post("/alert", async (req, res) => {

await tg.calls
.sendMessage()
.chatId(LOG_CHAT)
.text(req.body.message)
.execute()

res.send("ok")
})

Architecture comparison

tgcore-ts
• Bot runtime: not required
• Webhook service: native
• Microservice: first-class
• Automation: designed for it

Telegraf / grammY
• Bot runtime: required
• Webhook service: limited
• Microservice: less suitable
• Automation: possible but not optimized

Think of tgcore-ts like Stripe SDK, but for Telegram automation.
🔥1
Top:
When you use Pyrogram + FastAPI
but your bot runtime goes down without webhook

Bottom:
Meanwhile tgcore:
Sleeping… still sending messages automatically.
ev tg.base_url = "https://tgcore.ryzenths.dpdns.org"

kw = await tg._post(
"/api/web/pinterest",
payload={"query": "pocong"}
)
if not kw["ok"]:
return None

await tg.raw.sendPhoto(
chat_id=m.chat.id,
caption="Result from Pinterest",
photo=kw["data"]["pins"][0]["media"]["images"]["orig"]["url"]
).execute()
Result from Pinterest