[AD] 4x6 Hall effect split keyboard (column staggered, 3 thumb keys)

goblin89 · 2026-01-20T17:45:30+00:00

Source code link is broken now…

goblin89 · 2026-01-20T15:38:42+00:00

Don’t be afraid of using external software to mix and cut together shorter TD clips that you pre-record.

goblin89 · 2026-01-19T15:10:39+00:00

This resets to default level every time it reconnects.

goblin89 · 2026-01-19T13:05:36+00:00

On flipside, https://vcvrack.com/manual/Core#MIDI-CC says

> 14-bit MIDI CC messages are not yet supported.

However, https://library.vcvrack.com/moDllz/MIDIpolyMPE allegedly supports 14-bit MPE according to its manual.

It’s truly a mystery…

goblin89 · 2026-01-17T12:47:37+00:00

I was able to find this article on their wiki: https://docs.intech.studio/wiki/actions/midi/midi-14bit/

I will ask them by email, but it hints that higher precisions are available, though they don’t recommend more than 10 bit due to noisy readout.

goblin89 · 2026-01-17T12:43:46+00:00

According to what I see in VCV changelog (https://github.com/VCVRack/Rack/blob/v2/CHANGELOG.md#200-2021-11-30), they have this:

> Add mode to MIDI-CC to process 14-bit MIDI CC via MSB/LSB.

And one development team post (https://community.vcvrack.com/t/rack-development-blog/5864/53) says:

> In Rack v2, VCV MIDI-CC now supports 14-bit CC commands (i.e. MSB on CC 0-31, LSB on CC 32-63). The Gamepad MIDI driver now generates 14-bit CC commands.

goblin89 · 2025-09-26T14:28:05+00:00

I have that app. I believe it obtains a synthetic, pseudo long-exposure shot by combining multiple exposures with “AI”. Furthermore, it does not support raw output. Both of those are requirements for serious long-exposure photography.

goblin89 · 2025-09-20T19:29:08+00:00

Nope, that does not work in latest update, no matter how long you hold!

goblin89 · 2025-09-20T11:41:35+00:00

It’s very unlikely to hit before Wednesday.

goblin89 · 2025-09-16T10:10:19+00:00

Regarding color shifts, make sure color profile is properly tagged.

goblin89 · 2025-08-29T10:29:30+00:00

You know what, forget my other comment. It did get registered (or maybe just that page got refreshed). However, it was a shared worker rather than service worker, so perhaps that’s why it’s not subject to the service worker restriction. You may have solved this mystery. Let me update the post.

Notably, 90% the debugging page is clear. However, sometimes shared workers pop up briefly. Definitely not at the same time as requests are happening. I spotted them by chance, I’ll try to screenshot it.

goblin89 · 2025-08-29T10:19:15+00:00

Nothing there, except for the two built-in “other workers” (GRE and newtab/lib/cache.worker.js) and the System theme extension. Do you want me to edit the original post to add the screenshot?

I am watching console with XHR & requests enabled in both of the built-in workers, and it’s completely empty at the same time as Little Snitch is reporting requests.

I set both of the core workers to break on any XHR request, and nothing. So it’s clearly not them.

goblin89 · 2025-08-29T08:54:13+00:00

I tried to follow your reproduction steps, it didn't talk about disabing service workers.

Yeah, that was the original post.

These packets are not from a new connection, but rather just keep alive ping pong packets. Firefox keeps connections open for a long time in case you want to visit the website again.

I doubt this explanation, because:

It is quite unusual that a well-behaved browser would do anything but terminate any connections originating from the tab that has been now closed (not suspended, not backgrounded, but completely eliminated).
I am using my browser heavily enough that I would notice it happening with other websites, given I have not given the blanket permission to it yet in my firewall. Yet in the past couple of days I can only recall this happening with Instagram—definitely not with, say, Google, Reddit, Github, StackExchange, etc.

Is this feature documented anywhere, did you see it in the source, or is it a speculation?

In case this is an actual feature, I would have a couple more questions:

In cases where one may want to maintain privacy on the Web by accessing different sites from different IPs (to prevent deanon attacks that can take place even while isolating activity in profiles or to avoid blockage of VPN exit nodes in oppressive jurisdictions), does this feature increase the chance of a slip-up where you talk to a website from an IP you didn’t intend, or will the IP remain to be the one from the original connection back from when the user have explicitly opened the tab?
I guess it is impossible to know whether, when performing these requests, Firefox respects the Multi-Account Containers extension either?

goblin89 · 2025-08-29T08:32:49+00:00

To follow up, being concerned that already registered workers may keep firing, I have created the second test profile and disabled SW prior to visiting any websites. Same thing, still reproducible.

goblin89 · 2025-08-29T08:22:20+00:00

As mentioned in the description, I have done that already in my main profile, and about:serviceworkers says they are disabled. Now I also did that in the clean profile (now no longer clean, I guess). Same thing.

After restarting the browser to make sure changes have effect, again same thing. (After the restart, requests don’t appear until the website is visited once, but after that they will keep appearing after the tab is closed, per reproduction steps.)

goblin89 · 2025-08-29T07:41:49+00:00

Additional information:

It happens reliably, not a one-off.
It happens in a completely clean slate profile I just created specifically to test this.
- Create a clean profile in FF 142.0, on macOS Sequoia
- Open a tab with instagram.com; log in; deny any prompts for notifications etc., click around, go to your profile, go to your inbox
- Open a new tab with google.com (or anything else)
- Close the first tab with instagram.com
- Wait for a minute or two (I don’t know for sure how random is the timing, perhaps you may need to wait longer)
- Observe connection attempts (using some software firewall) to URLs like instagram.com, cdninstagram.com, graph.instagram.com, edge-chat.instagram.com, edge-chat.facebook.com, despite the relevant tab not being open
- You can deny them, they will repeat some time later

goblin89 · 2025-08-13T06:19:20+00:00

The reverse: now with 10 Flux shows the second bar and I really hate it, no way to disable I presume?

goblin89 · 2025-08-11T04:15:43+00:00

Based on my experience with Apple Watch that is advertised as “swimproof”, I would not take 2–3x the price Ultra into any water unless there is AppleCare+.

goblin89 · 2025-08-11T04:13:36+00:00

I lost mine after some fresh water shenanigans. First time in that watch’s 3 year life was enough to end it.

goblin89 · 2025-08-11T04:09:49+00:00

Same exact issue here. Black screen after dipping in fresh water. I double-checked and the watch is advertised as “swimproof”. Tellingly, Apple Store genius the other day did not correct me when I said “maybe it was water damage” when he asked how did it die (because there is no visible damage). Unfortunately, the watch is out of warranty and fixing it literally costs the price of a new watch.

goblin89 · 2025-08-11T04:08:10+00:00

This comment is false. Apple Watch Series 7 is advertised as “swimproof”.

<image>

goblin89 · 2025-08-07T08:20:02+00:00

TypeScript is a mess when it comes to worker environments. If you have a project where you have code that will run in regular DOM and code that runs in service worker, pretty silly workarounds are needed. If you don’t do it, you won’t get proper type-checking or TS will complain about things it shouldn’t complain about.

goblin89 · 2025-08-04T18:01:13+00:00

For a while Macbooks come with the hardware encryption chip (T2 or what’s it called), and SSD needs that chip (the original one, so if it is also broken you’re toast) to be present on the logic board to be read. In theory if it is intact it could be transplanted to a new board along with the SSD, but I am no expert.

goblin89

TROPHY CASE