One of my all-time favorite guilty pleasures is indulging in productivity porn.
Nun möchte ich zeigen, wie mit dem Raspberry Pi automatisch E-Mails verschickt werden können. Damit kann der Raspberry Pi z. B. automatisch eine Nachricht absetzen, wenn sich der Zustand eines I/O geändert hat.
As Emacs user I always want to use Emacs interface to edit documents. When I write e-mails, I also do, so I tried to introduce notmuch, emacs and offlineimap. As a result I feel notmuch on emacs is very useful in terms of tagging, searching, and emacs interface.
Some configurations below were not on the web, so I note here. If you follow my way to handle e-mails, this may help you.
I have tried to get my mail in the traditional Unix way, with an MTA, MDA, MRA, MUA, all that stuff. It was a huge pain. With some more modern programs, though, I can have a setup that still follows the Unix philosophy of single-purpose programs working together, while being a lot easier to understand.
There are four main programs in my setup:
- offlineimap: fetch mail from servers
- notmuch: index and search local mail
- alot: read indexed mail
- msmtp: send mail to servers
My current setup involves four major componenets. Offlineimap to fetch email, notmuch to index email, Astroid to view/search/read/write emails and msmtp to send emails.
When I first started trying to understand the memory allocator of Go, it was maddening. Everything seemed like a mystical black box. As almost every technical wizardry is hidden beneath abstractions, you need to peel off those layers one by one to understand it.
Simple Einrichtung, stabile Tunnel: WireGuard bringt einige Vorzüge mit sich. Wir zeigen, wie leicht es sich unter Windows, Linux und Android aufsetzen lässt.
Der Mac ist logischer, komfortabler, benötigt weniger Wartung und bietet das Beste aus beiden Welten – das sind nur einige der Argumente für den Wechsel. Mac & i zeigt auch, wie sich Windows-Umsteiger in macOS schnell zurechtfinden.
Parallel multicore programming should be easier than it is. What makes it such a struggle? Most programming languages were designed without parallel programming in mind. Attempts to add on parallel programming features, or parallel libraries, are doomed to a struggle against the impediments built into the original languages.
The distributed, multicore train is stopping for no programmer, and especially the systems programmer will need to be ready to hop on to the distributed parallel programming paradigm to keep their systems running as efficiently as possible on the latest hardware environments. There are three new systems programming languages that have appeared in the last few years which are attempting to provide a safe, productive, and efficient parallel programming capability. Go is a new language from Google, Rust is a new language from Mozilla, and ParaSail is a new language from AdaCore.
Pia Klemp hat mehr als 1000 Menschen vor dem Ertrinken gerettet. In Italien wird nun gegen sie wegen Verdachts auf Beihilfe zu illegaler Einwanderung ermittelt.
When it came time to implement 2FA in my open-source project Mentat, I wanted to try something a little different. As an end-to-end encrypted chat app, asymmetric encryption was already an important aspect of the platform, and was easy enough to implement using OpenPGP.js. When a user signs up for the platform, a keypair is generated and the public key is saved in the database as part of that user's identity. But an issue arises when the user wants to sign into a different device: how can the user's private key be transmitted in a way that doesn't reveal their credentials to the server? As it turns out, I was able to solve this issue and add a second authentication factor in the same step.
Just hearing the word CMake is typically enough to make a shiver run down my spine.
I don't mind letting your programs see my private data as long as I get something useful in exchange. But that's not what happens.