Notices by MacLemon (maclemon@chaos.social)

Autoposts from the birdsite are problematic and may even violate your home instance's guidelines.

- short/tracking URLs
- usernames not/existing in both universes or who are different persons cause confusion
- RTs clutter local/federated timelines
- responses aren't read preventing discussion

- no use of
- content warnings (CWs) for peace of mind
- image descriptions for accessibility
- public/unlisted/followers/direct addressing

Thanks

OH: *hach*
Alte Fotos?
Alte Browsertabs!

Some people asked about my #oneWeekOneTool efforts in learning more about #tmux(1).
Yes, I now have published my ~/.tmux.conf file.

https://github.com/MacLemon/dotfiles/tree/master/tmux

Caveat emptor: It's made for the current tmux(1) 2.7. It works fine with nested sessions the way _I_ like it and works on macOS and FreeBSD. (Haven't tested any other OS since I don't use anything else where this comes into play.)

README.md is prominently missing. I'll add one when I find the time.

@henryk I totally agree. Having a public ledger of all the password history, even if encrypted, puts up a great level of attack surface, IMHO. I mean, how good do you expect the passwords that protect that thing to be statistically?
I can just clone the repo and start attacking it offline with as many CPUs I'm willing to afford.
Keeping the same info in an offline repo allows for versioning likewise and keeps the attack surface lower. I wouldn't risk it.
@flowfx

@flowfx Conveniently disregards the fact that you must change all passwords after changing access. Since the credentials stored in git include all their history and you could just go back to a commit where you still had access.
Now you have a password management problem, a git problem, a key distribution problem without meaningful revocation mechanism, and a GPG problem, including a denial of service attack vector for pull requests by changing passwords though a commit.

Just keep it separate.

Wer schon neulich an der EU Umfrage zur Uhrenumstellung teilnehmen wollte: Der Server scheint momentan brav zu funktionieren.

Die Fragen sind, meiner persönlichen Eineschätzung nach, sehr sinnvoll gestaltet inkl. der Antwortmöglichkeiten. (Multiple Choice UND Freitext Felder.)

Dauert keine 3 Minuten.
https://ec.europa.eu/eusurvey/runner/2018-summertime-arrangements

Los, tut was für unser aller Gesundheit! Permanente Sommerzeit FTW!