For emacs itself, since I compile #emacs from master once a week, I always keep the last version that did not have any problem. I build from git in ~/local/src/emacs and run this version; but make install in /usr/local/ if the current version has not had any issue.
For my config: every change is committed into a git repo, so I can always get back to a previous stable version.
I have been using this workflow for years now without any major frustration. And I really depend on #emacs since it is my window manager, mail reader, word processor, organizer, agenda, chat client, file manager, etc.
@redfrog@Khrys Est-ce que Attac a une présence active sur Mastodon? La dernière fois que j’ai regardé, le site d’Attac de ma région n’avait été mis à jour depuis 2 ans et leur seule présence en ligne était Facebook. Je dois avouer ma déception et me demande comment peut-on lutter contre les multinationales et baser sa communication sur les GAFAM …
@drewdevault Impressive. Just a dumb question. If you don't have networking or USB working yet, how did you get the markdown file from the laptop to your blog?
#Microsoft seems to have lost a key that gives attackers access to basically ALL Microsoft #cloud services including "Login with Microsoft".
In other words: it looks like anything from Microsoft clouds including 3rd-party authentication is compromised. And they won't set up their systems from scratch as you'd normally do after a hack.
@publicvoit Do you have a link with more information about this issue?
,----
| #Microsoft seems to have lost a key that gives attackers access to basically ALL Microsoft #cloud services including
| "Login with Microsoft".
|
| In other words: it looks like anything from Microsoft clouds including 3rd-party authentication is compromised. And they
| won't set up their systems from scratch as you'd normally do after a hack.
|
| This & more updated on my "You Can't Control Your Data in the Cloud" article on https://karl-voit.at/cloud/
`----