prettydiff

share-file-systems

TypeScript2019–2026

prettydiff / share-file-systems

share-file-systems

Use a Windows/OSX like GUI in the browser to share files cross OS privately. No cloud, no server, no third party.

Explore on GitHub Read Hacker News discussions

4Distinct people

65Mentions

1Explicit recommenders

146GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Use a Windows/OSX like GUI in the browser to share files cross OS privately. No cloud, no server, no third party.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I started learning JavaScript in 2008. Back then the popular validation tool was JSLint whose motto is: JSLint will hurt your feelings. The idea is that under the sloppiness of…

austincheney used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

prettydiff/wisdom · linked in 5 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

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

Observed mentions: 2019-12-31 05:40:38 UTC to 2026-05-05 09:26:18 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	0	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	5	0	5
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	17	1	16
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	14	0	14
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	22	0	22
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	4	0	4
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	0	1
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	1	0	1

What Hacker News says

5 sources

austincheney·Dec 7, 2020

I noticed a link for distributed/peer-to-peer. https://github.com/arewedistributedyet/arewedistributedyet I am working on a Node/browser app that solves for this. The idea is to invert the web, which is inherently public, and you get an experience that’s inherently private. With privacy you can do things that aren’t possible or healthy on the public web. It works out of the box if both end points are IPv6 but IPv4 will require some additional service support to work outside of private networks, due to NAT. The application is currently just a file sharing tool but soon it will have a text message component. It’s about to achieve fully distributed test automation in the browser, which is a necessary maintenance tool to test the application using user events and DOM navigation across multiple computers for distributed end-to-end tests. If I

Read the rest

modify the architecture of the application to support loading and unloading of external components then the application becomes a micro operating system, but this requires many security considerations I have not explored. https://github.com/prettydiff/share-file-systems Please keep in mind this application is highly experimental.

In Areweyet

austincheney·Mar 3, 2020

Yes. Reinventing the wheel in this case is far less work than it sounds. You aren't really reinventing anything. Here is my current project where everything is vanilla. * Code: https://github.com/prettydiff/share-file-systems * Demo: http://mailmarkup.org/sharefile/demo1.mp4 The video demo is a few months old now, but in the current code I have broken network sharing during a refactor. The GUI and local file system still work well though.

In Ask HN: Has anyone ever got contacted from the “Who Wants to be Hired?” posts?

austincheney·Feb 19, 2020Recommendation phrase

I started learning JavaScript in 2008. Back then the popular validation tool was JSLint whose motto is: JSLint will hurt your feelings. The idea is that under the sloppiness of the language there was a polished gem of rapid expression. I didn't really figure out the language, though, until I started writing personal tools during my second military deployment in 2009. My recommendation for learning this language is to forget all the books and helpful guides. Just build something. Here is a good reference of the standard methods: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... Of that reference list the most immediately important areas are: Array and String. My personal recommendation for really embracing this language are to learn and master scope in the language. Don't mess around with class, prototypes, inheritance,

Read the rest

new, or this until after you have built at least one tool in the language. Most people coming into this language jump in expecting to program in the style of some former language only to be disappointed that JavaScript is not in fact their former language. My second personal recommendation is to gain confidence around the expressiveness of functions in this language. Functions are first-class objects, which means they can be used anywhere a primitive type can be used. https://developer.mozilla.org/en-US/docs/Glossary/First-clas... Perhaps the most important thing to learn for any language is data structures. If you have a solid understanding of data structures you can bend any algorithm to your will. You mention not learning any APIs, but there are two exceptions you should make in order to better understand the language. * DOM - If you are learning JavaScript in the browser I recommend learning the DOM. I mean the standard imperative DOM methods from the DOM specification. The DOM is a tree model of nodes where each node knows its place in the tree relative to its peers. By appreciating the nature of those fluid relationships you can do incredible things with little effort that execute incredibly fast. I built a complete GUI in the browser in just over 2 weeks that executes as fast as the OS's GUI because I had an understanding of the DOM. Here is the video demo: http://mailmarkup.org/sharefile/demo1.mp4 and code: https://github.com/prettydiff/share-file-systems * Nodes fs library - If you are learning JavaScript on the terminal with Node.js I recommend learning Node's fs library methods. The file system is also a tree model comprised of nodes that can be walked very quickly. After you have built one or more tools in this language you will independently learn to appreciate the conventions in this language that best suit your personal programming styles.

In Ask HN: How do I learn JavaScript?

austincheney·Feb 13, 2020

Just the code: https://github.com/prettydiff/share-file-systems

In The web as a GUI toolkit

austincheney·Jan 29, 2020

I ran this against a file sharing application I am working on and the results were strange. Security features were supremely emphasized, even security concepts I didn’t realize I was focusing energy on. I am not saying the tool is wrong, but just that it picked security better than I had intentionally considered. No other features were highlighted though, so you still have no idea what the application is doing. https://github.com/prettydiff/share-file-systems

In Microsoft Application Inspector