Updated `content/docs/guides/upload-content.md` and `content/docs/getting-started.md` to accurately reflect the application's runtime behavior, specifically regarding upload workflows, CORS configuration, and routing links. - Clarified CORS instructions to distinguish between R2 (manual) and S3 (auto) configuration. - Updated example origins to be more generic (localhost). - Explicitly mentioned the "Hashtags" section in the upload form. - Clarified navigation to the Storage tab. - Fixed the broken link to the Watch History view (using hash routing). - Removed unsupported "captions" from the metadata list. - Validated changes using `tests/docs/verify-upload-claims.test.mjs`. Co-authored-by: PR0M3TH3AN <[email protected]>
4.6 KiB
How to Upload Content
bitvid is a decentralized platform, but for larger video files, we support Cloudflare R2 and S3-compatible storage backends. This allows you to upload files directly from your browser to a high-performance storage bucket.
Prerequisites
- A Cloudflare Account (free to create) or an S3-compatible provider.
- An activated R2 Plan (if using Cloudflare).
Supported Media & Limits
Before you start, ensure your content meets the following requirements:
Accepted File Types
- Video:
.mp4,.webm,.mov,.mkv,.ts,.m3u8,.mpg,.mpeg - Thumbnail: Any standard image format (
image/*)
File Size
- Recommended: Up to 2GB per file.
- Why? Browser-based uploads rely on your device's memory for hashing and chunk management. Files larger than 2GB may cause browser instability or crashes.
Metadata
- Title: Required.
- Description: Optional.
- Thumbnail: Optional.
- Tags (Hashtags): Optional but highly recommended for discoverability. Use the dedicated "Hashtags" section in the upload form.
Step-by-Step Guide
1. Create a Bucket & Enable Public Access
- Log in to your provider's dashboard (e.g., Cloudflare).
- Create a new bucket (e.g.,
my-bitvid-videos). - Enable Public Access:
- Cloudflare R2: Go to Settings > Public Access and enable "R2.dev subdomain" or connect a custom domain.
- S3 Compatible: Ensure the bucket policy allows public read access for objects.
- Copy the Public Bucket URL (e.g.,
https://pub-xxxxxx.r2.dev). You will need this later.
2. Configure CORS
To allow your browser to upload files directly to the storage bucket, you must allow Cross-Origin Resource Sharing (CORS).
Cloudflare R2 (Manual Configuration Required):
- In your bucket's Settings tab, scroll down to "CORS Policy".
- Click "Add CORS Policy" (or Edit).
- Paste the following JSON configuration. You must allow headers used by the AWS SDK (
amz-sdk-*).
[
{
"AllowedOrigins": ["http://localhost:5500", "https://bitvid.network"],
"AllowedMethods": ["GET", "PUT", "POST", "DELETE", "HEAD", "OPTIONS"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag", "Content-Length", "Content-Range", "Accept-Ranges"],
"MaxAgeSeconds": 3600
}
]
Note: Replace
AllowedOriginswith your actual origins (e.g.http://localhost:5500for local development, orhttps://your-custom-domain.com).
S3 Compatible Providers: bitvid will attempt to configure CORS automatically for generic S3 providers if your credentials have sufficient permissions. However, if uploads fail with CORS errors, apply a similar policy manually in your provider's console.
3. Create API Credentials
- Create an API Token or Access Key pair.
- Permissions: Ensure "Object Read & Write" access (or
s3:PutObject,s3:DeleteObject). - Copy the credentials: You will need the Access Key ID and Secret Access Key.
4. Configure bitvid
- In bitvid, open your Profile (click your avatar).
- Navigate to the Storage tab in the sidebar menu (or click "Configure Storage" in the Upload Modal).
- Click "Add Connection" (or use the default form).
- Select Cloudflare R2 or S3 Compatible.
- Enter your credentials:
- Account ID (R2 only)
- Access Key ID
- Secret Access Key
- Bucket Name
- Public Access URL (The URL from Step 1)
- Endpoint (S3 Compatible only)
- Click "Save Connection".
bitvid will verify your credentials by attempting to list or upload a test file. Once verified, return to the Upload Modal to start sharing!
Upload Lifecycle & Moderation
How Uploads Work
- Direct Upload: Your browser uploads the file directly to your storage bucket. No video data passes through a bitvid server.
- Client-Side Hashing: Your browser calculates a cryptographic hash (info hash) of the file to enable WebTorrent support.
- Publication: The video metadata (title, URL, hash, tags) is signed by your Nostr key and published to relays.
Moderation & Visibility
While publication is decentralized and permissionless, the bitvid.network instance may enforce moderation policies:
- Whitelists: If the instance is in "whitelist mode", you may need approval before your videos appear in public feeds.
- Blacklists: Violating community guidelines may result in your account being hidden from this instance.
- User Blocks: Viewers can mute or block your content individually.
Check the Community Guidelines for more details.