Show HN: BrowserFace – Embeddable Chrome Front end. Connect to browser remotely https://ift.tt/3jQm0Lf

Show HN: BrowserFace – Embeddable Chrome Front end. Connect to browser remotely https://ift.tt/3bsstIZ September 4, 2020 at 06:21AM

Show HN: Techwriting.styles.wiki – Tips for improving project docs, RFCs etc. https://ift.tt/3bC2Tlf

Show HN: Techwriting.styles.wiki – Tips for improving project docs, RFCs etc. https://ift.tt/2QSbUgj September 4, 2020 at 01:41AM

Show HN: Single neuron neural network written in COBOL https://ift.tt/2Dw24xE

Show HN: Single neuron neural network written in COBOL https://ift.tt/2Ake43d September 4, 2020 at 03:12AM

Show HN: My GitHub Readme Is Interactive https://ift.tt/3lMEbDa

Show HN: My GitHub Readme Is Interactive https://ift.tt/3lHNbcG September 4, 2020 at 02:05AM

Show HN: Using cec-utils,HomeAssistant, & a Pi to make a soundbar a soundmachine https://ift.tt/2QOyHJQ

Show HN: Using cec-utils,HomeAssistant, & a Pi to make a soundbar a soundmachine https://ift.tt/3gW6Y4K September 3, 2020 at 09:09PM

Show HN: Skia-canvas, a browserless implementation of the Canvas API for Node.js https://ift.tt/3lOA0GP

Show HN: Skia-canvas, a browserless implementation of the Canvas API for Node.js https://ift.tt/3jJlD4V September 3, 2020 at 04:58PM

Show HN: LibreSelery – Solution for the Open Source Donation Pool Problem https://ift.tt/3lGLj3U

Show HN: LibreSelery – Solution for the Open Source Donation Pool Problem https://ift.tt/3bmCZSf September 3, 2020 at 07:53PM

Show HN: A proactive way of securing your Linux server https://ift.tt/3jHoISV

Show HN: A proactive way of securing your Linux server https://ift.tt/3lNG2HW September 3, 2020 at 06:38PM

Show HN: Real Time Stream Processing Startup https://ift.tt/35872Mx

Show HN: Real Time Stream Processing Startup We are working on a product which makes stream processing easy for data analysts and data scientists. It’s a higher level alternative to Flink, Kafka Streams and Spark Streams. As well as making stream processing simpler, we also felt that lots of people were building these AWS stream processing platforms based on Kafka and something like Flink so wanted to offer this as a service. We would welcome any input on the space or approach: Home page: http://Timeflow.systems Demo: https://youtu.be/fGfgBaHXOkE September 3, 2020 at 06:27PM

Show HN: A Chrome extension to help save books you want to read https://ift.tt/2QPF7Iy

Show HN: A Chrome extension to help save books you want to read https://ift.tt/3gXm7CO September 3, 2020 at 06:02PM

Launch HN: Slapdash (YC W19) – A uniform, low-latency interface for cloud apps https://ift.tt/3boeKmu

Launch HN: Slapdash (YC W19) – A uniform, low-latency interface for cloud apps Hello HN, I'm Ivan, one of the founders of Slapdash ( https://slapdash.com/ ). Slapdash lets you work across all of your cloud apps at desktop speed, sort of like an OS for cloud apps. We have built a uniform, low-latency data browser (kind of like Finder) as well as a unified command line-like interface (kind of like Spotlight) for the applications you use at work. When we left our big company jobs, one of the difficult things to part with was the tooling. Companies like Facebook & Stripe build a class of tools internally that unifies all the employees and any collaboration apps, so you can find anyone or anything the company knows. Everything is just a quick search away.[0] It’s quite a useful way to work. Common questions in day-to-day work are easy to answer. What’s the history of this code abstraction? What are my colleagues working on? What’s the story with this customer? Building such a system today means connecting people's cloud apps, because that's where most of the work is happening today. Even for a small team like us, our work spans Drive, Dropbox, Figma, GitHub, Asana, Notion, Docusign, Slack, Quip, etc. The first thing we built was a low-latency file system for cloud apps. You connect an application like Drive, or GitHub to Slapdash and we give you a way to search & browse the data in a uniform interface (kind of like Finder). It turns your working world into a database you can easily query. We modeled our file system as a graph and we built our architecture to match, with a focus on performance. We built an import system, which effectively solves a graph replication problem (translating the structure of the app data to the Slapdash graph and keeping it in sync). We then built a graph database on top of Postgres, added a data access layer with graph semantics, with GraphQL API delivering the data to the client. Of course, the data we store is encrypted on disk, in-transit and in the data store. Slapdash employees can't see the contents of what we index since everything except the reverse index is encrypted. It’s not zero-access yet, but we’re building in that direction.[1] What we discovered is that by applying optimizations to how we store (sharding & colocation) & retrieve data (batching & coalescing) we could achieve an almost zero-latency[2] experience when browsing application data. As a result, it's much faster to browse Google Drive in Slapdash than in the Drive interface itself. While the low-latency file system is interesting, we learned that being able to search and navigate is not enough utility for a single individual. People don’t search as much as they think they do, and most have their unique information foraging habits that work well-enough. However, we wanted Slapdash to be useful for anyone, not just an employee at a big company, so we turned our attention to building a new experience on top of the file system. Our goal was to take a leap in speed with which people can control their computers. We thought this was possible because the difference in UX between desktop & cloud app environments was so acute: the desktop OS is principled, integrated and fast, while cloud apps are latency-laden and confined to crowded browser tabs. To that end, we built the Command Bar (Command Line + Search Bar). The Command Bar is best experienced as a desktop app, where it’s invoked with a global shortcut. You can quickly search your apps, file tasks, peek at your calendar, create zoom meetings, etc: all with a couple of keystrokes. Of course, you can also write your own commands too. In practice, it meaningfully cuts down the time you spend controlling the computer. For example, filing a task on GitHub might take 10 seconds of just navigating to the right screen, while you can start writing the task title within 2 seconds by invoking the "Create New GitHub Issue" command with the Command Bar. Things like searching for a customer record, doing a quick spreadsheet calculation and even routine things like opening an existing document are measurably faster. [3] For teams & companies, Slapdash provides a unified interface to a team’s collective knowledge. This has traditionally been reserved for top technology companies, but we are bringing these advantages to everybody else. And for the individual, we are making the use of disparate cloud apps feel closer to the classic experience of a desktop computer OS - fast, integrated and more productive. We are still figuring out what apps to support, what commands we should build and how we can open up the platform for others to build on as well. We would love to hear from you on any of those counts and any feedback you might have! [0] Facebook has something called "intern" and Stripe has an internal product called "Stripe Home". [1] Content is stored using ECIES (with Secp256k1 curve and AES256 cipher in CTR mode), public-key-encrypted with individual per-user, per-app key pairs. [2] It's actually not zero latency, of course, but by preloading most things on the hover state we can cut ~50ms of perceived latency (as long as the server response time is under that, which we try to do, it feels instant). [3] We use the keystroke-level GOMS model to evaluate interface speed, but the speed difference here is large enough that it can be intuited. Example of filing a task on GitHub: Time controlling computer: open browser, command + L ( focus location bar), type partial URL of repo until it auto-completes, wait for page to load, click on Issues, wait for page to load, click on “New Issue”. Expressing actual intent: typing title of task. Filing a task with Slapdash: Time controlling computer: Type Command + J, type “Cre gi” to fuzzy match “Create New GitHub Issue” command, hit enter. Expressing actual intent: typing title of task. September 3, 2020 at 05:13PM

Show HN: 50 days study C compiler https://ift.tt/2Z2sfTX

Show HN: 50 days study C compiler https://ift.tt/3lMzAkA September 3, 2020 at 03:44PM

Show HN: ORM for TypeScript with no query-builder, supporting full SQL queries https://ift.tt/3jGRvHl

Show HN: ORM for TypeScript with no query-builder, supporting full SQL queries https://ift.tt/3hVW405 September 3, 2020 at 02:50PM

Show HN: FixCache – keep track of bug-prone files from Git commit history https://ift.tt/2GnAC69

Show HN: FixCache – keep track of bug-prone files from Git commit history https://ift.tt/3gWzByG September 3, 2020 at 02:29PM

Show HN: Automated Health Dashboard https://ift.tt/3hYHrZK

Show HN: Automated Health Dashboard https://ift.tt/3hAHRW9 September 3, 2020 at 02:26PM

Show HN: Bidinfinity – Free eBay research and auction analytics platform https://ift.tt/2QOxbav

Show HN: Bidinfinity – Free eBay research and auction analytics platform https://ift.tt/2GjSoXW September 3, 2020 at 02:06PM

Show HN: Modern Data Engineer Roadmap 2020 https://ift.tt/2YYxAM8

Show HN: Modern Data Engineer Roadmap 2020 https://ift.tt/357VAAa September 3, 2020 at 01:36PM

Show HN: AS path tracing and IPv4/6 info lookup CLI tool (Linux/FreeBSD/Windows) https://ift.tt/3jU9lHd

Show HN: AS path tracing and IPv4/6 info lookup CLI tool (Linux/FreeBSD/Windows) https://ift.tt/33GqGyf September 3, 2020 at 11:21AM

Show HN: Using LXD system containers to deploy and manage complex environments https://ift.tt/2QPNuUH

Show HN: Using LXD system containers to deploy and manage complex environments https://ift.tt/351xnLS September 3, 2020 at 10:48AM