本文へ移動
cccskills
無料GitHub で公開

divine-relay-video-requirements

Fix "blocked: event rejected by relay policy" errors when publishing Kind 34236 (video) events to divine relays. Use when: (1) Kind 0 profile events succeed but Kind 34236 fails, (2) Generic policy rejection with no specific reason, (3) Video events work on other relays but fail on divine relays. The divine relay requires thumbnails for all video events - stricter than NIP-71 spec.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Divine Relay Video Requirements

Problem

Publishing Kind 34236 (short-form video) events to divine relays fails with "blocked: event rejected by relay policy" even though the events comply with NIP-71 spec.

Context / Trigger Conditions

  • Error message: blocked: event rejected by relay policy
  • Kind 0 (profile) events publish successfully to the same relay
  • Kind 34236 events fail on divine relays (wss://relay.poc.dvines.org, wss://relay.dvines.org)
  • Events that work on other relays fail on divine relays

Root Cause

The divine relay (funnelcake) has additional validation beyond NIP-71:

From divine-funnelcake/crates/relay/src/relay.rs:554-564:

// divine.video requires thumbnail for all videos (stricter than NIP-71)
// Accept: thumb tag, thumbnail tag, image tag, or imeta with image field
let has_thumb = event.get_tag("thumb").is_some()
    || event.get_tag("thumbnail").is_some()
    || event.get_tag("image").is_some()
    || has_imeta_with_image(&event);

if !has_thumb {
    // Event rejected
}

Solution

Ensure video events include a thumbnail in one of these formats:

  1. Inside imeta tag (preferred - NIP-92 compliant):

    ["imeta", "url https://...", "m video/mp4", "image https://thumbnail.jpg", ...]
    
  2. Standalone tag:

    ["thumb", "https://thumbnail.jpg"]
    ["thumbnail", "https://thumbnail.jpg"]
    ["image", "https://thumbnail.jpg"]
    

Getting Thumbnails from Blossom

Blossom (media.divine.video) auto-generates thumbnails for uploaded videos:

  • Thumbnail URL: https://media.divine.video/{video_sha256}.jpg
  • Generation is async - may take a few seconds after upload
  • Check with HEAD request before assuming availability

Verification

  1. Ensure imeta tag contains image https://... field
  2. Test publication: nak event -k 34236 ... wss://relay.poc.dvines.org
  3. Verify with: nak req -k 34236 -a {pubkey} --limit 1 wss://relay.poc.dvines.org

Example

// Build imeta with thumbnail
const imetaParts = [
  `url ${videoUpload.url}`,
  "m video/mp4",
  `image ${videoUpload.url}.jpg`,  // Blossom thumbnail URL
  "dim 480x480",
  `x ${videoUpload.sha256}`,
  "duration 6"
];
tags.push(["imeta", ...imetaParts]);

Notes

  • This is divine-specific - other relays may accept videos without thumbnails
  • The generic error message doesn't indicate which validation failed
  • To debug relay rejections: read the relay source code for policy details
  • Other divine relay validations in the same file:
    • Required d tag for addressable events
    • Required title tag
    • Required video source (imeta or url tag)

Debugging Strategy

When getting generic "relay policy" rejections:

  1. Test different event kinds (Kind 0 vs target kind) to isolate the issue
  2. Check if the relay codebase is available (divine repos are at ~/code/divine/)
  3. Search for "reject" or "blocked" in the relay handler code
  4. Look for validation beyond standard NIP requirements

Related Files

  • Relay validation: divine-funnelcake/crates/relay/src/relay.rs
  • Allowed kinds seed: divine-funnelcake/database/migrations/000015_seed_allowed_kinds.up.sql
  • Relay config: divine-funnelcake/crates/relay/src/config.rs

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月13日 更新

divinevideo のスキルをすべて見る

このスキルの問題を報告する