Chapi Dev Talks
My name is Chapi and I am a Developer. I post my thoughts about tech here. Message to our assistant to give U Feedback: @sophiservebot Join https://t.me/chapidevtalks_group
Ko'proq ko'rsatish📈 Telegram kanali Chapi Dev Talks analitikasi
Chapi Dev Talks (@chapidevtalks) Ingliz til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 10 449 obunachidan iborat bo'lib, Texnologiyalar & Aralashmalar toifasida 11 703-o'rinni va Efiopiya mintaqasida 3 281-o'rinni egallagan.
📊 Auditoriya ko‘rsatkichlari va dinamika
невідомо sanasidan buyon loyiha tez o‘sib, 10 449 obunachiga ega bo‘ldi.
26 Oktabr, 2026 dagi oxirgi ma’lumotlarga ko‘ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni 127 ga, so‘nggi 24 soatda esa 7 ga o‘zgardi va umumiy qamrov yuqori darajada qolmoqda.
- Tasdiqlash holati: Tasdiqlanmagan
- Jalb etish (ER): Auditoriya o‘rtacha 29.73% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining 13.90% ini tashkil etuvchi reaksiyalarni to‘playdi.
- Post qamrovi: Har bir post o‘rtacha 3 107 marta ko‘riladi; birinchi sutkada odatda 1 453 ta ko‘rish yig‘iladi.
- Reaksiyalar va o‘zaro ta’sir: Auditoriya faol: har bir postga o‘rtacha 28 ta reaksiya keladi.
- Tematik yo‘nalishlar: Kontent developer, database, dataset, addis, dataset.et kabi asosiy mavzularga jamlangan.
📝 Tavsif va kontent siyosati
Muallif resursni shaxsiy fikrni ifoda etish maydoni sifatida ta’riflaydi:
“My name is Chapi and I am a Developer.
I post my thoughts about tech here.
Message to our assistant to give U Feedback: @sophiservebot
Join https://t.me/chapidevtalks_group”
Yuqori yangilanish chastotasi (oxirgi ma’lumot 27 Oktabr, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli bo‘lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Texnologiyalar & Aralashmalar toifasidagi muhim ta’sir nuqtasiga aylantirishini ko‘rsatadi.
sudo mkdir -p /etc/systemd/resolved.conf.d/
sudo tee /etc/systemd/resolved.conf.d/dns.conf <<EOF
[Resolve]
DNS=1.1.1.1 1.0.0.1
FallbackDNS=9.9.9.9
EOF
sudo systemctl restart systemd-resolved
Your mileage may vary, but fixing DNS can make a noticeable difference.
Bandwidth affects how much data you move. DNS affects how quickly connections get started.
export AWS_REQUEST_CHECKSUM_CALCULATION=when_required
export AWS_RESPONSE_CHECKSUM_VALIDATION=when_required
aws s3 cp ./hello.txt s3://YOUR_BUCKET/hello.txt \
--profile telecloud \
--endpoint-url https://obsv3.et-global-3.ethiotelecom.et \
--region et-global-3
Those checksum settings helped us resolve an upload compatibility error. Check your bucket’s endpoint if you use another region.
We’ve written a practical guide based on moving a production application to Telecloud: the two login portals, Chrome password confusion, creating a VPC and subnet before your VPS, networking, backups, and how AI agents helped us through the setup.
Hopefully it saves you some of the trial and error we went through 🙂
[Read the Telecloud field guide](https://snapwre.com/blog/ethio-telecom-telecloud-guide)