spv.sh
spv.sh
living foss

hope i don’t get crucified for self promotion, stigmata would be hard to explain to my folks

  • SayCyberOnceMore@feddit.ukEnglish
    2·
    7 hours ago

    ~1600 hours uptime… no rebooting after patching?

    You… you do patch your web server… don’t you…?

    But, a good blog… must give my BIOSes a good looking at and see if I can change some of mine

    • spv.sh@lemmy.spv.shOPEnglish
      1·
      1 hour ago

      of course! probably not as frequently as i should. i oughta do a patch-job sometime tho…

  • Luke@lemmy.mlEnglish
    7·
    15 hours ago

    Your website is refreshingly simple and also manages to be unique looking. I like it!

    • MonkderVierte@lemmy.zip
      1·
      3 hours ago

      I don’t. Please make the header and footer smaller or non-floating on mobile. And padding of the text is too wide too.

      And on desktop, * {…} rules are not good behavior. Firefox complains about quirks mode too.

      Edit: this is about the website, the tech, not your blog. Didn’t got to read that yet.

  • BalakeKarbon@lemmy.ml
    121·
    17 hours ago

    Does this even count? Not even running on an open core written to FPGA using Foss tooling 😉

    Just wanted to say my experience running a Librem 5 was amazing until I realized my social groups are religiously against texting or using anything besides Snapchat.

    Also ran a PPP for a while but it seemed harder to stabilize for me at the time.

    Been running FOSS everything else except for some firmware, bios, microcode, silicon, etc for many years now with no complaints. Sometimes I purposely chose hardware that is supported though so I suppose I have tailored my experience.

    • spv.sh@lemmy.spv.shOPEnglish
      6·
      17 hours ago

      i tried to build a risc-v smartphone but the ox64 is a pita and i gave up, lol using an ARM core for that project now (once i get my damned shipment)

      • BalakeKarbon@lemmy.ml
        3·
        16 hours ago

        I have an orange-crab running Linux right now for an entirely auditable system up to that point and something reasonable secure but yeah I have not made the time to crank out some software/drivers for a screen, keyboard, and Internet.

        I have a clockworkpi uConsole with the R-01 RiscV board and a cellular modem that works great but again we’re back to square 1 since I couldn’t find much auditing done on the chip and I have not personally opened up any of mine. Although if my memory serves me right the sister core (XuanTie C910) had some holes in it so I guess it’s good someone looked at part of the family at least and published it. Also if I’m not mistaken the modem has an Arm in it running who knows what too like any other modem. The only auditable modem firmware I know of is the one for the pinephones.

        Within the rabbit hole, I think I’d trust anything between:

        • My own, or some other people’s, discrete transistors or vacuum tubes and diodes.
        • Most hardware made before ~1985 Ofc, running entirely FOSS.

        Idk what the upper limit is though I’d like to know.

        • spv.sh@lemmy.spv.shOPEnglish
          4·
          15 hours ago

          fellow u-console owner! i have the a-06. the modem is shite, in my experience. i can’t say for sure but i’d guess it’s arm. the pinephone (pro) uses the eg25-g (as i discuss in the article), which runs an android bootloader, older linux kernel, and generic gnu(?) userland. the bootloader, kernel, and userland are all FOSS (well, they can be flashed to be, anyway). the ADSP (the code that directly interfaces with the radios) is proprietary, for practical and regulatory reasons. this doesn’t really effect my threat model, as i assume that anything a sophisticated attacker could glean from an ADSP backdoor they could much more easily glean through the radio traffic itself. the TZ (arm trustzone) firmware is also proprietary, for technical reasons. iirc it’s signed by ARM, but this is just off the top of my head, so don’t quote me! or do, i’m not your dad…