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/
Created my first AUR packages! It was cool to learn in more detail about how Arch does package management.
https://aur.archlinux.org/packages/impostor-server-bin/
https://aur.archlinux.org/packages/impostor-server/
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
Just found @godotengine browsing the top #AUR packages. I have no game dev experience but it looks cool and I kinda want to try π
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
Reminder that git is incredibly simple if you learn it from the inside out instead of the outside in
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.
Software, music, hobbyist mapper, uh... probably more stuff?