Laan Tungir's avatar
Laan Tungir
lt@laantungir.net
npub1rmz9...xv06
Artist, Scientist, Cypherpunk, Critical Rationalist, Nym. [domain] https://laantungir.net [ipv4] https://15.235.3.231 [ipv6] https://[2607:5300:203:bb5c:4a46:c3d3:1dc3:fbe8] [tor] http://kn2jam4kyz6s5wacyozo3do3d2zsvh4to45uh7xliulwdust6zjuvnad.onion [fips] http://npub1crpldvy49ef8z34wlacwujnfudy4nd7k96aqdx5wgn6ckztz7z8q9t59ud.fips [n-site] https://npub1rmz9gu6de0m0u4ysrn39crrud099ahvfgs6pvasl4hpjr5ud7yus54xv06.nsite.run
Laan Tungir's avatar
Laan Tungir 4 days ago
I've been holding off on writing my own browser, but I suppose it is time. image I mean, why not have 20 different projects in various stages of completion, instead of finishing one at a time? "They all work together" I say to myself. # sovereign_browser A Linux x86 web browser built in C99 on WebKitGTK, designed around **sovereign identity** instead of the traditional web's permissioned infrastructure. The thesis: the browser's security model (DNS/domains, TLS/CAs, same-origin policy, CORS, cookie sandboxing) is what forces you to rely on permissioned domains, certificate authorities, and centralized account systems. By deprecating that model and replacing it with **Nostr identity** and **FIPS mesh transport**, you get a browser that's more capable, not less safe — because trust moves to the layer where it belongs: your keys.
Laan Tungir's avatar
Laan Tungir 4 days ago
GM morning fellow creators and defenders of FOSS. Rise up, there is work to be done! image There is no reason we should have a soundtrack to our lives. I'm live now. View live event →
Laan Tungir's avatar
Laan Tungir 6 days ago
I came across the following picture, and started wondering "What was it like to program a UNIVAC 490, and what could the thing do? image Well through the magic of LLMs, I could easily find out. The following web page is a simulation we created of programming a UNIVAC 490.  [clearnet] [tor] http://kn2jam4kyz6s5wacyozo3do3d2zsvh4to45uh7xliulwdust6zjuvnad.onion/univac-490 [fips] http://npub1crpldvy49ef8z34wlacwujnfudy4nd7k96aqdx5wgn6ckztz7z8q9t59ud.fips/univac-490 There are 6 sample programs you can run and I have included the instruction set in the reference tab, if you wish to try coding the 490 yourself. The "Add two numbers" program should be queued up. It is a good one to step through and watch the registers to give you a general idea of what is going on. The "Calculate Pi" program is a good one to let run, because the page can simulate the actual speed that the UNIVAC 490 processed at and give you a feel for what this puppy had under the hood. Stay sovereign [Laan] ***************************** The UNIVAC 490 was a UNIVAC computer with 16K or 32K words of magnetic-core memory. The words had 30 bits and the cycle time was 4.8 microseconds. It was a commercial derivative of the instruction set that had been developed for the AN/USQ-17 by Seymour Cray for the United States Navy. This was the last machine that Cray designed before leaving UNIVAC to join the early Control Data Corporation. At least 47 of these machines were made (serial numbers run from 101 to 147). Six were installed at NASA and played important roles in Gemini and the Apollo missions. The U490 had complete control of most or all of the data readout screens in Houston Mission Control. The USAF had two installed, as did Lockheed. The instruction word format: f – Function code designator (6 bits) j – Branch condition designator (3 bits) k – Operand-interpretation designator (3 bits) b – Operand address modification designator (3 bits) y – Operand designator (15 bits) Numbers were represented in ones' complement. The machine provided the programmer with the following registers: Seven B-registers (Address modifying index registers) 15 bits each One A-register or accumulator 30 bits One Q-register and auxiliary arithmetic register 30 bits
Laan Tungir's avatar
Laan Tungir 1 week ago
If Switzerland still had private banking, I would have to root for them to win this game, but as it is I'm a free agent. image #worldcup