Skip to main content

Johan Bové

Gophering along

2 min read

A screenshot of Johan's Gopherhole

I've been spending way too much time on servers in the last couple of days.

The Gopher Web is intriguing and fascinating and I totally understand the attraction of an ad-free, cookie-free, not-for-profit, underground(-ish) alternative to today's crowded and over-commericially exploited (according to many) HTTP Web.

It's not super straightforward to access, even-though there are good dedicated free browsers (for all platforms) available that totally support the Gopher protocol.

But I have the feeling that because the Gopher Web is a little harder to access, it is actually part of the attractiveness. Lots of humans tired of the current state of the WWW, who still want to publish
content and share stuff, are finding an alternative, albeit archaic, in the Gopher web.

Setting up a Gopher server wasn't hard either thanks to open-source software from dedicated hobbyist developers.

Formatting plain-text files has been interesting too. It's amazing how much effort some Gopher Hole Phloggers take to create beautiful ASCII art and line-out their paragraphs!

Discovering Phlogs has been an eye-opener and inspiring. There are many Phloggers who are publishing worthwile stories and interesting articles in plain text files in their Gopher holes or gopher burrows.

And I had some fun first-time experiences too playing a funny text-based adventure game called "Lost Pig" (2007) -  it's an interactive story, with lots of funny dialogue and plenty of character which by itself is also proof that Gopher pages can also be entertaining.

The Floodgap Gopher (Gopher proxy) site is a great place to start.

Johan Bové

Nokia 8110 4G Requests - Part 1

2 min read

Nokia 8110 4G banana yellow and black side to side

Gathering a list of issues and changes I would like to see fixed on my 4G phone.

Most of these issues can be fixed with a hypothetical software update. So it's up to HMD Global (@NokiaMobile) to work on the apps and system software on the phone and release a new update - preferably sooner than later.

And the WhatsApp integration should be implemented by Facebook Team WhatsApp of course.

List of software nuisances:

  • WhatsApp is running on the phone, but is lacking in these ways:
    • No support, even-though the phone has a QR-reading-cabable camera on board
    • Received videos have a maximum file size of 8MB, so anything bigger than that cannot be opened, at all. Memory limitations?
    • No calling
    • No video chat
  • No emoji input - This makes me really sad. 😅
  • No CalDAV and CardDav sync support - would have been great to be able to easily synchronize contacts outside of Google or Apple sync.
  • The volume controls are practically useless as the phone has three volume settings even-though it has a scale from vibrate to 15, the actual volume stages are "Really Loud", "Loud" or "vibrate".
  • The phone gets really hot during calls - not sure if software or hardware related to be honest.

It would be awesome if this list could be marked off soon.

Johan Bové

Known plugin update process

1 min read

In response to jgmac1106 on :

My plugin-updating process is currently like this:

  1. Create a fork of the Github idno project
  2. Checkout the code from the repo
  3. Fire up Beyond Compare and start a folder compare session
  4. Synchronize the plugin folder from local to remote

Of course it should be possible that you clone the Github plugin code through git clone and then do a git pull upstream to get the latest from the original master.

You should then be able to also run a composer update command to make sure you're getting the latest "vendor" dependencies too.

Johan Bové

My Known "Content-Security-Policy" htaccess configuration

2 min read

My current Known .htaccess Content-Security-Policy is full of tool urls.

<IfModule mod_headers.c>
Header set Content-Security-Policy: "default-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; object-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' https: data:; media-src *; worker-src 'self' https; font-src *; connect-src 'self'; frame-src 'self';
    Header set X-Content-Security-Policy: "default-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; object-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' https: data:; media-src *; worker-src 'self' https; font-src *; connect-src 'self'; frame-src 'self';
    Header set X-WebKit-CSP: "default-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; object-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' https: data:; media-src https:; worker-src 'self' https; font-src *; connect-src 'self'; frame-src 'self';

Johan Bové

Radio Soulwax - Benelux

1 min read

The Belgian DJ's from Radio Soulway (RSWX) clearly had way too much fun making this "Benelux" themed one hour long mix and accompanying video.

Johan Bové

No Hello

2 min read

A repost from the website, published Wednesday, January 16, 2013

Please Don't Say Just Hello In Chat

2010-07-19 12:32:12 you: Hi
2010-07-19 12:32:15 co-worker: Hello.
2010-07-19 12:34:01 you: I'm working on [something] and I'm trying to do [etc...]
2010-07-19 12:35:21 co-worker: Oh, that's [answer...]

It's as if you called someone on the phone and said "Hi!" and then put them on hold!
Please do this instead:

2010-07-19 12:32:12 you: Hi -- I'm working on [something] and I'm trying to do [etc...]
2010-07-19 12:33:32 co-worker: [answers question]

Note that you get help minutes sooner, and you don't make them wait. Instead, the co-worker can start thinking about your question right away!
You're trying to be polite by not jumping right into the request, like you would do in person or on the phone. But Chat is neither of those things. Typing is much slower than talking. Instead of being polite, you are just making the other person wait for you to phrase your question, which is lost productivity.
The same goes for "Hello -- Are you there?", "Hi Bob -- quick question.", "Do you have a sec ?", "yt?" and "ping". Just ask the question!
If you feel it's brusque to simply say "Hi" and ask the question, you can do something like this:

2010-07-19 12:32:12 you: Hi -- if you're not busy I was wondering if I could ask a question.  I'm working on [something] and I'm trying to do [etc...]

Additionally, asking your question before getting a reply allows asynchronous communication. If the other party is away, and you leave before they come back, they can still answer your question, instead of just staring at a "Hello" and wondering what they missed.
Short link to this page: (If you see that as someone's status, please be prepared to be ignored if you only say "Hello!".)

Johan Bové

Testing unlisted post

1 min read

This should be an unlisted post to test Issue 937 (

Johan Bové

Replying to Add .editorconfig for code formatting consistency

1 min read

Regarding the editorconfig support:

That's a good question. Looking at the Github project and the number of integrations that are available for all editors, I would say it's fairly widely supported.

It helps us to have everyone use spaces instead of tabs, even-though colleagues might use a different editor for coding.

Johan Bové supports RSS powered republishing

1 min read

Pretty neat how support RSS powered republishing.

Here is a screenshot of their interface:

Publishing to from RSS

Johan Bové

Pinning Known Status content to appear at the top of a page

1 min read

Regarding the Status plugin:

Just like Twitter does within pinning a status to a profile, a specific Status can be pinned to appear at the top of the list.

Would this be done within this plugin or would this have to be added to the Known core project?