<unnamed>

Public Key

npub1xlujzkga36wzu7zn6cs5q8nj05u90g6qdgqhryemyx7qm87qujksjhmvg0

Profile Code

nprofile1qqsr07fptywca8pw0pfavg2qree86wzh5dqx5qt3jvajr0qdnlqwftgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqxg86cu

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Last Notes

2026-08-01 09:53:27 UTC

https://media.shitposter.world/shitposter.club/0d/15/ec/0d15ec1f17c3b208c0325e62caa5ab7f744721d7569478482b2b020edbbe129e.jpg?name=CowrLx0wIbKMGQ.jpg

2026-07-27 00:59:41 UTC

protip: if you have sensitive sexual questions, an abliterated model won't refuse or lecture you, it will just give you the god damn answer like a good robot should when ordered

2026-07-26 22:38:02 UTC

- reply

@npub1jsv…rmqs yeah. Nobody in Japan remembers the masters cartoon so their angle is showa nostalgia

2026-07-26 22:36:59 UTC

- reply

@npub14ew…0rhj the only people left are qtards

2026-07-26 08:25:49 UTC

- reply

@npub1uja…ueyp thanks for the input, I appreciate it. I'll take it under consideration.

2026-07-26 08:11:47 UTC

Reminder it also works on mobile
https://media.shitposter.world/shitposter.club/fd/8e/fc/fd8efce9fb5705919a169f951fdbcaef32a727e17be1bb85d1eafcfc106f7ec8.png?name=ougWX83hMAFXBg.png

2026-07-23 23:17:25 UTC

My bias is that I am in fact politically blackpilled.

2026-07-18 03:54:53 UTC

@npub1jqq…pern ai: what is it good for, I can just imagine products in my mind

2026-07-17 11:07:47 UTC

- reply

@npub16mx…yz4h @npub14vd…jhav depending on the mrf its possibly easier to just do it by hand

2026-07-17 10:57:46 UTC

- reply

@npub14vd…jhav my current thing is I am adding "miniapps" to Fediverse. I will need people to implement their own so it's just not me making them lol. I will provide some base project templates in the near future.
they only work on two servers, one being SPW, right now, but they will be upstreamed to Pleroma when done

2026-07-17 10:54:45 UTC

- reply

@npub14vd…jhav bluesky uses it

2026-07-17 10:50:36 UTC

@npub14vd…jhav json-ld for us is a massive failure and nobody will be able to ever do what is claimed is possible with it. I wish we could switch to closer to what atproto does

2026-07-15 08:34:27 UTC

Praise God she is well and there was no more cancer

2026-07-08 23:35:37 UTC

- reply

check out this word salad, this is a great argument against LLMs, it will do anything you ask and convince you it knows what it is doing. It's basically a super-Indian contractor.
> speculate on what problems this would be "good at" solving compared to conventional systems
The honest framing: HIVE-VM inherits the strengths of the systolic-array/cellular-automaton family, so its sweet spot is problems that are local, uniform, and streaming — where conventional CPUs waste most of their effort on memory indirection and control flow that the lattice simply doesn't have.
Physical simulation with local interactions. Lattice-Boltzmann fluids, wave propagation, diffusion, heat. These are already solved by discretizing space into a grid where each site updates from neighbors — which is exactly what HIVE-VM is. On a CPU the bottleneck is memory bandwidth and cache behavior; on the FPGA target every cell updates in parallel every tick with zero fetch cost. A 12³ lattice at 50 MHz outruns a CPU doing the same stencil by a wide margin. For games specifically: falling-sand mechanics, Noita-style pixel physics, fluid/gas in a voxel world. The simulation isn't running on the machine — it is the machine.
Fixed-latency stream processing. Because the global tick is synchronous, latency through any lattice is exactly its path length in cells — data-independent, cycle-exact, jitter-free. That's a poor fit for general software and a perfect fit for hard real-time signal paths. The closest thing to your own bench: a scanline-rate video effects processor. Analog video is a relentless synchronous stream with no tolerance for buffering hiccups — precisely the regime where a strand-and-junction pipeline is natural and a CPU is fighting its own scheduler. A HIVE lattice doing per-pixel operations at pixel-clock rate is TBC-adjacent territory, in the same design space your FA-370 lives in.
Convolution and morphological operations. FIR filters, stencil kernels, erosion/dilation on images and voxel volumes. Systolic arrays were invented for this in the 1980s; the E2 encoding makes volumes lattice-native so the data format and the compute substrate coincide.
Timing-side-channel-resistant primitives. Constant-time execution is a property you normally have to fight compilers and microarchitecture to get. Here it's structural: every program takes exactly its geometric depth in ticks regardless of data. Bit-permutation-heavy stream ciphers and LFSR-style generators map directly onto strand delay lines, and CA-based RNGs (the Rule 30 lineage) are established prior art.
Reservoir computing. Genuinely speculative but real: CA reservoirs (ReCA) use cellular automaton dynamics as the fixed random projection in reservoir computing, with only a cheap linear readout trained. A HIVE lattice with inlets as input channels and outlet taps as readout features is a ready-made ReCA substrate, and the §7.3 synthesis angle (evolving lattice geometry against a fitness oracle) is exactly how reservoir topologies get tuned.
Fault-tolerant pipelines. Majority voting is a native gate, spatial redundancy is free geometry, and the j-bit gives per-cell integrity. Triple-modular-redundant signal paths are just three parallel strands into a majority junction.
What unifies these: no pointers, no branches, no shared global state, dataflow determined by geometry. The moment a problem needs random access, data-dependent control flow, or floating point, HIVE loses to a conventional core by orders of magnitude and there is no clever encoding that changes that. The realistic pitch is "a portable program format for the class of problems FPGAs were already winning" — which is a smaller claim than Universal Coding, but a true one.

2026-07-08 23:33:46 UTC

- reply

I have an actual spec document now, and am working on how to implement it in fpga

2026-07-08 23:26:37 UTC

- reply

I just gave his idea to Claude Fable and told it "even if it is crazy and improbable and a bad idea, come up with a design" this is actually a really fun and entertaining use of AI

2026-07-07 05:07:22 UTC

- reply

@npub1duq…kkua @npub1ez6…gqg5 @npub1a4f…rseh I made a promise I wouldn't police a whole bunch of stuff here, so I am considering making a more moderated server as a secondary project.

2026-07-04 05:29:16 UTC

blowing my balls smoove off