stevelacy

Congrats on launching! Was following along with the development, glad to see it launched

Mikeal used to organize bicycle + coffee meetups in SF many years ago, and was very welcoming to anyone getting into Nodejs.

Very nice looking app, installed. Would be interesting if this integrated with Raycast.

I would suggest hiding the main window from the dock/switcher as when the window is closed it still presents the app title. Potentially NSApplication.setActivationPolicy(.accessory)

We have been using better-auth (open source) for a while, it was immediately a better experience compared to the existing (typescript) auth libraries. Plus no Nextjs lock-in, we migrated off Nextjs to Hono and only had to change the router.

If your project database is suspending for lack of requests I doubt a 500ms wake up delay is an issue.

Have been following along with the development, glad to see it announced!

This is amazing, love the ESP32 watchdog controller. Had a question about the keyboard - would it make sense for the keyboard to be hardwired to the laptop via USB-C and detachable to have one battery source?

> uncovering potential bugs that could compromise even these hardened environments

This seems to be a sensationalized statement. Apart from "trusting a black box" they didn't actually indicate an actual weakness, stating side-channel attacks as the obvious attack vector.

We use 1password with op (1password cli) to sync secrets on dev

Following your build statuses for a while, congrats on the launch!

Game dev here, totally agree.

File-locking across branches excited me, support for visual diffing of uassets would be insane. The platform screenshots as a git/github alternative didn't excite much interest as Plastic and Perforce are major players.

I found it harder than expected to locate a link to the git repos. A project that advertises as open source should have the git repos prominently displayed.

Is it possible to consume the malware list as JSON/SSE?

This was also a personal device, not one provided by the company. Either the company should have provided a device, or the employee should _not_ be using a personal device.

They are using AWS Nitro instances for their enclaves. These can absolutely be run on-prem with self-hosted licensed software to perform the computational redacting.

I've built several massive-scale k8s systems for prior companies, all scaled using the underlying built-in primitives without extreme cost. Where do you get the improvement metrics from? For instance: "5x faster deployments"

RGB room lights controlled via Arduino with a companion mobile app for changing colors/modes. Used zeroconf for finding the device on the network.

Farther comments in that thread indicate they are referring to PHF (password hashing function) not KDF (key derivation function). LUKS uses a KDF.

Is this designed for new home builds or remodel/retrofits? There would be a major cost difference between demo/prepping a retrofit over a new build.

Game development, especially Unreal engine, can produce repos in excess of 1TB. Git LFS is used extensively for binary file support.

Good to know, I was not aware. The squash/rebase issue is definitely problematic, though a tree of signatures could be appended to each commit. Now... this does break how commits are currently signed.

It would only allow commits signed by me to be pushed under my email. Github uses the email as the "proof" of commit ownership. By only accepting signed commits a user would not be able to push a commit impersonating me.

Correct. My suggestion for a solution is for github to add a "reject-unsigned" feature. Only allow commits signed by <my gpg key> and <my email> to be pushed to github, under any projects/org.

Many of the repos I found were clones of valid projects with same names under new orgs and new users. For instance, this projects is valid: https://github.com/scala-network/GUI-miner and it's infected clone: https://github.com/stellitecoin/gui-miner

GPG signed commits by the legitimate users do not contain the malware

Amazingly quick loads, slick project. I'd suggest adding a required class or warning to the inputs, I was hitting the publish button a few times wondering why it didn't publish until I filled out the title as I thought the "name" field was the title field.

Is the start date supposed to be in the future?

"The scraper came alive Tuesday, March 7, 2017 at 12:33 AM."

Or am I in the past...

I'll do that, thanks

I have not yet played with CAN messages, please do let me know how your testing goes. From what I understand yes, the messages would go through the BUS to the car's CPU.