| WebM |
720p |
VP9 |
Technical Mechanisms and Data Handling in Facebook Video Extraction
Facebook’s native platform enforces strict restrictions on direct video downloads to preserve content ownership and user engagement. Platforms like facebookvideosave.net employ a combination of reverse-engineered protocols, third-party libraries, and intermediary tools to circumvent these limitations. The technical infrastructure behind such services often relies on dynamic request handling, proxy networks, and API interception to extract video streams without violating Facebook’s terms of service. Below is an analysis of the underlying mechanisms, associated risks, and common operational challenges.
Technical Infrastructure and Extraction Methods
The extraction process typically involves the following components:1. Reverse-Engineered API Endpoints
Facebook’s video delivery system uses undocumented or semi-documented endpoints (e.g., `/video_download`, `/playback` URLs) that return video streams in formats like MP4 or HLS. Services like facebookvideosave.net parse these endpoints by analyzing network traffic from legitimate Facebook interactions. This often requires dynamic URL reconstruction based on video IDs, user sessions, and regional server routing. 2. Proxy and CDN Bypass Techniques
Facebook routes video requests through its global Content Delivery Network (CDN) to optimize latency. Extraction tools may employ:
Rotating Proxies: To distribute requests across multiple IP addresses and avoid rate-limiting or IP-based blocking.
User-Agent Spoofing: Mimicking mobile or desktop browsers to bypass client-side restrictions.
Session Hijacking (Limited Scope): Reusing authenticated cookies or tokens to access private video streams (e.g., via `ds_user_id` or `c_user` parameters).3. Browser Extensions and Headless Browsers
Some extraction methods leverage browser automation tools (e.g., Puppeteer, Selenium) to simulate human-like interactions. These tools:
Inject JavaScript snippets to intercept `fetch` or `XMLHttpRequest` calls before Facebook’s client-side encryption applies.
Exploit WebSocket connections for real-time stream capture, though this is less common due to Facebook’s frequent protocol updates.4. Third-Party Libraries and Open-Source Tools
Libraries such as:
`facebook-video-downloader` (Node.js/Python): Uses Facebook’s Graph API and undocumented endpoints to fetch video metadata.
`youtube-dl` Forks: Modified versions to handle Facebook’s unique stream formats (e.g., `fbwatch` plugins).
FFmpeg Integration: For post-processing streams into downloadable formats (e.g., converting DASH segments to MP4).
Note: Many of these tools operate in a legal gray area, as they rely on undocumented APIs that Facebook may disable without notice.
Bypassing Facebook’s Native Download Restrictions
Facebook implements multiple layers of protection against unauthorized downloads:1. Client-Side Encryption and Tokenization
Videos are encrypted with unique tokens tied to user sessions. Extraction tools must:
Decrypt tokens using reverse-engineered algorithms (e.g., AES-128 with session-specific keys).
Reconstruct playback URLs by analyzing JavaScript payloads in Facebook’s frontend code.2. Dynamic URL Generation
Facebook’s video URLs are not static; they incorporate:
Video ID Hashing: SHA-1 or MD5 hashes of the video ID to prevent direct linking.
Timestamped Parameters: `t` or `expires` values that invalidate old requests.
Example URL structure:https://www.facebook.com/video/embed?video_id=&hashi= Extraction tools dynamically generate these parameters by parsing initial page loads. 3. Rate-Limiting and CAPTCHAs
Aggressive scraping triggers Facebook’s anti-bot systems. Mitigation strategies include:
Request Throttling: Delaying between requests to mimic human behavior.
CAPTCHA Solving Services: Automated services (e.g., 2Captcha) to bypass manual verification, though this introduces ethical and legal risks.4. Protocol-Level Restrictions
Facebook uses:
HTTP/2 and QUIC: To complicate packet inspection and replay attacks.
Differential Service: Serving lower-quality streams to non-premium users, requiring tools to upscale or re-route requests.
Potential Risks and Legal Considerations
While video extraction tools offer convenience, they expose users to significant risks. Below are the primary concerns, categorized by impact:
Malware and Security Exploits
Services hosting extraction tools may bundle adware, keyloggers, or ransomware. For example:
Fake "Facebook Video Downloader" apps on third-party app stores have distributed spyware.
Malicious proxies used by extraction sites may log keystrokes or redirect traffic to phishing pages.
Data Privacy Violations
Cookie Theft: Tools requiring session cookies may expose login credentials if stored insecurely.
IP Logging: Proxies or public download links may log user IP addresses, enabling tracking or legal action.
Metadata Exposure: Downloaded videos may retain EXIF data or Facebook’s watermarks, linking them to original uploaders.
Copyright Infringement and Legal Action
DMCA Takedowns: Facebook aggressively pursues sites distributing copyrighted content (e.g., music videos, movies).
User Liability: Downloading videos for redistribution (e.g., reposting on other platforms) may violate Facebook’s Terms of Service and copyright laws.
Platform Bans: Repeated use of extraction tools can result in Facebook account restrictions or permanent bans.
Service Disruption and Unreliability
API Changes: Facebook frequently updates its backend, breaking extraction tools (e.g., the 2021 shift to tokenized URLs).
False Positives: Tools may fail on private videos, live streams, or region-locked content.
Legal Shutdowns: Hosting providers may terminate services hosting extraction tools (e.g., GitHub banning repositories for `facebook-video-downloader`).
For educational purposes, the following is a simplified example of how a tool might interact with Facebook’s video endpoints. This does not constitute endorsement or promotion of unauthorized access.// Step 1: Fetch video metadata via Graph API (requires user token)
GET https://graph.facebook.com/{video-id}/videos
Headers:
Authorization: OAuth {USER_ACCESS_TOKEN}
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Firefox/91.0 // Step 2: Extract playback URL from response (simplified)
Response Body (JSON):
{
"data": [
{
"id": "123456789",
"source": "https://video.xx.fbcdn.net/hp/x/.../v/.../s9e3t7t0.mp4",
"embed_html": "..." // Contains JavaScript with dynamic URL
}
]
} // Step 3: Construct direct download URL (reverse-engineered)
Constructed URL:
https://video.xx.fbcdn.net/hp/x/.../v/.../s9e3t7t0.mp4?e=1735654321&v=...&t=...&s=... // Step 4: Stream or download with FFmpeg (example command)
ffmpeg -i "constructed_url" -c copy output.mp4
Important: This example is for illustrative purposes only. Unauthorized access to Facebook’s systems violates their Terms of Service and may result in legal consequences.
Common Errors and Troubleshooting Steps
Users of video extraction tools frequently encounter errors due to dynamic content restrictions or technical limitations. Below are the most frequent issues and systematic solutions:
-
Error: "Video not found" or "Invalid video ID"
- Cause: The video may be private, deleted, or geo-restricted. Facebook’s backend may also return 404s for non-existent or archived content.
- Solution:
- Verify the video URL is shareable (e.g., via Facebook’s native share dialog).
- Check for regional locks by testing on a VPN.
- Use the video’s ID from the page source (e.g., `data-video-id="12345"`).
- If the video is live or ephemeral, note that extraction is often impossible.
-
Error: "Server timeout" or "Connection refused"
- Cause: Facebook’s rate-limiting, CDN throttling,
User Experience and Interface Design
FacebookVideoSave.net prioritizes a streamlined, intuitive interface designed to minimize friction for users extracting videos from Facebook. The platform balances simplicity with functionality, ensuring accessibility across devices while addressing common pain points in video-saving workflows. Below is an analysis of its layout, usability features, and comparisons with native alternatives, alongside technical considerations for large-file handling and accessibility.
Interface Layout and Key Features
The landing page of FacebookVideoSave.net follows a minimalist design with three primary sections: input, processing, and output. The workflow begins with a centered input field labeled "Paste Facebook Video URL Here", accompanied by a placeholder example (e.g., "https://www.facebook.com/video/..."). Below this, a "Save Video" button (styled in a high-contrast color like blue or green) triggers the extraction process. Progress indicators, such as a loading spinner or animated bar, appear dynamically during processing, with estimated completion times displayed for files exceeding 100MB.Secondary features include:
- Format Selection Dropdown: Users can choose between MP4, WebM, or original Facebook format (if available) before downloading.
- Quality Toggle: Options for standard (720p), high (1080p), or original resolution, with a note clarifying potential file size trade-offs.
- Batch Processing Note: A tooltip explains that the platform currently supports single-video extraction, with plans for multi-video uploads in future updates.
The footer contains a "How It Works" section with step-by-step icons (e.g., URL → Paste → Download) and a "Need Help?" button linking to a FAQ or support chat. The design avoids clutter, ensuring the core functionality remains the focal point.
The user journey follows this sequence:1. Input Phase:
- User navigates to FacebookVideoSave.net and pastes a video URL into the designated field.
- Example placeholder text:
Paste Facebook Video URL Here
Example: https://www.facebook.com/facebook/videos/1234567890/ - A "Validate URL" button (optional) checks for compatibility before processing. 2. Processing Phase:
- Upon clicking "Save Video", the button transforms into a spinner with text: "Extracting Video...".
- A progress bar appears below, segmented into three stages:
- Buffering (10–30%): Server fetches metadata and initial video chunks.
- Decoding (30–70%): Converts Facebook’s proprietary format to MP4/WebM.
- Optimizing (70–90%): Applies compression or resolution adjustments.
- For files >200MB, an estimated time (e.g., "~2 minutes remaining") updates dynamically based on server load.
3. Output Phase:
- Upon completion, a download button labeled "Download [Filename].mp4" replaces the progress bar.
- A secondary "Share Link" button generates a direct download URL, useful for mobile users.
- A success toast notification appears briefly: "Your video is ready! (1.2GB)".
Comparison with Facebook’s Native Methods
Facebook’s built-in video-saving methods (screenshots, screen recording, or third-party apps) present trade-offs in usability, quality, and legality. Below is a comparative analysis:
| Feature | FacebookVideoSave.net | Facebook Native Methods |
| Quality Preservation | Retains original resolution (up to 4K if available). | Screen recording loses quality; screenshots are static. |
| Ease of Use | One-click process; no app installation required. | Requires manual recording or app setup (e.g., AZ Screen Recorder). |
| File Size Control | Offers resolution/format selection. | No control; output depends on device recording settings. |
| Legality | Operates within Facebook’s ToS (user-initiated extraction). | Screen recording may violate ToS; screenshots are permitted. |
| Device Compatibility | Works on desktop/mobile browsers. | Limited to mobile devices for recording; desktop requires third-party tools. |
| Batch Processing | Single-video only (planned updates). | Manual repetition required for multiple videos. |
Pros of FacebookVideoSave.net:
- Eliminates the need for cumbersome screen recording or app permissions.
- Preserves video integrity (no re-encoding artifacts from screen capture).
- Provides transparency with progress tracking and estimated times.
Cons:
- Relies on third-party servers (potential privacy concerns for sensitive content).
- May face temporary bans if Facebook detects automated scraping patterns.
- No direct integration with Facebook’s native player (requires URL input).
Accessibility Considerations
The platform incorporates several accessibility features but has room for improvement in specific areas. Key implementations include:- Keyboard Navigation:
- Tab order follows a logical sequence: URL field → Save button → Format dropdown → Download button.
- Enter key triggers the "Save Video" action when focused on the input field.
- Escape key cancels ongoing processes (e.g., aborts extraction if user changes mind).
- Screen Reader Compatibility:
- ARIA labels are used for interactive elements (e.g., `aria-label="Paste Facebook video URL"`).
- Progress bars include dynamic text updates (e.g., "Extracting: 45% complete").
- Error messages are announced clearly (e.g., "Invalid URL. Please check and retry.").
- Visual Accessibility:
- High-contrast color schemes for buttons and progress indicators.
- Responsive design ensures readability on mobile devices (minimum 16px font size).
- Dark mode toggle (optional future feature) to reduce eye strain.
Gaps and Recommendations:
- Alternative Text for Icons: Missing descriptive alt text for icons (e.g., download arrow, spinner).
- Focus Indicators: Custom focus styles could be added for keyboard users.
- Cognitive Load: Complex workflows (e.g., format/quality selection) may overwhelm users with disabilities; simplifying defaults would help.
- Language Support: Interface currently limited to English; adding multilingual support would broaden accessibility.
Facebook videos often exceed 1GB, requiring optimized server-side processing to avoid timeouts or failures. FacebookVideoSave.net employs the following mechanisms:- Chunked Downloads:
- Videos are split into 50MB–100MB segments during extraction, reducing memory strain on the server.
- Each chunk is processed sequentially, with a buffer system to handle network interruptions.
- Progress Tracking:
- Real-time updates are provided via WebSocket or AJAX polling, with a refresh rate of ~1 second for active users.
- Estimated completion times are calculated using:
- Initial Buffering Speed: Measures the time taken to fetch the first 10% of the video.
- Average Processing Rate: Adjusts for server load (e.g., slower during peak hours).
- File Size: Larger files trigger longer estimates (e.g., 1.5GB → "~5 minutes").
- Fallback Mechanisms:
- If a chunk fails to process, the system retries automatically (max 3 attempts) before notifying the user.
- For extremely large files (>3GB), users receive a warning: "This may take hours. Consider reducing resolution."
- Server-Side Optimizations:
- CDN Integration: Static assets (e.g., progress indicators) are cached to reduce latency.
- Load Balancing: Distributes extraction tasks across multiple servers during high traffic.
- Compression Algorithms: Applies adaptive bitrate streaming (e.g., H.264 for MP4) to balance quality and file size.
User Experience Impact:
- Buffering Delays: Initial loading may take 5–10 seconds for high-resolution videos, but progress tracking mitigates perceived wait times.
- Mobile Limitations: Slower networks (e.g., 3G) may cause timeouts; the platform suggests switching to Wi-Fi or reducing quality.
- Transparency: Clear communication about processing stages (e.g., "Decoding audio track") reduces user anxiety during long extractions.
Mockup Description: UI Workflow Visualization
Below is a textual representation of the key UI states during a video save:State 1: Idle (Ready to Input) +-------------------------------------+
| [FacebookVideoSave.net Logo] |
| |
| [_____________________________] |
| Paste Facebook Video URL Here |
| Example: https://fb.com/... |
| |
| [Save Video] |
| |
| [How It Works] [Need Help?] |
+-------------------------------------+ State 2: Processing (Active Extraction) +-------------------------------------+
| [FacebookVideoSave.net Logo] |
| |
| [https://fb.com/video/12345] |
| |
Legal and Ethical Considerations in Facebook Video Extraction
Facebook’s Terms of Service (ToS) and copyright frameworks create complex legal challenges for platforms like facebookvideosave.net, particularly concerning unauthorized video extraction. While users may save videos for personal use, commercial redistribution or large-scale scraping often violates Facebook’s Computer Fraud and Abuse Act (CFAA)-like restrictions and Digital Millennium Copyright Act (DMCA) provisions. Ethical dilemmas further arise when distinguishing between fair use (e.g., archiving public content for research) and unauthorized exploitation (e.g., reposting copyrighted material for profit). Regional laws—such as the EU’s GDPR (data protection) and U.S. DMCA (copyright enforcement)—add layers of compliance risk, with penalties ranging from fines to platform shutdowns. Case studies of similar tools (e.g., SaveFrom.net lawsuits) demonstrate how legal actions escalate when extraction methods conflict with platform policies or intellectual property rights.
Facebook’s Policy Framework on Video Sharing and Downloading
Facebook’s Terms of Service and Community Standards explicitly prohibit actions that circumvent its systems to extract or redistribute content without permission. Below is a structured comparison of permitted vs. restricted actions, based on Facebook’s official policies and legal precedents:
| Permitted Actions |
Restricted Actions |
Legal Basis |
- Saving videos for personal, non-commercial use (e.g., offline viewing).
- Sharing publicly available videos via Facebook’s native tools (e.g., "Save to Camera Roll" on mobile).
- Using Facebook’s APIs for approved developers under strict data usage policies.
- Downloading videos from open licenses (e.g., Creative Commons) with attribution.
|
- Automated scraping of videos via third-party tools (e.g., facebookvideosave.net) without API access.
- Redistributing videos for commercial purposes (e.g., monetized reposts, ads, or resale).
- Bypassing Facebook’s copyright protection measures (e.g., DRM, watermarking).
- Using extracted videos in compilations or remixes without permission from original creators.
- Accessing or downloading videos marked as private or restricted (e.g., friend-only content).
|
|
Key Clarification: Facebook’s policies distinguish between personal use (often tolerated) and systematic extraction (explicitly banned). Courts have ruled that tools enabling mass downloads—even for personal use—can violate unfair competition laws (e.g., Germany’s UWG §3a) if they harm Facebook’s revenue model.
Ethical Dilemmas: Fair Use vs. Unauthorized Distribution
The ethical justification for saving Facebook videos hinges on context, intent, and transformation of the content. Below are scenarios illustrating the spectrum from legally defensible to high-risk actions, aligned with fair use doctrine (U.S.) and EU’s "fair compensation" principle:
Fair Use Criteria (U.S. Copyright Act §107):- Purpose: Transformative use (e.g., criticism, research, education).
- Nature: Non-commercial, personal, or archival intent.
- Amount: Minimal copying (e.g., single video for analysis).
- Market Effect: No harm to original creator’s revenue.
Scenario Analysis:
- Justified (Low Risk):
Academic Research:
A professor downloads a Facebook livestream of a public debate to analyze rhetoric in an offline classroom, citing the original source. Justification: Educational purpose under fair use; no redistribution.
-
Accessibility:
A user with a disability saves videos to a screen reader-compatible format for personal consumption. Justification: Aligns with ADA (U.S.) and EU Accessibility Act (2019).
- Gray Area (Moderate Risk):
Personal Backups:
A user saves all videos from a closed group to prevent data loss if Facebook deletes the content. Risk: Violates Facebook’s ToS if done systematically; may trigger GDPR right to erasure conflicts.
-
Fan Compilations:
A creator stitches together short clips of a musician’s Facebook posts into a "highlight reel" without permission. Risk: Likely infringes copyright unless the musician consents or the use is de minimis.
- High Risk (Prohibited):
Commercial Repurposing:
A company uses facebookvideosave.net to extract viral videos, edits them into ads, and sells them on stock footage platforms. Violations: DMCA, CFAA, and Facebook’s ToS §10.1 (IP rights).
-
Mass Scraping for Training AI:
A startup scrapes millions of Facebook videos to train an AI model without creator consent. Violations: EU Copyright Directive (Article 3) and U.S. Copyright Act §106 (exclusive rights).
Ethical Conflict: Even if an action is legally permissible (e.g., fair use), it may still violate Facebook’s ToS, leading to account termination or legal action. Users must weigh personal necessity against platform policies and creator rights.
Regional Legal Variations and User Liability
Jurisdictional differences significantly impact the legality of facebookvideosave.net and user liability. Below is a comparison of key legal frameworks and their implications:
| Region |
Relevant Laws |
Key Provisions A
Facebook video extraction tools serve diverse needs, from casual users preserving personal memories to content creators archiving promotional material. While facebookvideosave.net offers a streamlined solution, alternatives exist with varying capabilities, including batch processing, multi-platform support, and advanced features like cloud integration. Evaluating these tools requires a comparative analysis of their technical specifications, user interfaces, and legal compliance to determine which aligns best with specific use cases.The selection of a video extraction tool depends on factors such as platform compatibility, output quality, ease of use, and legal risks. Below, a structured comparison of five direct competitors is provided, along with a detailed breakdown of their functionalities, advantages, and limitations.
Direct Competitors to facebookvideosave.net
The following tools specialize in video extraction from social media platforms, with distinct features catering to different user requirements:
-
4K Video Downloader
- Unique Features: Supports batch downloads, integrates with cloud storage (Google Drive, Dropbox), and includes a built-in video converter for multiple formats (MP4, MKV, AVI).
- Supported Platforms: Facebook, YouTube, Instagram, Twitter, and 1,000+ other sites.
- Platform Compatibility: Desktop (Windows, macOS, Linux) and mobile (Android via APK).
- Output Quality: Preserves original resolution up to 4K, with options for subtitles and metadata retention.
-
YTD Video Downloader
- Unique Features: Focuses on YouTube and Facebook but includes a browser extension for quick access. Offers scheduled downloads and playlist extraction.
- Supported Platforms: YouTube, Facebook, Vimeo, and Dailymotion.
- Platform Compatibility: Desktop (Windows/macOS) and Chrome/Firefox extensions.
- Output Quality: Supports 1080p and 4K downloads with adjustable bitrate settings.
-
SaveFrom.net
- Unique Features: Aggregates video sources from multiple platforms, including Facebook Live, with no software installation required. Supports MP3 extraction for audio-only downloads.
- Supported Platforms: Facebook, YouTube, Instagram, TikTok, and Twitch.
- Platform Compatibility: Web-based (no desktop/mobile app).
- Output Quality: Limited to platform-provided resolutions; no direct 4K support for all sites.
-
JDownloader 2
- Unique Features: Open-source with advanced automation (e.g., automatic renaming, folder organization). Supports proxy servers for bypassing restrictions.
- Supported Platforms: Facebook, YouTube, Reddit, and torrent sites.
- Platform Compatibility: Desktop (Windows, macOS, Linux).
- Output Quality: High customization for resolution, format, and quality settings.
-
SnapDownloader
- Unique Features: Specializes in Snapchat and Instagram Stories but includes Facebook support. Offers "Smart Download" for multiple clips in one go.
- Supported Platforms: Facebook, Instagram, Snapchat, and Twitter.
- Platform Compatibility: Desktop (Windows/macOS) and mobile (iOS/Android via third-party apps).
- Output Quality: Preserves original quality but lacks 4K support for most platforms.
Comparative Analysis Table
The following table summarizes key criteria for evaluating facebookvideosave.net and its competitors, including platform support, output quality, and accessibility:
| Tool |
Supported Platforms |
Output Quality (Max) |
Batch Processing |
Cloud Integration |
Platform Compatibility |
Browser Extension |
- Legal Compliance Notes
| facebookvideosave.net |
Facebook, Instagram |
1080p (platform-dependent) |
No |
No |
Web-based (mobile/desktop) |
No |
Terms of Service compliance; no explicit DMCA violations reported. |
| 4K Video Downloader |
Facebook, YouTube, Instagram, Twitter, +1,000 sites |
4K |
Yes |
Google Drive, Dropbox |
Desktop (Windows/macOS/Linux), Mobile (Android) |
Yes (Chrome/Firefox) |
Adheres to platform APIs where possible; user must respect copyright. |
| YTD Video Downloader |
YouTube, Facebook, Vimeo, Dailymotion |
4K (YouTube), 1080p (Facebook) |
Yes (playlists) |
No |
Desktop (Windows/macOS), Browser Extension |
Yes (Chrome/Firefox) |
Primarily uses YouTube’s official API; Facebook support may violate ToS. |
| SaveFrom.net |
Facebook, YouTube, Instagram, TikTok, Twitch |
Platform-native (no 4K for all) |
No |
No |
Web-based only |
No |
Relies on third-party embeds; legal status varies by region. |
| JDownloader 2 |
Facebook, YouTube, Reddit, Torrent sites |
Customizable (up to 4K) |
Yes (automated) |
No |
Desktop (Windows/macOS/Linux) |
No |
Open-source; users must handle legal risks independently. |
| SnapDownloader |
Facebook, Instagram, Snapchat, Twitter |
Original quality (no 4K) |
Partial (multi-clip) |
No |
Desktop (Windows/macOS), Mobile (third-party) |
No |
Snapchat/Instagram support may violate platform policies. |
Note: Output quality and legal compliance depend on the platform’s API restrictions and regional copyright laws. Users should verify terms of service for each tool before use.
Step-by-Step Guide: Using 4K Video Downloader for Facebook Videos
4K Video Downloader provides a comprehensive solution for extracting Facebook videos with advanced features. Below are the steps to download a video using its desktop application:
-
Installation and Setup
Download the latest version of 4K Video Downloader from the official website and install it on your desktop. Launch the application and ensure your system meets the minimum requirements (Windows 7+/macOS 10.12+).
-
Accessing the Facebook Video
Open Facebook in your browser and navigate to the video you wish to downloadfacebookvideosave net represents a double-edged tool in the digital content ecosystem, offering unparalleled convenience for users seeking to preserve Facebook videos while operating within a complex web of technical, legal, and ethical constraints. Its ability to bypass native restrictions through sophisticated extraction methods highlights both innovation and the persistent tension between accessibility and platform governance. As users weigh the platform’s advantages—such as format versatility and speed—against inherent risks, a balanced approach is essential. Whether for personal archival, professional use, or educational purposes, understanding the nuances of facebookvideosave net empowers individuals to navigate its capabilities responsibly. The broader implications for video-sharing platforms and third-party tools remain a critical conversation, shaping the future of digital content consumption and preservation.
|
|---|
|
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of www.linuxunplugged.com.