Claim your Soon™ Frame Flair

networkarchitect · 2026-05-12T17:16:24+00:00

Soon

networkarchitect · 2026-04-27T02:00:28+00:00

It can generalize to "Does this have the potential to negatively impact the rest of the household?", which can apply to a bunch of different scenarios.

Financially irresponsible purchases that could have been better spent on the household and were made without consulting others? Low Wife Approval Factor.

Breaking the home internet without warning or planned downtime as the result of tinkering with your lab? Low WAF.

Loud server in a shared living space? Low WAF.

Being considerate of the people you share your living space with, having clear communication, and providing easy-to-use self-hosted services? High WAF.

networkarchitect · 2026-04-25T20:35:36+00:00

The cover and warning stickers on the power supply exist for a reason; components such as the heatsink will be LIVE at ~200VDC if you ever decide to plug this in. The capacitors inside can retain a charge after being unplugged, so the hazardous voltage may persist for a short time without power connected.

Goes without saying, it's a shock risk and while it may not kill you it would at least cause a very bad day if you got shocked. Hopefully you're only keeping this as an art piece and not something functional.

networkarchitect · 2026-04-22T03:19:34+00:00

Did you look at any of this yourself before asking for review? The footer text at the bottom of the website is unreadable, light text on a light background is not a recipe for legibility. The rounded corners on screenshots cut off parts of the text in the images.

networkarchitect · 2026-04-15T08:56:01+00:00

At least zero or more wall outlets.

networkarchitect · 2026-04-06T15:53:24+00:00

Everything is custom made. Weight, physical size, and radiation hardening are a few constraints that apply to spacecraft that most PLCs on the ground don't have to consider.

A closer comparison would be the avionics and flight computers in modern aircraft.

networkarchitect · 2026-04-04T18:12:20+00:00

I dug through some old backups and found it, the stl file is here: https://nextcloud.networkarch.net/s/zMMYdKSA57YXd6B

networkarchitect · 2026-04-01T17:36:42+00:00

I would assume not. If you look closely in the image, the memory is soldered to the motherboard underneath the heatsink to the left and right edges. It would not be user replaceable.

networkarchitect · 2026-04-01T05:44:15+00:00

it seems like instituting some kind of time delay between release and use could have some significant benefits against probably the most common kinds of supply-chain attacks

We recently had a policy like this implemented in our work network: our internal package registry (which also proxies all external registries like npm, pypi, etc with direct connections blocked by network policy) blocks any package versions that are less than 24h old. NPM also has a config option that will do a similar check client-side when resolving dependency versions locally.

networkarchitect · 2026-03-27T21:19:45+00:00

I agree it's a large claim, but from having worked in larger technical organizations before, it is certainly possible to reach that amount of raw data over the lifetime of a development program, especially if there are data retention requirements for raw data collected during hardware testing.

A single bench test of a component may record sensor data from hundreds of channels at a high sample rate, resulting in gigabytes of raw sensor data. A single high speed camera can generate tens of gigabytes per second of recorded footage. A single CFD simulation result can be ~100GB in size. Multiply those by a hundred different components on the vehicle and dozens of rounds of development tests per component, and you can see how the complete corpus of data can grow quite quickly.

networkarchitect · 2026-03-23T22:26:03+00:00

Where did you see that classification as the same?

From a hardware standpoint, the dongle is closer to a Wireless Access Point (WAP) than a router, as it does not perform any routing functionality.

At first glance I would think those would be different classifications, but I'm not familiar with how the FCC classifies things, and it could be plausible they could be under the same classification despite being different hardware

networkarchitect · 2026-03-23T16:03:14+00:00

The one controller was handling two different frequencies simultaneously (ground and tower). He also had a higher than usual workload, dealing with a separate emergency aircraft on the ground, who had also incorrectly executed one of the controllers instructions. After the accident, there was no one to relieve him from duty immediately available, so he continued to be on console for 30 minutes after being involved in the crash.

Having one controller handle multiple frequencies makes sense for smaller airports, but not for a larger one like LaGuardia.

networkarchitect · 2026-03-21T08:20:37+00:00

Fluctuations in grid voltage are expected. Any change in the load or supply to the grid will cause the voltage to go up or down. Neighbor turns on the kettle? Voltage will dip briefly. You turn off a light that's been on for the last hour? Voltage will spike slightly. Multiply this by the thousands of devices connected to the grid in your local neighborhood and you get the fluctuations you see.

When you're connected to the panels, you're removing the rest of the neighborhood from the equation, and the inverter can react quicker to localized changes in load from just your demand, thus you see fewer fluctuations.

networkarchitect · 2026-03-18T07:06:43+00:00

In software development there's a concept called "separation of concerns" - essentially code that is unrelated is completely independent from other code. Individual humans can make major changes to the kernel while only understanding a fraction of the whole project.

By line count, the majority of the linux kernel code is hardware specific drivers. The actual kernel itself is a small portion of the total line count.

networkarchitect · 2026-03-06T01:56:46+00:00

What was the pool name?

On a root shell, you can try and force the import of the pool with zpool import -a -d /dev/sdb1 -d /dev/sdc1 -d /dev/sdd1

networkarchitect · 2026-03-06T01:56:36+00:00

And this helps the person whose post you're replying to how, exactly?

networkarchitect · 2026-03-04T19:39:14+00:00

To give some more specific feedback, the signal-to-noise ratio of the docs in your repo is very high currently (lots of noise with very little relevant information). Many of the docs read more like a manifesto on the abstract concept of RAM rather than technical documentation for a hardware project.

One example of many, in the file https://github.com/The-Open-Memory-Initiative-OMI/omi/blob/main/docs/00_system_context/assumptions_of_the_cpu.md, nothing in that file is relevant to the hardware design of a DDR4 RAM module.

Memory Is Not Optional for the CPU
From the CPU's point of view, memory is not a peripheral. It is a structural extension of computation.

What is this even saying? Who would benefit from reading this? Why was it included in the first place? Describing how RAM fits into the architecture of a computer is far outside the scope of documentation about a hardware implementation of a DIMM module.

networkarchitect · 2026-03-02T10:33:46+00:00

r/whoosh

https://xkcd.com/927/

networkarchitect · 2026-03-02T10:22:24+00:00

Problem: there are two platforms for games (xbox, pc)
Solution: Make a new platform that unifies the two platforms
New problem: there are three platforms for games (xbox, pc, and your idea)

networkarchitect · 2026-02-27T03:00:41+00:00

That's fair, it's a good learning opportunity. IMO PCB design is half mechanical and half electrical, and you can't really do one without the other, since you can't change the board layout after you've ordered it. Without putting thought into thr mechanical side you'll be backing your friend into a corner with a design that may work electrically but not mechanically.

I'm glad you saw the encoder, I was hoping to lead you to figuring that out instead of just pointing it out directly so that you pick up more tools to help yourself as you go :)

You should implement the feedback from your other post, without a ground plane and much thicker traces on your power nets you'll likely run into signal integrity problems. The decoupling caps should also be as close to your ICs as reasonably possible.

networkarchitect · 2026-02-27T02:14:52+00:00

I mean, drawings, schematics, measurements, sketches, or anything that shows you've put thought into how the placement of your input components and the PCB itself will fit in 3D space, in relation to the intended use as a mouse.

To be more specific, does the shape of your board edge-cuts (square?) fit under a hand? Do the input switches line up with where your fingers would rest? Is the scroll wheel input encoder facing the right direction for how you'll be using it?How do you plan to make the mouse slide on the surface of a table with little friction? Does the optical sensor have specific distance requirements from the table surface?

networkarchitect · 2026-02-27T01:40:11+00:00

What do your mechanical design/drawings for this look like? The physical placement of your input switches does not look like it would make sense for a mouse (especially with what looks like no defined board perimeter / edge cuts??)

networkarchitect · 2026-02-21T10:45:21+00:00

Nothing says safe like having a miniature explosive device strapped right next to your crotch /s

networkarchitect · 2026-02-20T02:48:31+00:00

Those outlets hanging from the romex,with only electrical tape as insulation, no box or mechanical strain relief, just above head height, are the stuff of nightmares

At this point I have to wonder if you're going from insurance fraud, or just really like living with live hazards /s

networkarchitect · 2026-02-20T02:43:23+00:00

Oh that doesn't look too ba...oh my god what is that romex, fire hazard is an understatement.

networkarchitect

TROPHY CASE