Having spun up Port70 as a support library for my effort to add gopher support to Rogallo, the next thing I needed was some code to parse the "gopher map" responses that you get back from Gopher servers. While this could have been some code in Rogallo itself, much like with Gemtext, it seemed sensible to put it in its own library so it could be useful elsewhere.
Because Rogallo heavily relies on MIME types to make decisions about what to do with content, each ItemType has a best-efforts-guess mime_type associated with it. This will make it pretty straightforward for me to decide if a resource from a Gopher server is something Rogallo can display.
It was, of course, inevitable that this would happen. After spinning up Port79 so that I could add finger support to Rogallo, it made sense that I start to think about Gopher support too. So here we go: Port70, a similar library for async interaction with Gopher servers.
This is going to be a bit of an adventure for me. While I'm long familiar with the existence of Gopher, and I'm fairly certain I used a client once or twice back in the 90s, I've never really had dealings with the protocol so know very little about it. Which is a good thing: something new (old?) to learn.
My plan with this is to add the GopherURI class to the list of URI types that Rogallo understands and handles and then provide a method of displaying and navigating the result. I think the cleanest and easiest way of doing this will be to add some code that transforms a menu response into gemtext and then just let the viewer widget display it as normal; each of the links in the menu being turned into gopher:// URIs.
This should be fun to play with. I'm looking forward to pulling it all together.
I've just bumped Port79 to v1.0.0. There's no significant change in this release, other than the addition of the usual dunder-based metadata that is common in Python libraries; somehow I'd managed to leave it out in the last couple of releases.
Now that I've successfully added finger support to Rogallo, and the library is working out well, there didn't seem much point in letting it hang around in zero-point-whatever-land.
On the off chance that someone else does use Rogallo, and needs help getting to the bottom of some sort of issue, I thought it might be useful to add a diagnostics command to the CLI. Right now it's pretty simple, just dumping some version and environment information.
This was something I was interested in adding, and a couple of people have already requested it, so Rogallo now has finger support. This has been added in a couple of ways. The first and most obvious is that finger: URIs are now natively supported in Gemtext content. So now if you follow a finger:// link you'll see the response in Rogallo itself.
The other method is to use the new !finger command that has been added to the application's command line.
Of course, in the command line, you can also just enter a finger:// URI if you wish, which I guess is a third way of doing it.
Finger URIs are recorded in the history, and can also be bookmarked.
This was also something I was keen on doing, and then someone else happened to ask for it: support for swapping out to an external editor for writing user input. While the current mechanism is fine for entering a one-liner -- or composing a very short message -- a proper editor (for me that's ideally one with the ability to check spellings) is generally going to be far more useful for a longer body of text. So, with this in mind, the internal editor can now optionally swap out to your text editor of choice.
If you have either VISUAL or EDITOR set in your environment (VISUAL beats EDITOR), Rogallo will let you swap to it by pressing F3 in the internal editor. You can also override that choice by setting external_editor in the configuration file.
Personally, I'm finding this is working really well with emacsclient. From now on, I'm going to find writing content in Geminispace a lot easier.
Now that I've been wandering around Geminispace some more, I've noticed that a common use of pre-formatted text is for logos, ASCII art, that sort of thing. Generally, the sort of things that are best presented with the background the same as the surrounding text. A different shade of background is fine if showing code and stuff, but I feel that this:
looks better than this:
To this end, I've modified the pre-formatted text rendering so that, by default, if pre-formatted text has no alt-text, the background is the same as the surrounding text. On the other hand, if it does have alt-text (and so is likely the name of a programming language, which implies syntax highlighting, which in turn implies you want it to stand out), it isn't blended with the rest of the text.
If your preferences differ from mine, you can control this with the new blend_pre_formatted_with_background configuration file setting. It takes a list of alt-text strings that should be blended. By default it looks like this:
"blend_pre_formatted_with_background":["",]
That is, by default, it only blends empty alt-text pre-formatted text. As it happens, Station uses alt-text for the logo and the user image, but I'd like them blended in too, so I'm running with this:
The last change is a small cosmetic fix to mouse interaction with links. When the mouse cursor is over a link, there should be a hover effect (that is, the background should change colour). This wasn't working if you had link stripes turned on. This is now fixed.
A quick update to Port79. When I kicked this off I'd set up the FingerURI class so that it was pretty permissive in what it would accept. So, for example, you could do any of:
Nice and handy, right? Accept pretty much any input and turn it into a finger URI. However, once I started to add finger support to Rogallo, I realised that this wasn't as helpful as I'd like as it meant I couldn't use it to actually check for a valid URI. It would be more useful to have the class be strict about only being passed finger: URIs.
With this change I can confidently use FingerURI to test if any given input is an actual finger URI, and this also makes it work in a similar way to GeminiURI in Wasat.
I woke up this morning to find that EE had sent me an email at around 00:30 last night.
We're sorry we didn't stick to our appointment or give you 24 hours' notice that we couldn't make it.
We've added a £32.31 credit to your next bill to try and make up for it.
You don't need to do anything, we'll add it automatically.
If you have any questions, please visit our help page.
And then at 08:17 this morning, I got an SMS:
Hi from EE.
We're sorry for not sticking to our appointment or giving you 24 hours' notice that we couldn't make it. We've added a credit of 32.31 GBP to your next bill. You don't need to do anything, but please go to ee.co.uk/go/compensation if you have any questions. Thanks.
Which is kind of weird, because I remember someone turning up yesterday, and my broadband speed is now 935/107 Mbps at the router (vs. the 35/2.7 it was at the start of yesterday). Perhaps it's their way of saying sorry for the failure to deliver the other day? Who can tell though, it doesn't actually say when and why.
We came to see if we can connect your property to our Full Fibre network yesterday.
The good news is we can, but the engineer found that the existing network connection point wasn't suitable for private land's underground connection, so we need to plan a new way to bring the fibre cable to your home, which may also require a specialist engineer for a flat roof connection.
We're really sorry for the delay, but we're on it and will update you again in the next 10 days (we're usually much quicker).
We promise Full Fibre's worth the wait. It's the UK's most reliable broadband technology.
The flat roof thing was... interesting, but okay, I'm sure they know what they're doing and that it's some automated system with a restricted set of outcomes.
Skip forward one day and I get an SMS out of the blue:
Hi, it's Openreach on behalf of EE/BT.
Sorry we missed you.
Book a new date for your Full Fibre installation here: [removed]
The "Sorry we missed you" was very odd. They didn't miss me. I saw them two days earlier. But, again, okay... I followed the link and it also seemed to be written as if one of us had missed an appointment and I needed to pick another day. Anyway, I ignored what it said and just used the date picker to pick the next available day (which was today: as in the day I'm writing this).
Fast forward to today and there's a knock on the door at around 08:30. Around two hours later, and this is what I was seeing:
To be clear: this isn't the actual speed of the connection. This was a quick test from my Mac, in my office, via the Wi-Fi connection. I don't currently have a Mac or PC wired into the router so can't measure the full speed. Testing on the router itself, it's much closer to 943Mbps/100Mbps. But, yeah, I'm good. I finally have full fibre again!
There was an immediate downside though. Once it was all set up, with the new router (which I swapped to as it has Wi-Fi 6, so why not?), I noticed that the ping times between my Macs were all over the place; this was also noticeable in that the ssh connections were so jittery to the point of being almost unusable.
Bugger.
So I did a bunch of digging online and, without getting too deeply into it (because I'm not a networking guy): the problem is AirDrop/Sidecar. They don't play well with a Wi-Fi 6 connection, so do stuff in the background that causes your ping times to be all over the place.
The solution? Turn this off for the Wi-Fi connection on the affected Macs:
I can't find anything that suggests I'm going to regret doing this for the couple of Macs in my office, and for my MacBook Air, and having done it, the performance is fine again.
This is why I avoid anything to do with networking: it always seems like if you improve one thing, it degrades some other thing, and it's only ever fixed by remembering to tweak some reasonably obscure setting somewhere on some particular item of hardware.
While I'm having a moment of calling code stable, I've bumped Wasat to v1.0.0 as well. There's no actual difference here when compared to the last release, other than the development status classifier in the PyPI metadata and the version number.
The library feels pretty stable at this point. I've been using Rogallo every day for a wee while now and I've seen no surprising problems.
Thirty-three days ago, back on the 18th of June, I created a development directory called rogallo, and started adding dependencies and laying out the main user interface of Rogallo. It's been tons of fun working on it while exploring Geminispace. Given that it's quickly turned into my daily driver, and I'm finding it stable, I've decided it's time to drag it out of the 0verse and consider it worthy of being v1.0.0.
I was going to hold off a little longer, mainly because I wanted to flesh out the documentation some more, but that seems like a poor reason to keep it stuck somewhere in v0.x.
To recap, for anyone who might not have followed the development so far: Rogallo is a terminal-based client for the Gemini Protocol. I've built it for my own education. I've built it for fun. I've built it because I want to use it. I've built it hoping that someone else might enjoy it too. Some of the key features, as of this first "stable" release, are:
Keyboard-first TUI interface with good mouse support too.
Bookmark support.
Forward/backward navigation.
Location history.
Home page.
Designed to work on macOS, GNU/Linux and Windows.
Trust-on-first-use support.
In-application creation of client-side certificates.
Full support for user input, both normal and sensitive.
Full support for redirections.
Context-sensitive help screens.
All main application commands available via a command palette or an in-application command line.
Themes.
Responsive layout that dynamically adjusts to terminal resizing.
Support for viewing Gemtext files in the local file system.
View source support.
Copy-to-clipboard support for URIs or page content.
Optionally-numbered links with quick-jump support.
Supports ANSI escape sequences in content.
Supports filtering out ANSI escape sequences.
Emoji filter (lets you remove emojis from most text).
Support for handing off unsupported content to the operating system (with safety checks).
Probably some other stuff I've forgotten right now.
On top of this, there's more to come. v1.0.0 isn't the end of the line with Rogallo. I'm having plenty of fun using it, and improving it, and there's more I want to add. I very much want to add in-app support for the Finger Protocol, and I can see myself falling down the Gopher rabbit-hole1 at some point too. While I don't want the application to grow out of hand, I can see plenty of extensions and enhancements that will be satisfying to add.
If any of this sounds interesting and you want to have a play, Rogallo is licensed GPL-3.0 and available via GitHub and also via PyPI. If you have an environment that has pipx installed, you should be able to get up and running with (note that Python 3.12 or later is required):
