HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
1fpsvideo
1fps
Go2024–2024
1fpsvideo / 1fps

1fps

1fps.video client app

2Distinct people
2Mentions
0Explicit recommenders
186GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

1fps.video client app

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 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 hour2 dated mentions

Observed mentions: 2024-08-06 18:23:36 UTC to 2024-08-07 02:13:17 UTC.

012024-08-06 18:00:00 UTC to 2024-08-06 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 6, 18:002024-08-06 19:00:00 UTC to 2024-08-06 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-06 20:00:00 UTC to 2024-08-06 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-06 21:00:00 UTC to 2024-08-06 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-06 22:00:00 UTC to 2024-08-06 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 6, 22:002024-08-06 23:00:00 UTC to 2024-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-07 00:00:00 UTC to 2024-08-07 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-07 01:00:00 UTC to 2024-08-07 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-07 02:00:00 UTC to 2024-08-07 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 7, 02:00

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
Aug 6, 18:002024-08-06 18:00:00 UTC2024-08-06 19:00:00 UTC101
Aug 6, 19:002024-08-06 19:00:00 UTC2024-08-06 20:00:00 UTC000
Aug 6, 20:002024-08-06 20:00:00 UTC2024-08-06 21:00:00 UTC000
Aug 6, 21:002024-08-06 21:00:00 UTC2024-08-06 22:00:00 UTC000
Aug 6, 22:002024-08-06 22:00:00 UTC2024-08-06 23:00:00 UTC000
Aug 6, 23:002024-08-06 23:00:00 UTC2024-08-07 00:00:00 UTC000
Aug 7, 00:002024-08-07 00:00:00 UTC2024-08-07 01:00:00 UTC000
Aug 7, 01:002024-08-07 01:00:00 UTC2024-08-07 02:00:00 UTC000
Aug 7, 02:002024-08-07 02:00:00 UTC2024-08-07 03:00:00 UTC101

What Hacker News says

2 sources
See updated docs for Windows users: https://github.com/1fpsvideo/1fps?tab=readme-ov-file#windows... Please understand the Windows toolchain is often broken, and binaries are preferable. I will roll out binaries soon for all platforms. I also noticed some cursor coordinates issues on Windows machine (I have high resolution). I'm wondering if you have any issues with that as well. Good news is that there are steps to workaround and we're aware of these issues :) I guess check back later, I hope we gonna fix it soon!
In Show HN: 1-FPS encrypted screen sharing for introverts
Good job releasing your project! It's a cool idea and surprisingly minimalist. That said, I've found a number of cryptographic flaws in the application source. This should not be used in instances where the encryption is mission-critical. 1) You generate a random key [0] and then feed it into PBKDF2 [1] to generate a 32-byte AES-GCM key. If you can generate 32 random bytes instead of 10 reduced-ASCII characters and a key stretch, just do that. PBKDF2 is for turning a password into a key, and it's far from the recommended algorithm nowadays; prefer scrypt if you need to do this sort of thing. 2) AES-GCM with random 12-byte nonces. Never use random IVs with GCM; this breaks the authentication [2] [3]. Given the pitfalls of AES-GCM with respect to random nonces, you might prefer switching to XSalsa20+Poly1305. The advantage of XSalsa is it h
Read the rest
as an extended nonce length, so you can use random nonces without fear. 3) Random key derivation with a restricted character set can make brute force attacks easier. You should have a 256-bit random key, and if you want that key to be within a certain character set, then encode the byte output from the CSPRNG using that character set. 4) 1fps achieves symmetric key distribution via a URL with a fragment identifier ("#") which IIRC is not sent to the server. Therefore it assumes you have a secure key distribution channel - the link contains the key, so it's important that only the intended recipient can view the part after the "#". If the server is truly malicious, it can deploy client-side Javascript to send the fragment to the server, allowing the server to access the key (and thus cleartext communication). [0]: https://github.com/1fpsvideo/1fps/blob/main/1fps.go#L99 [1]: https://github.com/1fpsvideo/1fps/blob/main/1fps.go#L287 [2]: https://eprint.iacr.org/2016/475.pdf [3]: https://soatok.blog/2020/05/13/why-aes-gcm-sucks/
In Show HN: 1-FPS encrypted screen sharing for introverts

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.