Fixed an issue with the Signet client where, on some-but-not-all Debian 12 boxes, it wouldn't detect the signet unless it was inserted before the client was started.

It turned out to be something weird going on with inotify not providing the correct name of the symlink the the udev rule creates in /dev.

I'm still not sure why it's showing up all weird, but I found a way to handle it and that'll be in the next release.

Reply to this note

Please Login to reply.

Discussion

If anyone knows why the symlink is showing up in inotify as things like ".#signet373aec7d28de370a" instead of just "signet", which is what the symlink name actually is, LMK.

Somehow I think it might be too early for me to find any operating system programmers on nostr.

nostr:nevent1qqs8t9jxcflvlcvtw9n9639etxhj69e0ep4p2ekrhytyt96e966kn2spz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzp5cw4x82vh5487g6hylkkv82284n83gxlp75nasq5yu6auq249g3qvzqqqqqqyqaa2ag