Channel
@pieceJS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
431subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001588139153 |
|---|---|
| Type | Channel |
| Username | @pieceJS |
| Description | شاید اینا تکات ساده ای باشند اما بعضاً به پهنای دو روز باگ برای من بوده اند 🤓 آدرس گروه: @iran_javascript_group ———————————————— ☕️ Java Channel: @pieceJava 📒 JavaScript Channel: @pieceJs |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pieceJS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 05:18 | 431 | no change |
| 8 Aug 2026, 04:30 | 431 | first reading |
20 posts held, back to 11 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
110 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 74.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 82 | 74.5% | |
| 😁 | 12 | 10.9% | |
| 🗿 | 6 | 5.45% | |
| 👌 | 5 | 4.55% | |
| 🤣 | 2 | 1.82% | |
| 🆒 | 1 | 0.909% | |
| 👎 | 1 | 0.909% | |
| 🔥 | 1 | 0.909% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 110reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 11 November 2024 to 14 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💎 یه اشتباه لوکس در MongoDB هنگام نوشتن سیستم لاگر برای طراحی دیتابیس یه سیستم لاگر شاید فکر کنی اگر تمام لاگها یا فعالیتهای کاربر تو یه نشست رو بریزی داخل یه آرایه توی همون داکیومنت کاربر، کارِت راحت میشه و با یه کوئری کل دیتای نشست رو دریافت میکنی. اما اشتباه دقیقاً همینجاست! اگر فعالیتهای کاربر زیاد بشه (مثلاً ۱۰۰۰ تا کلیک کنه)، حجم اون سند مدام بزرگتر میشه. این یعنی کندی شدید دیتابیس، درگیر شدن شدید رم و در…
🔥1
یه سوءتفاهم رایج توی خیلی از کدبیس ها اینه که فکر می کنیم چون داخل سرور درست هندل شده، پس نوع HTTP Method مهم نیست. در حالی که API فقط اجرا نیست، قرارداده. متد HTTP Method یعنی: من دارم چی کار می کنم؟ نه اینکه: تو سرور چجوری نوشتمش. متد PATCH یعنی دارم فقط بخشی از یک resource رو تغییر می دم، متد PUT یعنی جایگزینی کامل، وقتی مینویسم POST یعنی… یه کار مبهم. اینکه همه این ها رو با POST بزنیم شاید الان کار کنه، و…
👍5
#مثبت_برنامه_نویس وقتی کارت گرافیک گیر می کنه یا صفحه تار شد: Win + Ctrl + Shift + B درایور گرافیک ریست میشه و همه چیز سر جای خودش برمی گرده معمولاً حین بازی های سنگین، تدوین های خفن یا ارائه با ویدئو پرژکتور این موارد زیاد پیش میاد #خودمم_میدونم_ربطی_هم_به_جاوا_اسکریپت_نداره_😭 🌐 @pieceJS
👌5😁3
💎 متغیر های محیطی در نکست جی اس * متغیرهای محیطی معمولی مثل IS_DEV فقط توی سرور قابل دسترسی هستند، یعنی وقتی کد توی سرور اجرا می شه می تونی به اونا دسترسی داشته باشی. * متغیر هایی که اسمشون با NEXT_PUBLIC_ شروع می شه مثل NEXT_PUBLIC_IS_DEV هم توی سرور و هم توی مرورگر (کلاینت) قابل دسترسی هستند. * یعنی اگر NEXT_PUBLIC_IS_DEV را تعریف کنی، تو هر جای پروژه میتونی از ازشون استفاده کنی، چه سرور باشد چه مرورگر، مثلا این…
👍5
از اولین کسانی که شغلش رو به خاطر ایآی از دست داد؛ تام بود (:
🗿5😁2🤣1
💎 فرق ?? و || در جاوااسکریپت چیه؟ const age = props.age ?? ""; حالا چرا به جای || از ?? استفاده شده؟ 🧐 تفاوتش اینجاست: 🔷 اپرتور ?? فقط وقتی مقدار null یا undefined باشه، سمت راست رو جایگزین میکنه. 🔷 ولی || هر چیزی که Falsy باشه (مثل "", 0, false) رو رد میکنه! نمونش: const a = "" ?? "default"; // => "" const b = "" || "default"; // => "default" پس اگه میخوای مقدارهایی مثل "" یا 0 رو نگه داری، از ?? استفاده…
👍9🗿1
💎 نکته در مورد استفاده از هوک useEffect در ریکت سعی کنید همیشه از مقادیر Primitive Type به عنوان Dependency استفاده کنید. استفاده از مقادیر Reference Type نظیر آبجکت ها موجب رندر های غیر ضروری بسیاری میتونه بشه اما اگه نیاز بود حتماً یه متغیر رفرنس تایپ رو به عنوان وابستگی به useEffect بدید سعی کنید فقط یکی از پرارپتی های Primitive Typeش رو به عنوان وابستگی بدید مثلاً user.firstName بدید نه خود user رو. 🌐 @pieceJ
👍9
دوستان عزیزم، بعد از 15 سال سابقه طراحی سایت و وب نصیحت دلسوزانه ای دارم برای کسانی که تازه میخوان مسیر JS رو پیش بگیرند. باشد که هم ثوابی برا ما بشه هم نکته مفیدی برای شما بمونه از این حقیر 😁
😁7👎1🤣1
💎 یه تریک اچ تی ام الی برای اینکه تمام تگ های <br/>درون یه بلاک اچ تی ام ال از کار بندازید کافیه بهش استایل زیر بدید. div br{ display: none; } 🌐 @pieceJS
👍5
💎 دو واجب مهم برای هر Next.js دولوپر! اولیش: Rate Limiting با استفاده از پکیجهایی مثل express-rate-limit، تعداد درخواستهای کاربران رو محدود کن تا از حملات DDoS و سوء استفاده جلوگیری کنی. npm install express-rate-limit و دومیش: Proxy با تنظیم پروکسی در next.config.js، مشکلات CORS رو حل کن و آدرس سرور اصلی رو مخفی نگه دار. // next.config.js module.exports = { async rewrites() { return [ { …
💎 معرفی PlayCanvas: یک کتابخانه حرفهای برای ایجاد اپلیکیشنهای 3D اگر به دنبال یک کتابخانه سبک و قدرتمند برای ایجاد اپلیکیشنهای 3D با استفاده از React هستید، PlayCanvas گزینهای عالی برای شماست! این کتابخانه به شما امکان میدهد تا به سادگی و با استفاده از قابلیتهای پیشرفتهای مانند پشتیبانی از رویدادهای اشاره، فیزیک، و Gaussian splats، اپلیکیشنهای خیرهکننده و تعاملی بسازید. پکیج PlayCanvas به شما این امکان را …
👍3
💎 مشکل استایل های راستچین برای برخی پکیج های اسلایدر اگه اسلایدر کار میکنه ولی تصاویر نشون داده نمیشن، ممکنه مشکل از direction: rtl; باشه! بعضی اسلایدرها فقط با ltr درست کار میکنن. کافیه جهت رو تست کنید، شاید همین یه تغییر مشکل شما رو مثل من حل کنه 🌐 @pieceJS
👍2
Showing the 12 most recent of 20 posts we hold for @pieceJS. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 444,014 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.
“تیکه پاره های جاوا اسکریپت” (@pieceJS), 431 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pieceJS.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.