HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
castlabs
electron-releases
Python2019–2024
castlabs / electron-releases

electron-releases

Castlabs Electron for Content Security

6Distinct people
9Mentions
0Explicit recommenders
298GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Castlabs Electron for Content Security

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2019-03-11 13:11:53 UTC to 2024-01-03 17:19:46 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

4 sources
This certainly isn't short, but I don't know how to make it shorter, as I don't know what you don't know, and what you want to know. You need a DRM "capable" video component to be allowed to play most internet video content that isn't directly user generated, or news. The consequence is that the giants holding the rights to these components are effectively holding the keys to a decent chunk of the internet. For a browser specifically made for synced playback of movies, they essentially hold the keys to all of it. The big movie studios simply won't allow either streaming or download without you using one of these solutions on both ends of the stream. The author applied for some form of license of the purportedly free and open Widevine DRM component which is used/approved by almost all big streaming sites. The request was rejected citing a
Read the rest
somewhat odd reason: That the project was open source. This is odd because https://github.com/castlabs/electron-releases is open source, apparently "blessed" by Google/Widevine, and available to use on the only condition you get a license from Widevine. Which should then be impossible? Which leads us to several somewhat plausible conclusions. Either the author requested the wrong licence/needs a feature not available in previously mentioned projects, someone at Widevine made a mistake, or there is a lot of smoke and mirrors going on to either make it seem Widevine is accessible to anyone when it truly isn't.
In I tried creating a web browser, and Google blocked me
smaddock·Mar 11, 2019Submission

Ask HN: Has anyone completed a license agreement with Google Widevine?

I'm building my own Chromium-based browser with Electron [1] and I'd like to be able to support DRM-enabled content like Netflix. In order to do so, the browser must support Verified Media Path (VMP) to verify the authenticity of the device platform. And to support VMP, a license agreement (LA) with Widevine must be completed. [2] Contacting Widevine has been... difficult, with no response after 3 months. I know there have been a few others with similar experiences. [3] Has anyone been able to complete a LA with Widevine? What was your experience like? [1] https://github.com/samuelmaddock/metastream [2] https://github.com/castlabs/electron-releases#licensing [3] https://github.com/electron/electron/issues/12427
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.