💾 Archived View for sysnull.info › blog › 20220120.gmi captured on 2022-04-29 at 11:28:08. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-03-01)
-=-=-=-=-=-=-
2022-01-20
Got email up and running for a few weeks now. Honestly sort-of not too bad at the end of it but certianly takes quite some time to get it up and running at first. The setup includes: postfix (smtps), dovecot (imaps), postgrey + rspamd (spam filtering), OpenDKIM (DKIM), and postmarkapp.com (DMARC reporting service). Got 97% on internet.nl's email test, can't close that 3% without DANE unfortantly because namecheap's nameserver doesn't have TLSA. Good enough for now I guess, but certainly in a (near?) future, I'll get a nameserver with TLSA support to get DANE in.
The main reason why I want high security features parity is because I know modern email requires quite a high standard these days if you were to even want to send/receive emails from major providers and any random (but responsible) general providers. Proving that my emails are not spam (and vice-versa) and using the latest standards hopefully ensures less likely the email don't even get delivered to the sender.
I have read blog posts on both sides regarding email, either: "it's too hard to upkeep, emails getting rejected", to: "it's not that hard, make sure you keep up with security requirements and it'll be fine, etc...". It's way too early for me to say this or that about email, but regardless of the negatives about it, I still rather want to learn and actually have an email server running at least to get a gist of what running an email server be like. There's a good write up by J. B. Crawford at his blog: computer.rip subject on: diy mail, which generally gave a fairly good overview and advice on email from his perspective.
If you wanted to email me something (even a git patch for one of my project), it's in the home page.
computer.rip - 2021-12-26 diy mail
In a recent update for gemlog2feed, input/output are now done via UNIX pipes, which makes it more flexible to use with other programs. It actually seemlessly opens up a use case for me: getting gemini feed via Newsboat. Newsboat currently does not (or even will never) support the gemini protocol, however it does read local file feeds as usual. Combined with gmni and shell scripting, run the script once can be used to fetch gemini feeds into an atom xml file which can then be readable by Newsboat as usual. Within Newsboat, you can setup a gemini client like for example, AV-98 to open a feed's link. While this isn't the most ideal solution for combining Gemini and WWW/HTTPS RSS/Atom feeds, at least it's one way to have both types of contents in one feed reader. In some near/far future, I might bother to make an RSS/Atom feed reader with Gemini support and my way on implementing features to suit my needs but for now, this will do just fine.
Here's an example basic shell script to fetch Antenna and my site:
#!/bin/sh
gmi_feed() {
link=$1
name=$2
path=$3
gmni -j always "${link}" | gemlog2feed "${link}" "${name}" > "${path}"
echo "Fetched ${link}"
}
gmi_feed gemini://warmedal.se/~antenna/ "Antenna" "/home/user/Feeds/gemini/antenna.xml"
gmi_feed gemini://sysnull.info/blog/ "sysnull" "/home/user/Feeds/gemini/sysnull.xml"
tildegit.org - solderpunk/AV-98
Still on the topic of RSS/Atom feeds and newsboat, I recently devised a way for myself to read a feed's site content without needing to open up a full-fledge browser (like Firefox or Chrome/Chromium). If you know about the "reader view" in Firefox, then this is what rdrview is but just a CLI program that just generates some HTML to be read by another browser, like w3m. rdrview/reader view are a neat way on cutting off the unnecessary part of the webpage and just giving you the primary content to read, which in turns should make it a lot easier for more limited browsers like w3m, netsurf, or whatever browser/reader of your choice to read the content. Here's an example of how I use it:
rdrview -B "w3m -cols 80" "${link}" | less
Minor updates to gmi2html:
Nothing much here, although there's something I'm thinking that would see me working more on gmi2html in the near future. More on that at a later blog post when it comes.