Sipeed Lichee Pi 4A RISC-V SBC review and Debian demo. This is the first RISC-V computer I’ve tested that's provided a usable desktop computing experience right out of the box. End-user RISC-V is starting to arrive! :)

You can learn more about the Lichee Pi 4A on its web page here: https://sipeed.com/licheepi4a

And the board has excellent documentation here: https://wiki.sipeed.com/licheepi4a.html

Note that the hardware I used in this video was purchased from AliExpress: https://www.aliexpress.com/item/10050...

I have reviewed four previous RISC-V SBCs, including the StarFive VisionFive 2, which also (after some messing around) provides a good desktop experience:

• VisionFive 2: RISC-V Quad Core Low Co...

I also have an 2023 update on RISC-V developments here:

• RISC-V 2023 Update: From Embedded Com...

And my general introduction to RISC-V is here:

• Explaining RISC-V: An x86 & ARM Alter...

For additional ExplainingComputers videos and other content, you learn about becoming a channel member here:

/ @explainingcomputers

More videos on computing and related topics can be found at:

/ @explainingcomputers

You may also like my ExplainingTheFuture channel at:

/ @explainingthefuture

Chapters: 00:00 Introduction 00:45 Unboxing 03:33 Specifications 07:26 First Boot 10:37 Debian Demo 18:10 Another Milestone

grow!

!cypherpunk@infosec.pub

cyph3rPunk

!cypherpunk@infosec.pub

infosec.pub/c/cypherpunk

This collection of networks offers no end to end encryption. Anyone with administrator access to an Instance can read anything that travels through that Instance’s infrastructure – including direct messages. The level of risk correlates with the number of cross-Instance interactions between users. If users from different Instances communicate, an attacker need only compel one Instance to reveal the direct messages between all of the interacting accounts. The centralised equivalents – Twitter, Tumblr, etc – can cloak their users through governance and resources. In a peer-to-peer network without encryption, there’s no structure, no agreed-upon governance, and absolutely no protection. Compromising or compelling an Instance or its staff means that all of network traffic is laid bare to its assailant.

I’d love to have a discussion on this (now fairly old) article which IMO has yet to provoke the kind of much-needed action on this topic that we, as a community of cypherpunks, are capable of.