Definir as métricas do piloto, a telemetria mínima e o critério Nostr
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the referenced sections of docs/design.md (lines 144, 181, 185, and 214) to understand the pilot and current P2P design. Define the metrics and numerical thresholds, the minimum telemetry decision, and the criteria for switching to Nostr with Brazilian relays; then record the telemetry decision in the RIPD and policy. Done means all decisions and thresholds appear in the named documents.
Written by the indexing model from the issue text.
Description
Contexto
O piloto existe para provar que a rede funciona antes do convite ao canal, mas não há métricas, telemetria nem o critério que faria trocar a pilha P2P por Nostr. Qualquer telemetria exige consentimento e coleta mínima; a retenção de logs de acesso segue o parecer.
Escopo
- Métricas: tempo de sync, cobertura de A Rua, falhas de conexão, consumo de dados, prazos de moderação
- Decidir telemetria mínima com consentimento ou nenhuma, e relatório de falhas
- Critério escrito de troca para Nostr com relays brasileiros
- Limiares numéricos a medir nos ensaios de escala e no piloto
Critérios de aceite
- As métricas, os limiares e o critério estão no design.md
- A decisão de telemetria consta no RIPD e na política
Fontes
Fase: Fase 1 — Piloto 18+ · Dificuldade: pequena
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Varanda-org/varanda
-
área:app área:produto sem-fase tipo:decisão
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Varanda-org/varanda#91 ·
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
-
área:identidade área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#92 ·
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
-
área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#89 ·
All issues in Varanda-org/varanda
Similar issues
-
bug needs triage P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pbakaus/impeccable#1143 ·
Maintainers usually reply within 1 day
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
next() is called twice when the request closes after busboy fails to startPossibly taken @NgoQuocViet2001 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day