chromakode

I had my first serious medical procedure a year and a half ago, which required a rare specialist. My insurance, Anthem Blue Cross, covered everything, and called and mailed me ahead of time confirming my hospital stay at UCSF was approved and in network. So, YMMV.

Ubuntu has a bunch of non-GUI server flavors. It's a common base image for cloud VMs, similar to Debian.

https://ubuntu.com/download/server

It's very funny and odd that they retained the "God's in his heaven, all's right with the world" text.

It's legal to charge for distributions of GPL licensed projects. The OSI definition [1] specifically notes it's one of the freedoms in licenses considered open source.

Back in the mid 2000s I recall seeing drama about projects like The GIMP being repackaged and sold. While legal, the sellers exploited information asymmetry to profit from people unaware the software was available for free. The counterpoint is that distributors do work packaging the app -- maybe AccessConnections contributed some value by reviewing the content as a trusted third party.

So yeah, it's legal but might not be ethical. Open source licenses do require the source code and license to be accessible to the end user. This can be tucked away as a link in a credits screen. I'm not a lawyer, so I'm curious whether a link counts as source code distribution if you know your end users won't have unrestricted access to the Internet.

[1]: https://opensource.org/osd/

Agreed. I would not consider running a closed source shell because it's not auditable.

Discord's iOS and Android apps are built using React Native [1]. This enables business logic to be shared with the desktop and web clients, as well as shared UI components between both mobile apps.

Part of the reason you see abandoned repos is because the community has adopted libraries like Reanimated, React Native Gesture Handler, and React Navigation, which offer a lot of leverage to implement ambitious animations and native experiences in JS/TS.

React Native is mature enough to build big apps, and the community is active. It's still necessary to reach into Swift/Kotlin to implement some things, but for large apps that's not an unexpected lift. For cross platform JS/TS apps, no alternative offers the code sharing and delivery flexibility advantages of RN. I expect it'll remain relevant due to it's unique advantages and the community library stack will continue to mature.

[1] https://discord.com/blog/android-react-native-framework-upda...

Here's a recent example of typosquatting ads serving malware from the first Google search result:

https://threatresearch.ext.hp.com/adverts-mimicking-popular-...

I've always considered my phone getting charged while cable tethering to be a significant benefit.

Single PoE switch with cameras on a VLAN (so they don't have internet access). I use my old framework main board (yay for reuse!). Started with a USB Coral but switched to NVMe, which is more reliable passing through to a VM.

Frigate links some Dahua camera recommendations in their documentation: https://docs.frigate.video/frigate/hardware/

I installed them and they've been rock solid. Low light performance is excellent. The turret form factor is nice and unobtrusive.

Fandom is completely unusable these days without an ad blocker. I'm surprised communities still put up with it. Why hasn't another free wiki host emerged?

Goodhart's Law

Yep, but you need to do it on the board of a proprietary doorbell. Many projects take a cheap one and modify it. The unique thing about ratgdo is it reverse engineered the protocol.

Different density per monitor is something Wayland handles better than X11. https://news.ycombinator.com/item?id=25970690#25972514

The problem with this is Chamberlain also implemented an encrypted protocol over their control wires in the name of "security".

ratgdo is the perfect bridge for folks who want local-only control -- it can even read the open/close/light state off the signal wires.

On Pixel phones you can assign the extra dim toggle to pressing both volume keys at once. It's also accessible on many Android phones via a quick settings tile.

Re: MyQ, check out ratgdo [1]. It's a lovely little hardware project that wires into Chamberlain/Liftmaster controllers and provides a local WiFi-only interface. It integrates perfectly with HA and requires no soldering or disassembly to install. It's a shame Chamberlain discontinued their homekit bridge, because it shouldn't be necessary to use a cloud integration to trigger a garage door.

[1]: https://paulwieland.github.io/ratgdo

Yes, using native SVG is a feature not a bug. As is using native text nodes. Converting to paths is a postprocessing step and not difficult to do.

The hard part is making a WYSIWYG editor, which both Figma and Penpot accomplish beautifully. The freedoms described in their marketing material may not be for you, but they are not indicative of poor quality.

Quality is an expression of priorities. I find this kind of rant frustrating because it's missing the forest for the trees.

Awesome project! I'd strongly recommend swapping in some antireflective glass. There's a couple affordable options with less than 1% reflection [1][2]. Made a huge difference vs. stock acrylic on my frames that get lots of environmental light.

[1] https://www.groglass.com/product/artglass-ar-70/

[2] https://www.framedestination.com/prod/sh/ultravue-uv70-pictu...

Same selling points as Chromium originally: faster and safer. The premise of Servo is that it'd make better use of multicore and would be safer because it was written in a memory-safe language. For modern users the big one is probably battery usage, though, which Safari excels at but would be harder for an open source player that has to support every device.

Have you looked at the Zenphone 10? That appears to be the true Pixel 3 successor.

I remember Jeff Han's multitouch demos (which pre-dated the iPhone!) -- is this what you were thinking of? https://youtu.be/ac0E6deG4AU

Likewise, fair enough. I appreciate you clarifying your threat model. I try to operate with low trust dev environments whenever possible, which is a major motivation for using VMs. It only takes one malicious npm or pip package for it to pay off.

My motivation for sandboxing is to fearlessly tinker with unfamiliar dependencies without thinking too deeply about the supply chain. Starting with isolation makes it safer to experiment, which is important to me for velocity.

For example, let's say I've got a git repo on a guest VM and I'm syncing the dir to the host. If I run `git push` on the host (because my ssh key is there), it implicitly runs any pre-push script dropped there by the guest, defeating any isolation.

Yep! I run code-server inside the guest VM (or remote host). It's a great middle ground for snappy editing and isolation.

Re: provisioning, really basic automation around KVM. I've been meaning to experiment with Firecracker for more transient runtime environments.

Mounting a guest fs or syncing it to the host is rife with security footguns.

I've developed almost exclusively in VMs for over a decade. One reason I use VMs is to isolate the execution context from development and deployment. I used to passthrough from the host but poor performance and the lack of inotify are DX barriers. Passing through the FS to the host is a no-go because of subtle executable things like git-hooks that could enable sandbox escape.

The simplest and best approach I've found is to use a git remote on the host to push branches to/from the guest sandbox. I can commit on the sandbox fs and treat the host as an upstream remote. On the host I pull from the sandbox and push up to GitHub/etc. It's a bit more process but becomes second nature quickly and requires no extra tools. This also works well for remote servers.

Another approach I've used is lsyncd to sync files from the host to the guest (Mutagen is another cool syncing tool). In practice, though, I've found syncing to be a footgun too. It's too easy to edit a file on the host and blow away a change inside the guest with no undo. This is one reason I've found explicit git push / pull to be cleaner.

This is often termed a "Third Place" https://en.wikipedia.org/wiki/Third_place

Hah, I had a Deathstar die on me back in the early 00s too. Surprisingly, about a decade later I hammered it with ddrescue and was able to get almost all the data off it!

For sure. I knew I had all the right ingredients to restore, and had kicked the tires 6 months back, but I initially copied over the wrong key. When it failed to load I had a sad moment until I realized my mistake. In such fail moments there's a flash of clarity where every process gap becomes blindingly obvious.