- Why “AI-powered” is accurate
- Key difference: fully local AI, no external API
- Core algorithms by feature group
- Recommendations
- Search & Discovery
- Notifications & Scheduling
- Behavior Analytics
- Input data & technical stack
- Business benefits (measurable)
- Transparent methodology
- Compared to “AI” via external APIs
- Typical use cases
- Quick FAQ
- Conclusion
Why “AI-powered” is accurate
- Self-learning from data: learns from tens of thousands of reading events, no fixed rules.
- Probabilistic decisions: time-decay, smoothing, and Bayesian shrinkage reduce noise/sparse data.
- Personalization at scale: every user receives unique suggestions/schedules/notifications based on their profile and community similarity.
- Continuous optimization: measures success rate and improves release timing, titles, and recommendations over time.
Key difference: fully local AI, no external API
- Runs on-site: all processing happens in WordPress/PHP/MySQL, no user data leaves your server.
- Stable & controlled: no API quota/policy issues; performance is guaranteed with caching, batching, indexing.
- Privacy-first: reading history and user behavior stay entirely inside your system.
Core algorithms by feature group
Recommendations
- Trending: growth rate of views per hour/day, time-decay, quality/engagement, topic momentum; diversity filter prevents “one author/genre domination.”
- What to read today? merges multiple sources: favorite genres, collaborative from similar readers, trending in interest groups, and new releases; weighted merge for final ranking.
- Readers also viewed: item-based collaborative filtering (Jaccard + confidence), excluding already read/followed titles; robust even with sparse data.
- Next-Best Read (NBR): sequential A→B recommendations within 36h (lookback 120 days, half-life 30 days). Uses CTE + window functions (MySQL 8+/MariaDB 10+), with Bayesian smoothing + base popularity P(B) + lift (λ=0.3). Cached (8h) with reason strings like “
XX% chose this · ×above avg.” - Smart Finish Reminder (SFR): detects near-finished titles: progress ≥ 70% but not completed; marked “interrupted” if inactive ≥ 36h; reminder cooldown 24h, max 6 titles. Progress calculated with
COUNT(DISTINCT chapter_id).
Search & Discovery
- Bigram Keyword Generator (BM25 + NPMI + LLR): generates high-quality 2-word phrases for Init Live Search. Uses titles (×3 weight), unigram scoring with BM25 (k1=1.5, b=0.75, weighted by view/comment), then bigram + NPMI + LLR (Dunning). Filters and selects 15 diverse keywords (anti-duplicate).
Notifications & Scheduling
- Golden release hours: analyzes 7×24 slots, half-life, kernel smoothing, Bayesian shrinkage, z-score uplift vs baseline; picks multiple top slots with spacing.
- Personalized notifications: scheduled by golden hours, target users via aggregate queries (no N+1), content from reading profile/new chapters/suitable recs; measures performance per slot.
Behavior Analytics
- Reader Drop-off Analytics: hazard estimation of stopping per chapter, 14-day grace, half-life 60 days, prior Beta(1,19). Outputs “drop-off peaks” (badge) + full series for charting; runs on window functions, no schema changes.
Input data & technical stack
- Reading logs & profiles: detailed reading history (time, manga, chapter, user); profiles by genre/team/author/intensity/followed titles.
- Time normalization: UTC-based, converted to WordPress timezone for scheduling; supports minute offsets.
- Performance: adaptive caching, batch ~50 users, micro-delays to avoid bursts, indexed queries.
- Advanced SQL: NBR & Drop-off require window functions + CTE ⇒ MySQL ≥ 8.0 or MariaDB ≥ 10.x.
- Security & permissions: AJAX admin requires
manage_options+ valid WP nonce (X-WP-Nonce); rejects unauthorized calls. - Optimized Init Live Search: queries IDs only (
fields:'ids'), Unicode normalization, stop words/phrases by locale (filterable). - Caching & stampede protection:
set_transient()with lock; TTL: NBR 8h, Drop-off 6h. - Index recommendations:
(user_id, manga_id, read_at)for reading logs;(manga_id, chapter_number)for chapters.
Business benefits (measurable)
- Boosted release-day views: chapters land in peak activity hours.
- Smarter weekly scheduling: multiple good slots balance hot vs. growth titles.
- Higher retention & DAU: personalized recs + streaks bring users back daily.
- SEO impact: content hits the right audience at the right time, improving dwell time & internal CTR.
Transparent methodology
- Time-decay weighting: exponential decay (half-life) prioritizes recent signals.
- Smoothing: hourly kernel smoothing + Bayesian shrinkage stabilize thin data.
- Uplift vs. baseline: 168 weekly cells (24/day); z-score ensures confident slot selection.
- NBR: A→B chains in 36h, half-life 30d, Bayesian + lift reduce bias toward global hits.
- SFR: ≥70% progress + 36h inactivity + 24h cooldown; list limited to avoid spam.
- Drop-off reliability: prior Beta(1,19) (~5%) + neighbor smoothing stabilize hazard; badge shows effective sample size.
- Bigram keywords: BM25 + NPMI + LLR with soft thresholds and lexical diversity.
Compared to “AI” via external APIs
- No third-party dependency: immune to model changes/quota limits.
- Cost efficiency: no per-call API fees; performance is tunable locally.
- Deep customization: half-life, alpha, slot count, spacing, kernels, thresholds… all adjustable to site context.
Typical use cases
- Multi-slot releases: distribute series across golden hours, avoid cannibalization.
- Push new series: target uplift slots + notify genre-similar readers.
- Re-activate dormant users: send daily-best recs based on past favorite genres.
Quick FAQ
- Is it really AI? Yes — statistical models & collaborative filtering, learning from real data, not rule-based.
- Need external APIs? No — fully local in WordPress/PHP/MySQL.
- Does it show confidence? Yes — uplift %, z-score, drop-off badges with effective sample size.
- How does NBR work? Tracks “after finishing A, what B within 36h” + half-life, Bayesian smoothing, lift.
- Does SFR spam? No — only when ≥70% + inactive ≥36h; cooldown 24h; max 6 titles.
- Does keyword gen read content? No — titles only (×3 weight) for speed & less noise.
Conclusion
AI-powered is not a slogan. Init Manga combines statistical algorithms & collaborative filtering — running entirely in WordPress — to turn reading data into smarter release timing, recommendations, and notifications with measurable impact. Enable golden hours, set slot count & spacing, monitor uplift/success rate for a few weeks, then fine-tune half-life, kernel, alpha to match real traffic. As data grows, the system learns better and builds lasting competitive advantage for your site.
Note: Most modern WordPress hosting/VPS already meets requirements (MySQL 8+/MariaDB 10+ for NBR/Drop-off).
Comments