Sungbin Jo
@goranmoomin.dev
programming on the web with react and on the mac with cocoa, appkit, and swift. interested in programming languages and low-level system programming. an emacs user. profile image not me.
i could not resist, i updated my main device to ios 26 on the first day… and it’s burning through battery like crazy lol
June 9, 2025 at 9:16 PM
i could not resist, i updated my main device to ios 26 on the first day… and it’s burning through battery like crazy lol
the fact that the window rounded corners’ radius doesn’t match with the traffic lights annoy me immensely… eww
June 9, 2025 at 6:03 PM
the fact that the window rounded corners’ radius doesn’t match with the traffic lights annoy me immensely… eww
#wwdc25 seems like ipados 25 also has an actual windowing system (finally)?
www.apple.com/newsroom/202...
www.apple.com/newsroom/202...
June 9, 2025 at 5:52 PM
#wwdc25 seems like ipados 25 also has an actual windowing system (finally)?
www.apple.com/newsroom/202...
www.apple.com/newsroom/202...
as per xkcd.com/386/:
someone is *wrong* on the internet.
someone is *wrong* on the internet.
April 26, 2025 at 9:47 AM
as per xkcd.com/386/:
someone is *wrong* on the internet.
someone is *wrong* on the internet.
it’s scarily capable — both openai’s o3 and claude 3.7 sonnet with thinking can go through whole chunks of javascript, figure out which module id corresponds to what logic, and can explain the logic with unminified, prettified names.
actually pretty useful, i’ve confirmed that they are correct.
actually pretty useful, i’ve confirmed that they are correct.
April 24, 2025 at 10:46 PM
it’s scarily capable — both openai’s o3 and claude 3.7 sonnet with thinking can go through whole chunks of javascript, figure out which module id corresponds to what logic, and can explain the logic with unminified, prettified names.
actually pretty useful, i’ve confirmed that they are correct.
actually pretty useful, i’ve confirmed that they are correct.
i had a friend buy me a 4-inch, used iphone se over from a trip to japan (it was 4000 yen), and it feels super weird to hold this tiny, tiny phone (by current standards).
almost feels like i’m back in an alternative 2016.
almost feels like i’m back in an alternative 2016.
April 23, 2025 at 9:36 AM
i had a friend buy me a 4-inch, used iphone se over from a trip to japan (it was 4000 yen), and it feels super weird to hold this tiny, tiny phone (by current standards).
almost feels like i’m back in an alternative 2016.
almost feels like i’m back in an alternative 2016.
genuinely curious: why would ‘randomly relink kernel on every boot’ be a mitigation to anything? isn’t it the case where if you can jump a kernel address anyway, that’s pretty much shoot, no?
(it’s the openbsd innovation page, if anyone’s interested: www.openbsd.org/innovations....)
(it’s the openbsd innovation page, if anyone’s interested: www.openbsd.org/innovations....)
February 23, 2025 at 4:09 AM
genuinely curious: why would ‘randomly relink kernel on every boot’ be a mitigation to anything? isn’t it the case where if you can jump a kernel address anyway, that’s pretty much shoot, no?
(it’s the openbsd innovation page, if anyone’s interested: www.openbsd.org/innovations....)
(it’s the openbsd innovation page, if anyone’s interested: www.openbsd.org/innovations....)
finally apple intelligence coming in korean (in early april). finally!
February 21, 2025 at 9:03 AM
finally apple intelligence coming in korean (in early april). finally!
i know that i did probably not write a good prompt to begin with, but it does seem that the claude model seems to be biased too much towards react code…
i did not expect a react component from asking a way to check health for disks.
i did not expect a react component from asking a way to check health for disks.
![A Claude conversation that goes on as below:
q: how can i check the health of specific disks?
a: I'll help you create a script to check disk health. Here's a React component that can display disk health metrics:
<Disk Health Monitor>
This component creates a visual dashboard for monitoring disk health. Here's what it tracks:
Storage usage with a visual progress bar that changes color based on capacity
Disk temperature with warnings for high temperatures
Error count tracking
Read and write speeds
Overall disk health status with warnings for potential issues
The component uses color coding to make it easy to spot potential problems:
Green: Good/normal conditions
Yellow: Warning conditions that need attention
Red: Critical conditions (like very high storage usage)
To get real disk health data, you'd need to connect this component to system monitoring tools that can provide actual disk metrics. Common tools for collecting this data include:
[the remaining conversation is not visible]
On the right, the claude artifact displays a webpage that displays a list of hardcoded storage usage, temperature, error count, i/o speed, and the total status of the two disks.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreiefyx7yezy6f3mkip5oant7i5nrpjspbeicxiltnnatoafkcuod5a@jpeg)
February 10, 2025 at 9:51 AM
i know that i did probably not write a good prompt to begin with, but it does seem that the claude model seems to be biased too much towards react code…
i did not expect a react component from asking a way to check health for disks.
i did not expect a react component from asking a way to check health for disks.
Am I going crazy or is the kerning between Y and e of the Yeah seems to be wrong?
This is the official Bluesky client, up-to-date. Seems like something is off with the fonts…
This is the official Bluesky client, up-to-date. Seems like something is off with the fonts…
February 4, 2025 at 5:06 AM
Am I going crazy or is the kerning between Y and e of the Yeah seems to be wrong?
This is the official Bluesky client, up-to-date. Seems like something is off with the fonts…
This is the official Bluesky client, up-to-date. Seems like something is off with the fonts…
my macos/emacs experience shows
![Which Ctrl- keyboard shortcuts do you use in your terminal?
[x] Ctrl-C (quit)
[x] Ctrl-Z (suspend)
[x] Ctrl-R (search history)
[ ] Ctrl-L (clear screen)
[x] Ctrl-D (EOF)
[x] Ctrl-A (beginning of line)
[x] Ctrl-E (end of line)
[x] Ctrl-W (delete word)](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreiga2cdnuyuuqa7jr3666mbt5diohfxcsbienmoxlfzygbvs2u7ltq@jpeg)
January 8, 2025 at 5:38 PM
my macos/emacs experience shows
Just from the screenshots, the settings screen scream obviously Electron.
I don’t have a way to really articulate it but from the screen layout, the margins and paddings of the tab titles, the thin titlebar, and the white background color of each tab all feel very… webby and not native at all.
I don’t have a way to really articulate it but from the screen layout, the margins and paddings of the tab titles, the thin titlebar, and the white background color of each tab all feel very… webby and not native at all.
January 2, 2025 at 2:53 AM
Just from the screenshots, the settings screen scream obviously Electron.
I don’t have a way to really articulate it but from the screen layout, the margins and paddings of the tab titles, the thin titlebar, and the white background color of each tab all feel very… webby and not native at all.
I don’t have a way to really articulate it but from the screen layout, the margins and paddings of the tab titles, the thin titlebar, and the white background color of each tab all feel very… webby and not native at all.
That was fast… shout out to Screens!
edovia.com/en/screens/
edovia.com/en/screens/
![Edovia Support (Edovia Helpdesk)
Dec 27, 2024, 11:53 EST
Hi Sungbin Jo,
Thanks for your inquiry!
Just to let you know that we found the issue and Screens 5.4.9 should be available soon. We'll let you know when the version is available.
Sorry for the inconvenience and thank you for your patience.
Have a wonderful day!
—
Timothy
Edovia Support
Goranmoomin
Dec 27, 2024, 11:03 EST
Hello!
I’d like to report a bug in Screens 5 when using my iPad's hardware keyboard.
The hardware arrow keys are sending wrong key events (or at least different key events from the software arrow keys on screen) via VNC, when connecting to a Wayland compositor. Instead of sending the expected Up keypress (key 111, sym 65362), it is sending a Shift modifier followed by a ‘U’ keypress (key 30, sym 85).
This makes it impossible to use arrow keys for navigation in apps like VSCode, Cursor, and Firefox since they just type 'U' instead of moving the cursor. The same problem happens with other arrow keys and the ESC key too.
The following is output from the Wayland event viewer (wev) between the two:
Software arrow key:
[21: wl_keyboard] key: serial: 331; time: 0; key: 111; state: 1 (pressed)
sym: Up (65362), utf8: ''
[19: wl_keyboard] key: serial: 331; time: 0; key: 111; state: 1 (pressed)
sym: Up (65362), utf8: ''](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreiatwungno4dyjwpjzruuwtcpvjkqt7j2rddiyrdavqga72baignuq@jpeg)
December 27, 2024 at 6:17 PM
That was fast… shout out to Screens!
edovia.com/en/screens/
edovia.com/en/screens/
![A GitHub screenshow with the following contents:
[unicorn image]
We couldn't respond to your request in time.
Sorry about that. Please try refreshing and contact us if the problem persists.
Contact Support — GitHub Status — @githubstatus](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreidyhn2thhbd64gma4eqlznz54ysa7kc44wkdx55guqrmabzitylba@jpeg)
yeah so i first created my account with the picopds/create_identity.py script (when first trying to use picopds): github.com/DavidBuchana...
and it generated the privkey.pem file for me.
i then created the account with all of the info when moving to millipds: as in the screenshot.
and it generated the privkey.pem file for me.
i then created the account with all of the info when moving to millipds: as in the screenshot.
![sungbin@sungbin-macmini:~/millipds$ uv run millipds account create did:plc:ilbuexsezfgfn6ospjcpkupt test00.dev.goranmoomin.dev --unsafe_password=[redacted] --signing_key=../picopds/privkey.pem
WARNING: passing a password as a CLI arg is not recommended, for security
INFO:millipds.database:creating account for did=did:plc:ilbuexsezfgfn6ospjcpkupt, handle=test00.dev.goranmoomin.dev](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreieqeexyg44eedpdmwd3364ggux2rliazcj3743netdtvot3raxzoy@jpeg)
December 2, 2024 at 2:39 AM
yeah so i first created my account with the picopds/create_identity.py script (when first trying to use picopds): github.com/DavidBuchana...
and it generated the privkey.pem file for me.
i then created the account with all of the info when moving to millipds: as in the screenshot.
and it generated the privkey.pem file for me.
i then created the account with all of the info when moving to millipds: as in the screenshot.
i'm logging the outbound jwt that i'm sending to the appview, and from logging it does seem that it's being signed by the correct key, and that the corresponding public key is uploaded to plc.directory/did:plc:ilbu... – though tbf i'm failing to validate the jwt in jwt.io.
![sungbin@sungbin-macmini:~/millipds$ uv run millipds config
db_version : 1
pds_pfx : 'https://pds.dev.goranmoomin.dev'
pds_did : 'did:web:pds.dev.goranmoomin.dev'
bsky_appview_pfx : 'https://api.bsky.app'
bsky_appview_did : 'did:web:api.bsky.app'
jwt_access_secret : '[REDACTED]'](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreie2xhlkazqt4f7v3tnsr5afqmmkys2nqhk3dxojgjujgzv5dfw3pe@jpeg)
December 2, 2024 at 2:31 AM
i'm logging the outbound jwt that i'm sending to the appview, and from logging it does seem that it's being signed by the correct key, and that the corresponding public key is uploaded to plc.directory/did:plc:ilbu... – though tbf i'm failing to validate the jwt in jwt.io.
so i'm assuming that the jwt error is coming from:
github.com/bluesky-soci...
which is prob being called from
github.com/bluesky-soci...
millipds signs a new jwt when proxying to the appview with the right key.
so error is prob that bsky is failing to validate them from the keys from plc.directory?
github.com/bluesky-soci...
which is prob being called from
github.com/bluesky-soci...
millipds signs a new jwt when proxying to the appview with the right key.
so error is prob that bsky is failing to validate them from the keys from plc.directory?
![@authenticated
async def static_appview_proxy(request: web.Request):
lxm = request.path.rpartition("/")[2].partition("?")[0]
# TODO: verify valid lexicon method?
logger.info(f"proxying lxm {lxm}")
db = get_db(request)
signing_key = db.signing_key_pem_by_did(request["authed_did"])
authn = {
"Authorization": "Bearer "
+ jwt.encode(
{
"iss": request["authed_did"],
"aud": db.config["bsky_appview_did"],
"lxm": lxm,
"exp": int(time.time()) + 60 * 60 * 24, # 24h
},
signing_key,
algorithm="ES256",
) # TODO: ES256K compat?
} # TODO: cache this!
appview_pfx = db.config["bsky_appview_pfx"]
if request.method == "GET":
async with get_client(request).get(
appview_pfx + request.path, params=request.query, headers=authn
) as r:
body_bytes = await r.read() # TODO: streaming?
return web.Response(
body=body_bytes, content_type=r.content_type, status=r.status
) # XXX: allowlist safe content types!
elif request.method == "POST":
request_body = await request.read() # TODO: streaming?
async with get_client(request).post(
appview_pfx + request.path, data=request_body, headers=(authn|{"Content-Type": request.content_type})
) as r:
body_bytes = await r.read() # TODO: streaming?
return web.Response(
body=body_bytes, content_type=r.content_type, status=r.status
) # XXX: allowlist safe content types!
elif request.method == "PUT":
raise NotImplementedError("TODO")](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreigdr74aw4h7ryeg5likhdofiuo43jdk6iwnrfk7237pwtjkmeaydi@jpeg)
December 2, 2024 at 2:09 AM
so i'm assuming that the jwt error is coming from:
github.com/bluesky-soci...
which is prob being called from
github.com/bluesky-soci...
millipds signs a new jwt when proxying to the appview with the right key.
so error is prob that bsky is failing to validate them from the keys from plc.directory?
github.com/bluesky-soci...
which is prob being called from
github.com/bluesky-soci...
millipds signs a new jwt when proxying to the appview with the right key.
so error is prob that bsky is failing to validate them from the keys from plc.directory?
Was a tad surprising to me at least :)
October 19, 2024 at 12:24 AM
Was a tad surprising to me at least :)
I’m also just realizing that on the iPad with an external trackpad, a user’s feed doesn’t scroll if you try to scroll it on top of the user description (instead of the top of the posts list).
I should know better and report bugs via proper channels, but just to let people know.
I should know better and report bugs via proper channels, but just to let people know.
October 7, 2024 at 8:49 PM
I’m also just realizing that on the iPad with an external trackpad, a user’s feed doesn’t scroll if you try to scroll it on top of the user description (instead of the top of the posts list).
I should know better and report bugs via proper channels, but just to let people know.
I should know better and report bugs via proper channels, but just to let people know.
I’m swiping the same short distance with the same speed & snap for the three apps, and the standard iOS gesture recognization seems to register but the sidebar of the bluesky app seems to bounce off.
(Btw I’d love a draft feature in the app, just realized)
(Btw I’d love a draft feature in the app, just realized)
October 7, 2024 at 12:42 AM
I’m swiping the same short distance with the same speed & snap for the three apps, and the standard iOS gesture recognization seems to register but the sidebar of the bluesky app seems to bounce off.
(Btw I’d love a draft feature in the app, just realized)
(Btw I’d love a draft feature in the app, just realized)
One of the immediate things that felt ‘off’ to me was navigation.
Like I have a video comparing the navigation stack with other apps — the top bar fades out (instead of sliding) and the previous screen should have a light shadow.
The sidebar gesture recognizer also feels off…
Like I have a video comparing the navigation stack with other apps — the top bar fades out (instead of sliding) and the previous screen should have a light shadow.
The sidebar gesture recognizer also feels off…
October 7, 2024 at 12:29 AM
One of the immediate things that felt ‘off’ to me was navigation.
Like I have a video comparing the navigation stack with other apps — the top bar fades out (instead of sliding) and the previous screen should have a light shadow.
The sidebar gesture recognizer also feels off…
Like I have a video comparing the navigation stack with other apps — the top bar fades out (instead of sliding) and the previous screen should have a light shadow.
The sidebar gesture recognizer also feels off…
For now, I'm using the enchanted command below:
```
tar -cvzf - -C<srcdir> --no-xattrs --no-mac-metadata . | ssh <dstsrv> tar -xzf - -C<dstdir>
```
Note the flags --no-xattrs and --no-mac-metadata.
The manpage is wrong, --no-mac-metadata does applies to c mode as well, not just x mode.
```
tar -cvzf - -C<srcdir> --no-xattrs --no-mac-metadata . | ssh <dstsrv> tar -xzf - -C<dstdir>
```
Note the flags --no-xattrs and --no-mac-metadata.
The manpage is wrong, --no-mac-metadata does applies to c mode as well, not just x mode.
September 21, 2024 at 3:59 PM
For now, I'm using the enchanted command below:
```
tar -cvzf - -C<srcdir> --no-xattrs --no-mac-metadata . | ssh <dstsrv> tar -xzf - -C<dstdir>
```
Note the flags --no-xattrs and --no-mac-metadata.
The manpage is wrong, --no-mac-metadata does applies to c mode as well, not just x mode.
```
tar -cvzf - -C<srcdir> --no-xattrs --no-mac-metadata . | ssh <dstsrv> tar -xzf - -C<dstdir>
```
Note the flags --no-xattrs and --no-mac-metadata.
The manpage is wrong, --no-mac-metadata does applies to c mode as well, not just x mode.
Can anyone using Homebrew (brew.sh) and on macOS Sequoia check whether `rsync` works?
I'm using rsync v3.3.0 compiled via MacPorts, and it seems that the rsync I have is broken on Sequoia for some reason…
Is this specific to MacPorts or is this a global thing?
I'm using rsync v3.3.0 compiled via MacPorts, and it seems that the rsync I have is broken on Sequoia for some reason…
Is this specific to MacPorts or is this a global thing?
![3 consecutive executions of the command `rsync -avz dist/ sungbin-macmini:/srv/www/cosmo.goranmoomin.dev` failing.
The first failing error message is:
```
ssh: connect to host home.goranmoomin.dev port 8222: Undefined error: 0
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.3.0]
```
The consecutive error messages are:
```
ssh: connect to host home.goranmoomin.dev port 8222: Undefined error: 0
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(231) [sender=3.3.0]
```](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:7zbh5pwgh2rjzwnmooj75d2e/bafkreieouh7vq7ggedi5t6miiobyg62bszxqhhebyysart57gic5kxzckm@jpeg)
September 21, 2024 at 3:54 PM
Can anyone using Homebrew (brew.sh) and on macOS Sequoia check whether `rsync` works?
I'm using rsync v3.3.0 compiled via MacPorts, and it seems that the rsync I have is broken on Sequoia for some reason…
Is this specific to MacPorts or is this a global thing?
I'm using rsync v3.3.0 compiled via MacPorts, and it seems that the rsync I have is broken on Sequoia for some reason…
Is this specific to MacPorts or is this a global thing?
Building all of my 600 installed packages from source (as there are yet to be binary packages for Sequoia on MacPorts) on my MBP.
Hopefully it doesn't take more than a few hours.
This time though, MacPorts now finally has an automatic macOS upgrade/migration process (`sudo port migrate`)!
Hopefully it doesn't take more than a few hours.
This time though, MacPorts now finally has an automatic macOS upgrade/migration process (`sudo port migrate`)!
September 18, 2024 at 10:50 PM
Building all of my 600 installed packages from source (as there are yet to be binary packages for Sequoia on MacPorts) on my MBP.
Hopefully it doesn't take more than a few hours.
This time though, MacPorts now finally has an automatic macOS upgrade/migration process (`sudo port migrate`)!
Hopefully it doesn't take more than a few hours.
This time though, MacPorts now finally has an automatic macOS upgrade/migration process (`sudo port migrate`)!