Emelia/Emi

If you can't be with your waifu, become her. She/Her, Rather skittish. Am a giant nerd for trains, old computer stuff, and IPv6.

Follow requests subject to a loose vibe check.

Gender: HTTP 418 I'm a teapot
Location: HTTP 401 Unauthorized
PGP: 8900D5D4DB0AB41140C4012E379261EFD5FEA871
Age: Pre-Y2K
Optimal operating temperature: 68F/20C
Absolute Maximum operating temperature: 74F/23C
Storage Capacity: ~70TB

Public Key

npub18awg073vadjxw7vst9v3dduvxjulc7x7jjyskvqkjfa99xn28zdqj7pj7v

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsr7hy8lgkwker80xg9jkgkk7xrfw0u0r0ffzgtxqtfy7jjnf4r3xspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsphrcnu

Publishing to

relay.nostr.net

nos.lol

relay.damus.io

Author Public Key

npub18awg073vadjxw7vst9v3dduvxjulc7x7jjyskvqkjfa99xn28zdqj7pj7v

Show more details

Last Notes

2026-07-11 17:04:36 CEST

- reply

12€ is surprisingly *cheap*, at least to me. The last pinball place I saw recently was $20 USD (~17€ currently) and didn't have nearly as many machines. (In an area of the US where cost-of-living is fairly cheap, too)

2026-05-11 16:03:31 CEST

- reply

I wonder if the 'raw' depth camera is even accessible to regular software? If it works in NIR, I'm half tempted to play around with it simply for that... (In MacOS that is. I'm not allowed to put Asahi on my work mac for obvious reasons, and my only "personal mac" is an old Core2-era mini I use for firewire DVcam stuff)

2026-02-18 23:36:23 CET

- reply

I could tell almost instantly just by the way they were talking about it that it was pretty much guaranteed to be all in their head. With enough exposure to that type of stuff, you start to spot behavioral patterns that give off red flags long before what they say actually confirms it.

2026-02-07 17:34:55 CET

- reply

Yeah, KYC stuff *required by the government* should be able to take advantage of an "oauth-like" service provided by said government. *Age* verification more invasive than a yes/no question should be absolutely verboten online, IMO.
(Though I'd *also* allow for http response headers or meta tags, to have a *defined* mechanism to tell software *running on the device* "this site should be blocked if the user is under 18" akin to youtube's provided mechanisms to enforce "restricted mode", rather than relying on giant third-party site categorization lists...)

2025-09-07 01:15:59 CEST

- reply

At least with the dishwasher pump I had the freedom to tip the thing backwards so I could prod at the underside unimpeded... First time it turned out the pump wasn't broken, the impeller was just jammed by a load of beans (WTF?) and the second time was a *big* giant glass shard from Something. How the hell those even made it through the sump filter, I have no idea.
From the second photo you posted, I suspect what happened is that water got through the seals and corroded away the innards until either the windings shorted or the assembly seized; I suspect the cracked magnet was caused by the corrosion (probably rust-jacking from the corroding bits), but is otherwise unrelated to the motor failure.
(This also reminds me to spin my garbage disposal, since I never use it and it tends to seize up with rust if I don't spin it once every 2 weeks or so...)

2025-09-07 00:52:35 CEST

- reply

Sorta reminds me of the time that I had to replace the belt on a dryer: I had gotten the belt around the drum, but in order to properly wrap it around the tensioner I had to have each of my arms shoulder-deep in a different hole, with my head mashed up against the frame, thus doing the whole thing totally blind. Thankfully it was a pretty simple arrangement...

2025-07-25 16:41:28 CEST

- reply

The problem is that as hardware has progressed, the tech stack has eaten *all* that additional performance and more. Bloated Java applets and flash would probably *fly* on modern hardware, for a 'fair' comparison.

2025-03-10 18:45:56 CET

- reply

Same here, given that my grandfather literally did exactly that a few years back.
My bigger problem is that I've since picked up anime figures and model trains, the latter of which in certain configurations are even more expensive than old computers, given that they require a good bit more horizontal space to operate... And I still have access to the MIT flea market in the warmer months... (you can find all *sorts* of fun shit there. SGI machines, NeXT boxes, a SparcStation lunchbox, Old telephony line cards, etc.)

2025-03-07 23:15:03 CET

Ah, lazy resellers... I just acquired a bunch of used (the listing had clear pictures of new-in-shrinkwrap tapes...) LTO6 tapes that *still had data on them* from the last person that used them. (Some mac backup program. Unknown which one, but the tape "header" file started with RxvrDlt)
At least they didn't "erase" them with a degausser, which destroys the tape...

2025-03-05 06:52:23 CET

- reply

The latter is actually piping the output of a subshell into stdin, although it is the same construct as other FDs. From some digging, the correct forms are either<code>exec 3<> /path/to/file<br>bwrap --seccomp 3 ...<br></code>
or <code>bwrap --seccomp 3 ... 3</path/to/file<br></code>
depending on if you want the fd to be read/write or read-only.
And /proc/$pid/fd/ is one and the same with the integer file descriptors, it's just a way to see which process has what files open, and optionally to access them "out of band" (which is occasionally useful, since you can retrieve open-but-deleted files that way)

2025-03-05 06:29:41 CET

- reply

The only way to invoke child processes on linux is via exec() and friends, so if you're invoking bwrap via popen() (even if via an abstraction) all you need to do is clear the O_CLOEXIT flag on a memfd you stuff the BPF code into (which would ideally be done by the abstraction, of course)
bwrap does it that way because seccomp stuff is "a bit too unwieldy" to describe in command line parameters, since it takes compiled BPF bytecode directly. Much easier to make a memfd and pass the blob along that way. (If I had to guess, the reason it takes an fd over a filename is because you can use anonymous memfds without needing a writeable tempdir? not sure why there's not a "from file" option though; at least there's *probably* a bash-fu way to pass an fd for a file to something. Never had a need to, so don't know off the top of my head)

2025-03-05 05:20:55 CET

- reply

The problem is that setting up namespaces really needs a clone() call where you continue execution in the child process before actually jumping into the target code, and AFAIK a lot of non-C languages don't really support that all that well without some pretty gnarly FFI shenanigans: plain fork() or clone() can hurt pretty bad for processes with a lot of frequently-touched RAM like a JVM (or anything with a compacting GC, really), and the mitigations for that are "do not use this for anything but immediately calling exec()" levels of footgun, so you'd practically need to call into a separate executable regardless...
At least since you're usually passing the argv array directly to bwrap instead of a single big string that needs to be parsed, it's not anywhere *near* as prone to command injection vulnerabilities as system() is, since it's much harder to confuse something that doesn't really need to actually *parse* all that much...

2025-03-05 02:22:38 CET

- reply

For sandboxing: Do what nautilus does and use something like bwrap ('bubblewrap') to stuff it in a micro-container with no access to anything but OS library paths and a tempdir for input and output files. It works similarly to apple's "blastdoor" setup.
Optionally, use something like apparmor/selinux on top of that, as you can define 'child' policies under a parent policy that are far more restrictive than generic policies for them can be. (I have no idea as to the actual terms for this, I just know it's possible from looking at CUPS. This would require some shenanigans/effort to pull off, however)

2025-02-21 01:00:18 CET

- reply

Debian at least ships it pre-configured for sshd (and has a bunch of "ready to use" filters that you just need to turn on with a jail config), but I mostly just use it to keep the logspam down; nothing gets logged if their traffic gets dropped by nftables.
I treat it as more of a "really, stop knocking on my door" tool than an actual security boundary, as any half-determined attacker (like the various "AI" scrapers) would just keep trying from different IPs.

2025-02-14 06:08:51 CET

- reply

IMO there is a good reason for the BIOS to have at least a primitive networking stack: network booting. But *by god keep that disabled unless actually attempting netboot*. Outside of that very specific scenario, the BIOS should *never* touch the network card. (Traditionally this was implemented in the network card as an option ROM, but with onboard Ethernet I don't see a problem embedding the relevant module into the BIOS for cost reasons, assuming it lies dormant until called upon to netboot)
I set up a netboot server in my lab for various install/recovery media and never looked back. No more random "did I get the partitioning right on this flash drive?"

2025-02-10 23:30:16 CET

- reply

I mean, if you're not aiming for corporate targets, that's actually a pretty stealthy and reliable way to do it. Looks just like legit discord traffic, so impossible to block at the network layer without either invasive TLS inspection or flat-out blocking discord entirely.
The only "non-stealthy" part is if *discord* notices and bans you...

2025-02-03 03:51:57 CET

- reply

To clarify the last part, 'device' is the technical term for "the assembly that screws into the wall box and has the outlets on it", not the appliance plugged into the wall. So the daisy-chaining occurs entirely within the wall, same as what's inside of a power strip.
The only 'daisy chaining' from actual *appliances* that I'm aware of is older desktops (as in "they sit under the monitor" desktop) like my SparcStation having an AC passthrough (usually switched?) for the monitor, using a C13 socket.

2025-02-03 02:42:42 CET

- reply

The "single 15A outlet on a 20A circuit" is mostly the spirit of the "no oversized breakers" rule. Where you have *multiple* 15A outlets, the most likely source of overload is "too many things," so no individual outlet is overloaded, but with only a single outlet, the *only* way to trip the breaker is to overload that outlet, meaning that the breaker must be matched to the outlet's rating.
EDIT: but it's also perfectly fine to use 12-gauge wire on a 15A circuit, and in fact it's quite common: "it's what we had on hand", thermal derating in a full conduit, voltage drop for long runs, etc. so the easiest fix if you do accidentally do that is to just swap out for a 15A breaker on that circuit.

2025-02-03 02:41:48 CET

- reply

For the first part, mostly just that some people are *idiots* and would plug them into the same circuit, but most of the actual *safety* issues only come into play if the different plugs are not sufficiently isolated from one another (such as with the "microwave transformer jankwelder" using two 120v plugs to get 240v) at least assuming the breakers are working as intended. If they're not isolated, the exposed metal bits on the unplugged end can rise to 120v if only one is plugged in. Specialized equipment, like servers with redundant PSUs, are generally installed by people that "know what they're doing" and as such are not subject to that rule.
The daisy chaining is perfectly safe: there's a two-screw "bus bar" on each side of the device that handles all the 'passthrough' current.

2025-02-03 01:58:24 CET

- reply

A single load using multiple plugs is generally "frowned upon" for very good reasons, so the only valid reason to have a 20A circuit feeding 15A outlets is simply to have *more* 15A outlets, or multiple <15A high-draw loads on the same circuit (which under load calculation rules is effectively the same thing: max outlet count is based on estimated load per outlet)
The 'daisy chain' configuration I was talking about is for the in-wall wiring: power from the breaker goes to one device, then it's "daisy chained" *through* that device to the next one.
Also, the only case where you *can't* use a 15A outlet on a 20A circuit is when you only have a single outlet. It's actually rather difficult to break that rule though, since the vast majority of devices are duplex (two outlet), and as such meet the "more than one outlet on the circuit" criteria.

2025-02-03 01:13:32 CET

- reply

I'm not kidding about the "15A" outlets almost always being 20As with a different plastic face. If you take one apart, you can see the bits for connecting to the 20A's rotated blade. IIRC either NEC or UL requirements were updated to effectively require that a while back, explicitly *because* you can make a legal 20A circuit out of multiple 15A outlets, and one legal wiring configuration effectively "daisy chains" the outlets (takes up less space in the box than a pigtail, but is also somewhat harder to work with, IMO. Wago pigtails all the way)

2025-02-03 01:05:58 CET

- reply

The kitchen circuits themselves are perfectly legal: they have more than one 15A socket on each 20A leg. The requirement is because the circuits may have *multiple* high-draw appliances on them, not a single big fat 20A appliance, so it perfectly complies with both the letter and spirit.
As for the range plug, I use the oven enough that it would be too much of a PITA, plus the thing's buried behind the oven.
The only reason a UPS needs a bigger plug than the load is because it needs to charge the batteries while the load is running. If you can charge them from a *separate* circuit, you can split the combined load.
The extension cord option relies on the outlets being "sneaky 20As" (because they *are* 20A outlets with a 15A faceplate) and putting a "15A" plug on the wall end of a big fat 20A-capable extension cord and just plugging the UPS into that instead. Basically making a really long adapter, since everything in that chain *supports* 20A, they're just physically configured to not "allow" it.

2025-02-03 00:43:33 CET

And yet again I am reminded the hard way that I should have a UPS (My money's on "rat/squirrel" or "excavator"). Unfortunately the only UPSes big enough to run my desktop *won't plug into anything in my apartment* because the builders were complete cheapasses and ran 15A circuits.
And for the mandatory 20A circuits in the kitchen? 15A outlets "because fuck you that's why."
My only option for a UPS is one that either does some hinky shit to charge from a separate circuit than the load is on, or stringing a big fat 10-gauge extension cord across my shoebox from the kitchen after bodging a 5-15 make-a-cord on the wall end. (In the US all modern 15A outlets are really 20As with a different faceplate, so this is perfectly *safe* to do, if not quite "up to code"...)
(I *somewhat* miss my parents' basement, because the ceiling is unfinished I was able to run a big fat 20A circuit to the rack for the UPS, with room to upgrade to a 240v-30 feed for the fatass rackmount models if needed)

2024-11-20 02:22:24 CET

- reply

If you used a sync separator to pull the hsync and vsync off of the composite output (yes, the newer ones still have it, it's in the headphone jack), I imagine that you could *probably* set the scanout timings close enough to push some pixels coherently?
For some details, someone [did it with a beagleboard](https://trmm.net/Mac-SE_video/ ) using the PRUs, but the pi doesn't have those, so you'd need to see what you can do with the GPU hardware instead (thankfully it's actually quite well documented these days)

2024-11-18 19:53:01 CET

- reply

...and this reminds me I still need to fix my minitel's CRT/PSU board... I initially thought it was a bad PSU so did a thing that *actually* blew the PSU, so I somehow need to conjure something that can spit out +-8v and 24v and then fix the still-broken CRT driver...
(I was already planning on replacing the PSU because it's 220v-only and I really don't feel like either wiring it to a dryer plug or hauling around a transformer with it...)

2024-11-15 22:12:08 CET

- reply

'Kanchou' is basically the japanese version of "sack tap": put two finger pistols together side by side, then poke someone in the bumhole as hard as you can. Having chocolate stuffs basically named "sack tap" just feels *wrong* for some reason...

2024-11-15 22:07:47 CET

- reply

Yeah, that's close enough to be "how did marketing not catch that?" (of course, given the English packaging, I'm not sure marketing knows enough Japanese *to* catch that...)

2024-10-11 03:38:14 CEST

- reply

That's exactly what I did in my old cave: ran the window AC off the existing 15A circuit shared with the adjacent bedroom (it's a tiny one so that's fine) and dropped a new 4-gang box with a dedicated 20A feed to run all my lab shit. Said cave is now the guest bedroom since I moved out, and the massive outlet array is *really* out of place in the middle of an empty wall...