silberengel/next.orly.dev - next.orly.dev - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
woikos	c5be98bcaa	fix(curating): correct pubkey hash computation and UI field name - Fix countEventsForPubkey to use SHA256 hash of pubkey (first 8 bytes) matching the PubHash type used in the Pubkey index - Fix UI to use event_count field instead of total_events Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	0e87337723	feat(curating): add scanpubkeys API method to retroactively populate unclassified users - Add ScanAllPubkeys method to scan SerialPubkey index for all pubkeys - Count events for each pubkey using the Pubkey index - Store event counts in CURATING_ACL_EVENT_COUNT_ prefix - Add NIP-86 "scanpubkeys" API endpoint to trigger the scan This allows the curation UI to show all existing users in the unclassified list, even if they had events before curating mode was enabled. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	0e30f7a697	feat: add NIP-99/Gamma Markets kind categories for curating mode Add marketplace_nip99 category with Plebeian Market event kinds: - 30402 (Products) - 30403 (Orders - legacy) - 30405 (Collections) - 30406 (Shipping options) - 31555 (Product reviews) Add order_communication category for Gamma Markets (kinds 16, 17). Rename existing marketplace category to marketplace_nip15 for clarity while keeping backward compatibility with the legacy alias. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	047cdf3472	Add curation ACL mode and complete graph query implementation (v0.47.0) Curation Mode: - Three-tier publisher classification: Trusted, Blacklisted, Unclassified - Per-pubkey rate limiting (default 50/day) for unclassified users - IP flood protection (default 500/day) with automatic banning - Event kind allow-listing via categories, ranges, and custom kinds - Query filtering hides blacklisted pubkey events (admin/owner exempt) - Web UI for managing trusted/blacklisted pubkeys and configuration - NIP-86 API endpoints for all curation management operations Graph Query Extension: - Complete reference aggregation for Badger and Neo4j backends - E-tag graph backfill migration (v8) runs automatically on startup - Configuration options: ORLY_GRAPH_QUERIES_ENABLED, MAX_DEPTH, etc. - NIP-11 advertisement of graph query capabilities Files modified: - app/handle-nip86-curating.go: NIP-86 curation API handlers (new) - app/web/src/CurationView.svelte: Curation management UI (new) - app/web/src/kindCategories.js: Kind category definitions (new) - pkg/acl/curating.go: Curating ACL implementation (new) - pkg/database/curating-acl.go: Database layer for curation (new) - pkg/neo4j/graph-refs.go: Neo4j ref collection (new) - pkg/database/migrations.go: E-tag graph backfill migration - pkg/protocol/graph/executor.go: Reference aggregation support - app/handle-event.go: Curation config event processing - app/handle-req.go: Blacklist filtering for queries - docs/GRAPH_QUERIES_REMAINING_PLAN.md: Updated completion status 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago