sallt @sallt@social.linux.pizza

im so tired of people in the foss community talking about how important freedom is, yet they are using gab or promoting other far-right bullshit. thats the opposite of freedom. we have to fight for every persons right to be free. until then, there is no such thing. if your in to that kind of bullshit, please unfollow me and tell me so I can do the same!

Mailing lists are resistant to censorship

https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prevent-censorship/

I tried #bashtop, It looks really cool! And it also shows much more information. But also it consumes a lot more CPU.

Like according to #htop it consumes like 17% of my CPU while htop consumes 0.7%.

Stop making websites that look good in Chrom* and shit everywhere else.

Microsoft is about to shut off its ebook DRM servers: "The books will stop working" https://boingboing.net/2019/06/28/jun-17-2004.html

Have you donated to #peertube yet?

https://joinpeertube.org/roadmap

Today, my son started to show real interest in computers and operating systems. I briefly explained how a computer works and that you can run any OS you want on it.
Also explained what Windows was, and he promptly said:
"But I like using Linux, it is better",
I asked him why, and he said:

"I like the penguin"

@lethalbit a good open source binary reverse engineering platform would be great

An object can be a blob, tree, commit, or tag. An object is identified by its ID, which is a SHA.

A blob is just some arbitrary data. Files are represented as blobs.

Trees are a list of blob IDs and other tree IDs, and their names. Directories are represented as trees.

A commit has a tree ID, an author, a date, a parent commit ID (or IDs, for a merge commit), and a commit message.

A reference is just a commit ID. Branches are a kind of reference. The only information which is stored to represent "master" is the ID of the latest commit. To get the commit log, you just follow the parent ID in each commit. To get the contents, you look at the tree ID of that commit. To update master, create a new commit and write its ID to .git/refs/heads/master (which is a plaintext file).

A tag has a commit ID, an author, and a message. It just calls out a specific commit as special, like a release number, and adds a message, such as that version's changelog.

All git commands are just a means of manipulating what is ultimately a very simple data store. If you want to know more about how a specific command works and how it relates to this data store, let me know.

I think I'll be clear about this: I am not anti-Mozilla.

(Though putting Pocket in their addressbar rather than an RSS/Atom subscribe button does go against my design principles for encouraging a more decentralized web)

I think they are a positive influence, but they have too much influence to loose to be as radical as they pretend to be.

At the same time we do need a truly radical browser engine to help get us out of the sad software development we're in. I hope to be that!

Stop Bad Laws Before They Start

Right now, there’s a proposal to essentially prevent you from flashing your own firmware/software to any product with a radio in it before the European Commission. This obviously matters to Europeans, but because manufacturers often build hardware to the strictest global requirements, it may impact everyone. What counts as radio equipment? Everything from WiFi routers to wearables, #SDR dongles to shortwave #radio.

https://hackaday.com/2020/07/25/stop-bad-laws-before-they-start/

In ecology, biodiversity is an important measure of ecosystem health.

Maybe we need to appreciate software, interface and network diversity as similar indicators of the health of our digital culture.