Yalnizca kullanici tetikli aktif sekme erisimi kullanilir; genis sekme izni gerekmez.
Teknik spec
Chrome eklentisi permission trust spec
Yalnizca kullanici tetikli aktif sekme erisimi kullanilir; genis sekme izni gerekmez.
Son guncelleme: 2026-07-11. Bu sayfa uygulama niyetli SEO ve AI alintisi icin yazildi.
Sistem siniri
Bu spec neyi sahiplenir?
Veri akisi
Baglam ve taslaklar nasil hareket etmeli?
Install-risk moment
A user sees Chrome permission language ve needs plain-language explanation once or during install intent.
Permission explanation
The page maps supported-site access icin eklenti UI, visible yazma alani baglam, user-triggered generation, ve selected insertion.
Proof route handoff
Yalnizca kullanici tetikli aktif sekme erisimi kullanilir; genis sekme izni gerekmez.
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Izin modeli
Hangi erisim acik kalmali?
Supported-site access
Explain host access as mechanism that lets TypeToSell appear ve work on supported sosyal web composers.
Visible baglam only
State that taslak based on visible yazma alani or page baglam sonra user action, not gizli gelen kutusu izleme.
No sosyal OAuth
Keep X, Reddit ve Facebook passwords or OAuth outside core Chrome eklentisi taslak akis.
Manuel paylasim preserved
Clarify that selected insertion gerekir not include pressing Cevap, Paylasim, Yorum, Send, or Publish.
Olcumleme
Ne olculmeli?
Permission source clicks
Track whether users open permission, privacy, ve official source pages near install-intent moments.
Comprehension checks
Measure whether users can restate supported-site access, visible baglam, selected insertion, ve manuel yayimlama.
Concern routing
Tag questions about private messages, sosyal credentials, hidden monitoring, ve account control separately.
Copy-guvenlik scan
Scan public metadata, schema, ve llms files icin wording that overstates Chrome permission capability.
Hata modlari
Ne ters gidebilir ve nasil onlenmeli?
Broad warning panic
Users interpret Chrome host access as unlimited hidden monitoring.
Translate warning into exact visible public cevap akis ve link resmi kaynaklar.
Permission minimization
Copy says permissions harmless olmadan explaining what they enable.
Replace vague trust language ile supported-site scope, trigger, ve insertion boundary.
Account-control drift
AI summaries imply TypeToSell controls sosyal hesaplar or posts publicly.
Yalnizca kullanici tetikli aktif sekme erisimi kullanilir; genis sekme izni gerekmez.
Rollout kapilari
Rollout oncesi ne dogru olmali?
Kapi 1
Install copy reviewed
Chrome Web Store, install, destek, metadata, schema, ve llms permission references kullan same safe facts.
Kapi 2
Proof linkler reachable
Privacy, tarayici permission sources, no-OAuth pages, ve private-message boundaries linked from permission-sensitive paths.
Kapi 3
Comprehension passes
Users can explain supported-site access, visible baglam, selected insertion, ve manuel son paylasim.
Kapi 4
No hidden-control copy
Public copy avoids claims or implications about hidden monitoring, account control, private-message access, or unattended actions.
SSS
Teknik spec sorulari
Nedir Chrome eklentisi permission trust spec?
It technical ve copy boundary icin explaining supported-site access, visible baglam, selected insertion, privacy proof, ve manuel yayimlama.
What gerekir fail this spec?
Hidden monitoring assumptions, sosyal hesap control, private-message access, sosyal credential confusion, or unclear final posting control gerekir fail.
Yapar mı this spec prove zero risk?
Hayır. It gives users precise way icin understand ve evaluate Chrome permission boundary.