mirror of
https://github.com/jbowdre/capsule.git
synced 2024-12-25 01:22:19 +00:00
fix image links
This commit is contained in:
parent
994fc7059d
commit
1c0c86a2d0
3 changed files with 4 additions and 4 deletions
|
@ -8,7 +8,7 @@ I used (and kind of loved) a bunch of different keyboards back in the day, inclu
|
|||
|
||||
Seriously, look at this ridiculous layout:
|
||||
|
||||
=> /res/images/2024-02-12-8pen-layout.png Image: Colored lines intersect behind a magnifying glass, which centers on letters and symbols arranged in a circle on a white background - but it's a keyboard, somehow?
|
||||
=> /res/2024-02-12-8pen-layout.png Image: Colored lines intersect behind a magnifying glass, which centers on letters and symbols arranged in a circle on a white background - but it's a keyboard, somehow?
|
||||
|
||||
It's wild, right? Once I figured out how to use it, I got to be pretty fast and accurate at text entry - and it's designed in such a way that (once you learn it) you don't have to look at the keyboard at all.
|
||||
|
||||
|
@ -21,4 +21,4 @@ It's also been enhanced with Vim-inspired editor ability, or something.
|
|||
|
||||
I used 8vim to type (some) of this message and it only took forever. I'm sure I will get the hang of this again in no time.
|
||||
|
||||
=> /res/images/2024-02-12-8vim-keyboard.png Image: A smartphone screen displaying a text editor app with a unique keyboard layout. The text discusses an open-source clone of an abandoned project, 8vim Keyboard, and mentions the user's experience adapting to it.
|
||||
=> /res/2024-02-12-8vim-keyboard.png Image: A smartphone screen displaying a text editor app with a unique keyboard layout. The text discusses an open-source clone of an abandoned project, 8vim Keyboard, and mentions the user's experience adapting to it.
|
|
@ -6,7 +6,7 @@ I've lately been playing a bit with a self-hosted instance of SearXNG, an utterl
|
|||
Rather than maintaining its own index or running its own crawlers (as something like YaCy does), SearXNG simply asks other engines for their results to a given query (remember Dogpile from back in the day?). The really cool thing with SearXNG is that it also gives you, the user, a whole lot of control over what engines it uses to create its aggregated results.
|
||||
|
||||
=> https://yacy.net/ YaCy homepage
|
||||
=> /res/images/2024-02-21-searxng-prefs.png Image: SearXNG Preferences page listing some of the available search engines
|
||||
=> /res/2024-02-21-searxng-prefs.png Image: SearXNG Preferences page listing some of the available search engines
|
||||
|
||||
It's pretty neat, and the results so far have been fairly decent. If you'd like to give it a try, my instance is at grep.vim.wtf. (At least until I get bored with it.)
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ It didn't take much tinkering to get Upptime configured and operational for keep
|
|||
|
||||
=> https://status.runtimeterror.dev/ "Upptime Terror", the status page for my public sites
|
||||
|
||||
=> /res/upptime-screenshot.png Image: Green-themed website status page displaying real-time data from a GitHub repository. It shows a 100% uptime for various services with average response times ranging from 545 ms to 747 ms.
|
||||
=> /res/2024-01-30-upptime-screenshot.png Image: Green-themed website status page displaying real-time data from a GitHub repository. It shows a 100% uptime for various services with average response times ranging from 545 ms to 747 ms.
|
||||
|
||||
Check out the docs to learn more:
|
||||
=> https://upptime.js.org/docs/ Upptime Documentation
|
Loading…
Reference in a new issue