After I decided to give KOReader another try, I knew that I needed some way of getting news articles onto my Kobo. The methods that KOReader supports are RSS feeds, Send2Ebook, and Wallabag. I investigated each of these methods at least briefly.
I ruled out Send2Ebook because it involves the client app sending your documents to an FTP server, and I’m not willing to run an FTP server in the year 2019 CE.
Protein pancakes are kind of a trend now, and you can buy pre-made mixes. It makes sense, because pancakes are a comforting breakfast food, but people want to have more protein in their diet, and fewer carbohydrates. This is my own recipe for making them from scratch. It is not low carb, but it should be a complete protein, since it includes a legume and a grain. The secret ingredient is chickpea flour, which you can buy at an Indian grocery store, where it is sold as “besan” or “gram flour”.
Gray Area responded to my Kobo post, pointing out, among other things, that you can actually save settings application-wide in KOReader, and not only for a particular book. That motivated me to give it another try, mainly for the sake of better font rendering, and hypenation (the lack of hyphenation in Nickel drives me batty).
So far, so good. I’ve got the defaults the way I want them now.
I mitigated the issue of Calibre making it hard to browse books in KOReader by configuring Calibre to not use subdirectories when sending books to the Kobo.
This is a recipe that’s actually 100% my own, though there’s nothing very original or creative about it. This is a soup that is optimized for being easy and fast to make, while still being filling and having a reasonable amount of protein.
Ingredients 2 Tbs vegetable oil 1 large sweet onion, diced 2 carrots, quartered lengthwise and diced 8 cups vegetable stock (I use Not-Chick’n Bouillon Cubes). 3 cans different canned beans (e.
Finished upgrading all of the computers in my home from Fedora 30 to Fedora 31 over the long weekend. It was pretty uneventful!
My own laptop went smoothly, though slowly, because it has a mechanical hard drive. All of the packaged software upgraded correctly and with no intervention, including the stuff installed from RPMFusion. I had quite a bit of self-compiled stuff, mostly relating to sway, and some of that had to be re-linked.
This little note is both a continuation of my ROOPHLOCH post, and a response to a pair of phlog entries: Ode to my Ebook Reader from Lambda Lab, and Bubbles and Baubles from Gray Area. Note: these are both on gopher; if your web browser does not support gopher, install the Overbite extension (Firefox or Chrome) or go to the Floodgap Gopher proxy and paste the URLs.
Like both phloggers, I have a Kobo e-reader.
I’m writing this blog outdoors, in accordance with the rules of Solderpunk’s ROOPHLOCH challenge. I’m also offline… there’s no Wifi here, and I have tethering turned off for my phone; I’ll turn it on for a minute when I’m done writing in order to publish it.
I’m sitting in a park or greenway that may or may not be closed to the public. This sign blocking the stairs to the boardwalk suggests that it is, but the corresponding wheelchair ramp isn’t blocked.
Minor germinal update: link syntax So, the Gemini link syntax was finalized:
Link Syntax Finalized
The one place this affects Germinal is in the generation of directory indexes. Germinal’s directory indexing code has been updated accordingly.
I have also updated the links on my Gemini site.
Unless there are changes coming to the response header line format, this is probably the last Gemini change that actually affects Germinal. Pretty much everything else is client-side.
Composing polls I have specifically not written support for creating polls yet.
Is the gemini map format intended to be reflowed? One question that hasn’t been addressed in the Gemini speculative specification is whether the Gemini map file format text/gemini is intended to be reflowed. By reflowed, I mean mainly that the line-length of the file itself is not intended to be mapped exactly to the output device, which should instead lay out the text with appropriate line lengths. This is what HTML renderers do, and what MarkDown renderers do, usually by way of conversion to HTML.