𞋴𝛂𝛋𝛆

  • 120 Posts
  • 1.05K Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle
  • Complex social hierarchy is a super important aspect to account for too. In the proprietary software realm, you infer confidence in the accumulated wealth hierarchy. In FOSS the hierarchy is not wealth, but reputation like in academia or the film industry. If some company in Oman makes some really great proprietary app, are you going to build your European startup over top of it? Likewise, if in FOSS someone with no reputation makes some killer app, the first question to ask is whether this is going to anchor or support a stellar reputation. Maybe they are just showing off skills to land a job. If that is the case, they are just like startups that are only looking to get bought up quickly by some bigger fish. We are all conditioned to think in terms of horded wealth as the only form of hierarchy, but that is primitive. If all the wealth was gone, humans are still fundamentally complex social animals, and will always establish a complex hierarchy. This is one of the spaces where it is different.


  • It is democratic. You have a right to all information, the right to error, the right to skepticism, and the right to protest in all nonviolent forms aka the right to offend others.

    In this regime of rights, the right to skepticism is the fundamental. You have a right to think for yourself. Authoritarianism is the opposite. Trust is its fulcrum and individual thought, belief, and access to information are not rights of individuals.

    You cannot have democracy and citizens without outlets of free expression of all types. There is no way to know if some group is in collusion or spreading misinformation for various purposes. Having the right to anonymously express and check concerns in the public commons is absolutely critical to democracy. Any attempt to remove it is an attack on skepticism, the fundamental cornerstone of democracy that if removed causes total collapse.





  • The main problem is when following instructions for command line tools. They might figure out how to use dnf instead of apt, but the extra layers required for ostree are not very friendly. There are a ton of potential frustrations in this area, especially with GPU stuff or hobbyist hardware like Arduino where kernel stuff is needed in userland. At least as of nearly 3 years ago, the documentation in this area sucks. I was on Silverblue for a few years and managed to get through the frustrations due to intermediate experience level. I found toolbox useless compared to distrobox. But using this with something like Arduino was annoying at best. The needed dependencies expected by whatever stuff I wanted to install was usually a big mystery with near useless error failure messages and names of packages and libraries totally unrelated to the package naming in DNF. When updating the base OS, stuff built in these containers is totally useless because I could not update the containers to the new OS image. Playing around with Flash Forth on a microcontroller was even worse. I ended up layering a bunch of stuff on the host because the containers were just not working. When I got an Nvidia machine, I went to Fedora Workstation and have had far fewer issues and frustrations. SB wasn’t bad, but it is a pain to use these if you need kernel level access. Just my $0.02. I was actually on SB for ~2-3 years.





  • Becoming a roadie and riding a bike everywhere for years fixed me feeling like this. I had to get over all of my insecurities being in public in a cycling kit. Being around other people riding and racing, it became my normal. Now… I don’t have to look at me, so why the fuck should I care what anyone thinks. They are used to it or whatever, who cares. I’m more interested in inferring their real intelligence versus narcissistic stupidity based on their responses. Old people are all ugly. “For your age” is just an excuse for it. The vanity is boring. People who are judgmental are just projecting their own inadequacy and internal misery.


  • Chemistry, math, physics, optics, metallurgy… The thing that is hard is how your needs for knowledge will change over time and what is accessible to you at each stage.

    For general electronics, The Art of Electronics is the goto book. For actually understanding practical stuff, you need to build a knowledge of the industrial revolution and how it evolved. The inventions of James Watt opened up steam. The Bessemer process scaled iron. Large heavy castings drove the potential for large lathes, but lathes are the key to everything. A lathe is capable of cutting a more precise screw than the one used to operate it. That old screw can be replaced with the new, until you achieve your desired precision.

    A reference flat is made using two granite stones rubbed together with water in between until the top one creates suction that can lift the other.

    Prussian blue and hand scraping are used to make machine flat surfaces.

    Automotive suspension components like springs and torsion bars are a good source of cheap tool steel. Engine heads are a good source of casting scrap and quality hardware. Wipers, window motors, and starters are great for building machines. Understanding how to repair and diagnose this stuff is a major skill. Knowing how to make real controlled heat is fundamentally important.

    I’ve never encountered single sources for this stuff.


  • llama.cpp is at the core of almost all offline, open weights models. The server it creates is Open AI API compatible. Oobabooga Textgen WebUI is more user GUI oriented but based on llama.cpp. Oobabooga has the setup for loading models with a split workload between the CPU and GPU which makes larger gguf quantized models possible to run. Llama.cpp, has this feature, Oobabooga implements it. The model loading settings and softmax sampling settings take some trial and error to dial in well. It helps if you have a way of monitoring GPU memory usage in real time. Like I use a script that appends my terminal window title bar with GPU memory usage until inference time.

    Ollama is another common project people use for offline open weights models, and it also runs on top of llama.cpp. It is a lot easier to get started in some instances and several projects use Ollama as a baseline for “Hello World!” type stuff. It has pretty good model loading and softmax settings without any fuss, but it does this at the expense of only running on GPU or CPU but never both in a split workload. This may seem great at first, but if you never experience running much larger quantized models in the 30B-140B range, you are unlikely to have success or a positive experience overall. The much smaller models in the 4B-14B range are all that are likely to run fast enough on your hardware AND completely load in your GPU memory if you only have 8GB-24GB. Most of the newer models are actually Mixture of Experts architectures. This means it is like loading ~7 models initially, but then only inferencing two of them at any one time. All you need is the system memory or the Deepspeed package (uses disk drive for excess space required) to load these larger models. Larger quantized models are much much smarter and more capable. You also need llama.cpp if you want to use function calling for agentic behaviors. Look into the agentic API and pull history in this area of llama.cpp before selecting what models to test in depth.

    Huggingface is the goto website for sharing and sourcing models. That is heavily integrated with GitHub, so it is probably as toxic long term, but I do not know of a real FOSS alternative for that one. Hosting models is massive I/O for a server.





  • No. The primary way of blocking radio is by raising the noise floor across the band. The type of radio is irrelevant. The protocol is irrelevant. It is all only the electromagnetic spectrum from infrared light, to visible spectrum light, to radio light, through to xray or gamma ray light. How we divide that up into protocols, bands, and names is totally irrelevant. When transmitting radio light, we are all restricted in how much power we are allowed to send. All receiver circuits are listening for meaningful information above the noise floor. Bands are allocated to try to create spaces for certain types of communications. This controls the noise floor. Then electrical engineers design the hardware you buy to operate within this specification. If that noise floor is raised, the physical hardware is unable to retrieve information and effectively makes it useless. If you are a radio wizard and build your own transmitter that has more power, you just created a giant beacon that anyone will track easily to your location. Transmitting always reveals your exact location. In military operations, you constantly hear about some entity going radio silent. This is why. If you are a soldier, you may not carry a cell phone at all when on the job because it is constantly revealing your location. The only way to avoid this is with actually hard wire connections. You are able to use lasers for line of sight communications, but in practice, you will be limited by the optical lens focusing complexity and atmospheric distortion even from the ground with point to point regional communication. If anyone crosses the beam it will still be detected and is likely to leak some light depending on conditions and design.

    Ultimately, your only real option is the sneaker net which is damn near useless in US suburbia hell. Don’t forget that the freeway system was not created for the citizenry. It is only about military mobility. That is why the Germans made the autobahn and why the USA and others had to copy the idea. Your only defense is in the democratic political space.




  • Just be aware that W11 is secure boot only.

    There is a lot of ambiguous nonsense about this subject by people that lack a fundamental understanding of secure boot. Secure Boot, is not supported by Linux at all. It is part of systems distros build outside of the kernel. These are different for various distros. Fedora does it best IMO, but Ubuntu has an advanced system too. Gentoo has tutorial information about how to setup the system properly yourself.

    The US government also has a handy PDF about setting up secure boot properly. This subject is somewhat complicated by the fact the UEFI bootloader graphical interface standard is only a reference implementation, with no guarantee that it is fully implemented, (especially the case in consumer grade hardware). Last I checked, Gentoo has the only tutorial guide about how to use an application called Keytool to boot directly into the UEFI system, bypassing the GUI implemented on your hardware, and where you are able to set your own keys manually.

    If you choose to try this, some guides will suggest using a better encryption key than the default. The worst that can happen is that the new keys will get rejected and a default will be refreshed. It may seem like your system does not support custom keys. Be sure to try again with the default for UEFI in your bootloader GUI implementation. If it still does not work, you must use Keytool.

    The TPM module is a small physical hardware chip. Inside there is a register that has a secret hardware encryption key hard coded. This secret key is never accessible in software. Instead, this key is used to encrypt new keys, and hash against those keys to verify that whatever software package is untampered with, and to decrypt information outside of the rest of the system using Direct Memory Access (DMA), as in DRAM/system memory. This effectively means some piece of software is able to create secure connections to the outside world using encrypted communications that cannot be read by anything else running on your system.

    As a more tangible example, Google Pixel phones are the only ones with a TPM chip. This TPM chip is how and why Graphene OS exists. They leverage the TPM chip to encrypt the device operating system that can be verified, and they create the secure encrypted communication path to manage Over The Air software updates automatically.

    There are multiple Keys in your UEFI bootloader on your computer. The main key is by the hardware manufacturer. Anyone with this key is able to change all software from UEFI down in your device. These occasionally get leaked or compromised too, and often the issue is never resolved. It is up to you to monitor and update… - as insane as it sounds.

    The next level key below, is the package key for an operating system. It cannot alter UEFI software, but does control anything that boots after. This is typically where the Microsoft key is the default. It means they effectively control what operating system boots. Microsoft has issued what are called shim keys to Ubuntu and Fedora. Last I heard, these keys expired in October 2025 and had to be refreshed or may not have been reissued by M$. This shim was like a pass for these two distros to work under the M$ PKey. In other words, vanilla Ubuntu and Fedora Workstation could just work with Secure Boot enabled.

    All issues in this space have nothing to do with where you put the operating systems on your drives. Stating nonsense about dual booting a partition is the stupid ambiguous misinformation that causes all of the problems. It is irrelevant where the operating systems are placed. Your specific bootloader implementation may be optimised to boot faster by jumping into the first one it finds. That is not the correct way for secure boot to work. It is supposed to check for any bootable code and deplete anything without a signed encryption key. People that do not understand this system, are playing a game of Russian Roulette. There one drive may get registered first in UEFI 99% of the time due to physical hardware PCB design and layout. That one time some random power quality issue shows up due to a power transient or whatnot, suddenly their OS boot entry is deleted.

    The main key, and package keys are the encryption key owners of your hardware. People can literally use these to log into your machine if they have access to these keys. They can install or remove software from this interface. You have the right to take ownership of your machine by setting these yourself. You can set the main key, then you can use the Microsoft system online to get a new package key to run W10 w/SB or W11. You can sign any distro or other bootable code with your main key. Other than the issue of one of the default keys from the manufacturer or Microsoft getting compromised, I think the only vulnerabilities that secure boot protects against are physical access based attacks in terms of 3rd party issues. The system places a lot of trust in the manufacturer and Microsoft, and they are the owners of the hardware that are able to lock you out of, surveil, or theoretically exploit you with stalkerware. In practice, these connections are still using DNS on your network. If you have not disabled or blocked ECH like cloudflare-ech.com, I believe it is possible for a server to make an ECH connection and then create a side channel connection that would not show up on your network at all. Theoretically, I believe Microsoft could use their PKey on your hardware to connect to your hardware through ECH after your machine connects to any of their infrastructure.

    Then the TMP chip becomes insidious and has the potential to create a surveillance state, as it can be used to further encrypt communications. The underlying hardware in all modern computers has another secret operating system too, so it does not need to cross your machine. For Intel, this system is call the Management Engine. In AMD it is the Platform Security Processor. In ARM it is called TrustZone.

    Anyways, all of that is why it is why the Linux kernel does not directly support secure boot, the broader machinery, and the abstracted broader implications of why it matters.

    I have a dual boot w11 partition on the same drive with secure boot and have had this for the last 2 years without ever having an issue. It is practically required to do this if you want to run CUDA stuff. I recommend owning your own hardware whenever possible.