Show newer

RT @DThompsonDev
TIL that one in every 10 adults in the U.S. believe that HTML is a sexually transmitted disease.

RT @melpa_emacs
The consult-notmuch package has been updated to version 20220421.346. melpa.org/#/consult-notmuch

@Parienve @turak
Wow. Motherload of the ideas I've been looking for! Let me see if I understand the workflow right:

1. create Pass location, in which
2. every file represents one password
3. git-control the whole location, so eg /Pass/.git

Is it a decision of tomb vs git? The tomb bit is the one I'm having a harder time piece together. Tomb encrypts entire directories, right?

@Parienve @turak passtomb and passwordstore were both new to me. Thanks for the references!

Check out this Meetup: Clojure Web Development Evolved (by Dmitri Sotnikov & Nik Peric) meetup.com/London-Clojurians/e via @Meetup

@turak Totally agree about not including sensitive information in code repos. These would be private (re: not even Github/lab) repos. But I have essentially avoided git for these files because it simply doesn't work. Is there any kind of internal solution that would maintain public encryption, but allow git-like reviewable synchronization of encrypted files?

I would like to use git to back-up, vc, and sync everything crucial on my text-based system, but some content, most notably my passwords file, are gpg encypted. This breaks git because reviewing changes essentially produces comparisons of gibberish. Does anyone know a solution for syncing/VC of encrypted data, which won't be only passwords?

jamesshore.com/v2/blog/2005/mi Nice old article on Microsoft getting TDD wrong in ways that many others have mistaken, too. Essentially, they suggested "waterfall-style TDD" which is a contradiction of terms. is meant to be fast and iterative. It is an absolute joy in Cider (and presumably other toolings and languages), where you re-run the failing test with every re-evaluation, watching for that joyful green light to say that now you've passed. jamesshore.com/v2/blog/2005/mi

@skyblond so detached heads should be thought of as "read only", where other branches are ready to be changed and pushed?

Check out this Meetup: The Secret Art of Storytelling in Programming (by Yehonathan Sharvit) meetup.com/London-Clojurians/e via @Meetup

@skyblond but why not just make it an ordinary branch? Why headless?

Why does have a detached head state? This seems like nothing but a "gotcha" to make you frantically search for lost code when you thought you were working on someone else's branch.

@Sphinx EXWM on Linux. I sold Linux stability in exchange for power, and made myself vulnerable to things like this.

EXWM on Linux. I sold Linux stability in exchange for power, and made myself vulnerable to things like this.

@Sphinx no, it's a software thing. Basically, upgrading a component of my OS.

Ugh. It's Friday. I simultaneously have the lack of wisdom so entertained a vain hope that upgrading that crucial thing won't destroy my system, and lack of energy to debug why my system wouldn't start. Now I type knowing that if I reboot right now, my system won't come up.

RT @luksamuk
@Endless_WebDev Now that's something I wanted to see in a long time: Portuguese and Lisp together. 😁

RT @juxtpro
Come and Meet JUXT! 👋 We will be opening the doors to our virtual office to welcome you all soon - what a treat! 🐣 What questions do you have for us? Let us know in the comments below.

RT @shimst3r
Okay, this sounds like 2022 *is* the year for Mastodon on the desktop. 🥹 twitter.com/joinmastodon/statu

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.