Parman - Activate OP_GFY now!!

I spent the last 3 days intensely thinking to create something new for computer security, making ParmanodL computers safer, but applicable to others who would want to copy. It involved... 1) Aggressive whiteboard doodling with frizzy hair 2) Long battles with retarded AI to test and probe 3)5 hr insominia mind's eye designing 4) Code testing It's a way to solve the injection problem when making software patches that require restricted access. Normally you'd need to physically enter the sudo password to permit (a deal breaker for web GUI), and if triggering the patch remotely, it's dangerous to send the sudo pass via a browser, or have the browser trigger scripts run by root. It's solved with a restricted bucket directory, a sudoers.d-preapproved patch-running script, that enforces pgp signature checks before moving git pull patche files to the restricted area for running. This way, parman-approved patch scripts can't be modified once they are in the restricted area, and beforehand if they are modified, The signature will be invalidated. This makes the script safe to execute with root privileges triggered by a remote browser, as nothing but parman-signed code can run. It's super niche, but new, so maybe I'll do a publication somewhere. Of course this is dependent on trusting Parmanode software in the first place, which you imply when entering your sudo password when requested. The modification means you don't have to keep doing it, and no extra risk is added. Similar to how you PGP check a wallet once when you install it, not every time you do a transaction. The wallet you are running can actually maliciously change after you've PGP-approved and installed it, but Parmanode restricted bucket files can't. This is one more reason to get a clean transaction computer at the very least, for bitcoin transactions - don't use your regular computer.

Most people don't have $400 available to buy bitcoin in an emergency.

It's a nice feeling knowing you can't get fucked in the arse because you bitcoin is in self custody.

Not buying bitcoin during these stupid crazy cheap prices is wrong and gay.

On Twitter, apparently it's supposed to be a tree, or two people holding hands. Here, it can only look like one thing...

When you order a node from Parman, you get tech support by Parman. And if you opt in at checkout (smol fee), you get a personal tour of the machine and software I made, over a video call. parman.org

Do you think Parmanode is looking pretty?

People no longer saying "bingo card" was not on my bingo card for 2025.

Sexy Bitcoin Station - Some people can't get enough 😘 This is ParmanodL, ParmAirGap and ParmaDrive.

If you have orange pill victims who need help with hardware wallet setup, and you can't do it yourself, or don't feel confident, you can order a BitBox02 from parman dot org, and select an add-on to get a discounted consultation from me to help set it up.

Blank canvas for Parmanode4 - some people want mouse action, so a browser interface is being added. The old-school terminal interaction will always be available; don't worry, everyone, calm down!

Parman's #nerdtips Do you want to know why a lot of base64 numbers (not all) end with = or ==? eg dGhlIHNhbXBsZSBub25jZQ== This might seem boring, but explaining it covers a lot of interesting things (also, I'm assuming you know what base64 is, but I will take requests to explain that another time). The = sign is not part of the character set (64 characters) of base64. It's used for padding at the end (for remainders), when the data to be encoded doesn't fit evenly in the byte-groups that will be used. It starts with understanding that base 64 encodes data with 6 bits at a time (00000000-00111111 in binary can hold the values 0 to 63 in decimal), and the smallest data communication unit in modern computers, a byte, has 8 bits (8 bits can hold 0 to 255, ie 256 different numbers). So instead of wasting two leading bits per byte, the lowest common multiple of 6 and 8 is used as a minimum "packet" for base64 storage - that common multiple is 24. So 3 bytes (24 bits) will correspond to four base64 characters. But, if the number of characters needed doesn't divide evenly, ie, there is a remainder, then the = sign indicates whether there is one or two entire unused bytes at the end. For example, let's say there is a large number (all data on a computer is a number) that requires 21 base64 characters to encode. That would use up 3 bytes for each 4 base64 characters (4 characters fit per 3 bytes), so 5 groups of 3 bytes (15 bytes) will be used for the first 20 characters. The last character will sit inside a 3-byte group on its own. The first byte of the three will have 6 bits with two unused bits, and then there are two entire unused bytes, so two ='s are added at the end of the base64 number. BUT WHY? Why not just print the base64 number and omit the = sign(s)? Because their purpose isn't for encoding the number - the purpose is for the time when the number is going to be decoded back to bytes. It is done in groups of 3 bytes, and without the = sign, the decoder won't know if there is a remainder or not, and the empty bytes will be interpreted as a zero instead of padding. https://armantheparman.com/nerdtips

You don't have to risk your life to resist tyranny - only your wealth. If you are afraid now, and selling Bitcoin to get some of your master's, money, shame on you. If you can't buy more Bitcoin when it's cheap, fine, not everyone has spare money, but you're doing the OPPOSITE?? - what the fuck are you doing?

Bitcoiner life tip, just my opinion, don't hate me for it... Don't be impatient for Bitcoin to win, and don't wait for your life to become good based on how Bitcoin performs. Appreciation for life can happen now, and hope for the future can remain intact. Making your life better can happen now in ways other than the ones you imagine you need extra wealth for. I'm not saying not to acknowledge the shit things, I'm saying there are always ways to improve the situation, and working towards that with a low time preference can be very satisfying too. Sign up to my non-existent newsletter for more tips.

Teachers - it's a privilege having the attention of young students and teaching them a class. DO NOT abuse that privilege by introducing your personal political beliefs.

The problem with arbitrary data tolerance is that it doesn't contribute to Bitcoin being money. It's like promoting the electrical conductivity of gold as a reason for it to be money. You might think that's not so bad but... The problem it causes, having arbitrary data, is subjectivity, and various attacks - it's easier to stand for none of it, and remain objectively supporting Bitcoin as money. You don't need to define what spam is - it's a subset of arbitrary data. You don't need to defend Bitcoin being a free speech platform (it's not), and explain why CSAM can't be blocked - it's a subset of arbitrary data. You don't need to care that not all arbitrary data can't be stopped - your principles are what guides you, and with the right principles, if people concur, consensus is easy to achieve. Right now, we're fractured, because people who don't want spam feel like they have to allow it because it's hard to define (and because shitcoiners and fiat maxis are disguising themselves as one of us, muddying the waters, looking at Lopp and others). I'm saying this is unnecessary. Just be against arbitrary data; it's not part of Bitcoin's purpose. If you desire extra "nice to have" features from arbitrary data, in addition to Bitcoin's pure monetary features, then you have to accept spam and CSAM, and unwanted additional attacks, and also damaging infighting.

All Parman.org products thus far have been ad/sponsorship free. But starting in 3 days, they will continue to be ad/sponsorship free.

People saying bingo card in 2025 was not on my bingo card

Smol announcement, I won't be making ParmanodL with Pi4's anymore. I have one left, and it's cheap. $350 USD (has 2Tb external SSD)