blog: fix images
ci/woodpecker/push/woodpecker Pipeline was successful
Details
ci/woodpecker/push/woodpecker Pipeline was successful
Details
parent
a201bc21bf
commit
476ed85e93
|
|
@ -17,7 +17,7 @@ Finally, it is important to verify that the stuffed animal has been certified to
|
|||
|
||||
## a good example: the jellycat bashful bunny
|
||||
|
||||
|
||||
|
||||
|
||||
One of my favorite bunny designs is the [Jellycat Bashful Bunny](https://www.jellycat.com/us/bashful-cream-bunny-bas3bc/). I have several of them, ranging from small to the largest size available.
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ This is what I would consider to be a high quality design. While the seam line
|
|||
|
||||
## a bad example: build a bear's pawlette
|
||||
|
||||
|
||||
|
||||
|
||||
A few people have asked me about [Build a Bear's Pawlette design](https://www.buildabear.com/online-exclusive-jumbo-pawlette/025756.html) recently, as it looks very similar to the Jellycat Bashful Bunny. I don't think it is a very good design.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Recently, a new version of ncurses was released and pushed to Alpine. The mainta
|
|||
|
||||
You might think, what a weird regression, and you'd be right. After all, pkg-config files are usually just installed to `$libdir/pkgconfig` in any sort of autotools-based build system. Indeed, in the past, this is what ncurses did as well. However, this was clearly too robust of a solution to the problem of determining where to install the pkg-config files, and so innovation™️ happened:
|
||||
|
||||
|
||||
|
||||
|
||||
Yes, you are reading this right: it is **scraping debug output** to find the pkg-config search path. This kind of behavior is clever, and it should absolutely be avoided in anything designed to be portable, such as a configure script. In fact, really, a build system should follow established expectations, specifically, in the autotools case, it should just default to `$libdir/pkgconfig` and allow the end user to override that if it makes sense to. Doing anything else is going to lead to edge cases and problems, since it is more clever than the user expects it to be.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,21 +17,21 @@ As most people know, GNU nano began its life as a clone of UW pico. Pico (shor
|
|||
|
||||
The licensing problem in combination with a desire to make a more capable editor based on the overall `pico` user experience led to the creation of GNU nano.
|
||||
|
||||
In the Alpine Linux distribution, both `pico` and `nano` are available. Here's what `pico` looks like by default:
|
||||
In the Alpine Linux distribution, both `pico` and `nano` are available. Here's what `pico` looks like by default:
|
||||
|
||||
## The default `nano` experience
|
||||
|
||||
Like with `pico`, the default UI for `nano` is quite boring to look at. Here is GNU nano displaying the same file with the default configuration:
|
||||
|
||||
As you can hopefully see, the default `nano` configuration is quite similar to that of `pico`. However, unlike `pico`, it can be changed by editing the `~/.nanorc` file.
|
||||
As you can hopefully see, the default `nano` configuration is quite similar to that of `pico`. However, unlike `pico`, it can be changed by editing the `~/.nanorc` file.
|
||||
|
||||
## Building something like `vim` using `.nanorc`
|
||||
|
||||
What I want in an editor is something that basically looks like `vim`, but is modeless like `nano`. Something like this:
|
||||
|
||||
But how do we get there? The answer is simple: we use the `~/.nanorc` file.
|
||||
But how do we get there? The answer is simple: we use the `~/.nanorc` file.
|
||||
|
||||
As a result of many people wanting the same thing: `vim`\-like functionality with modeless editing, `nano` gained several third-party patches which allowed for this. For the most part, these patches (or equivalent functionality) have been included upstream in recent years.
|
||||
As a result of many people wanting the same thing: `vim`\-like functionality with modeless editing, `nano` gained several third-party patches which allowed for this. For the most part, these patches (or equivalent functionality) have been included upstream in recent years.
|
||||
|
||||
Getting most of the way to a vim-like look and feel, without syntax highlighting, is quite simple. You simply need to add these lines to your `~/.nanorc` file with any recent version of `nano`:
|
||||
|
||||
|
|
@ -43,14 +43,14 @@ set nohelp
|
|||
|
||||
That gets you something like this:
|
||||
|
||||
However, that minibar looks a little ugly with the inverse text. The good news is, we can disable the inverse text by adding another snippet to `~/.nanorc`:
|
||||
However, that minibar looks a little ugly with the inverse text. The good news is, we can disable the inverse text by adding another snippet to `~/.nanorc`:
|
||||
|
||||
\# disable inverse text for the minibar
|
||||
set titlecolor normal,normal
|
||||
|
||||
The way this works is by setting the foreground and background colors for the titlebar to `normal`, which means that `nano` shouldn't change whatever color is already set. That gives us:
|
||||
|
||||
|
||||
|
||||
|
||||
## Enabling syntax highlighting
|
||||
|
||||
|
|
@ -67,4 +67,4 @@ include "~/.nano/c.nanorc"
|
|||
|
||||
Once you do that, you're done and left with a nano that looks like this:
|
||||
|
||||
Hopefully this post demonstrates that `nano` is a quite capable editor in its own right.
|
||||
Hopefully this post demonstrates that `nano` is a quite capable editor in its own right.
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ I really, _really_ wanted to find a reason to hate on Oracle here. I mean, the
|
|||
|
||||
So, we have one option for a paid ARM VPS, and that is only an option if you are willing to deal with Oracle, which are Oracle. Did I mention they are Oracle?
|
||||
|
||||
|
||||
|
||||
|
||||
## Scaleway
|
||||
|
||||
|
|
|
|||
|
|
@ -25,33 +25,33 @@ In the meantime, it is pretty simple to install Alpine. The first step is to p
|
|||
|
||||
Once the image is running, you'll be presented with a control panel like so:
|
||||
|
||||
|
||||
|
||||
|
||||
The next step is to create an SSH-based serial console. You will need this to access the Alpine installer. Scroll down to the resources section and click "Console Connection." Then click "Create Console Connection":
|
||||
|
||||
|
||||
|
||||
|
||||
This will open a modal dialog, where you can specify the SSH key to use. You'll need to use an RSA key, as this creation wizard doesn't yet recognize Ed25519 keys. Select "Paste public key" and then paste in your RSA public key, then click "Create console connection" at the bottom of the modal dialog.
|
||||
|
||||
The console connection will be created. Click the menu icon for it, and then click "Copy Serial Console Connection for Linux/Mac."
|
||||
|
||||
|
||||
|
||||
|
||||
Next, open a terminal and paste the command that was copied to your clipboard, and you should be able to access the VPS serial console after dealing with the SSH prompts.
|
||||
|
||||
|
||||
|
||||
|
||||
The next step is to SSH into the machine and download the Alpine installer. This will just be `ssh opc@1.2.3.4` where 1.2.3.4 is the IP of the instance. We will want to download the installer ISO to `/run`, which is a ramdisk, and then write it to `/dev/sda` and then sysrq b to reboot. Here's what that looks like:
|
||||
|
||||
|
||||
|
||||
|
||||
If you monitor your serial console window, you'll find that you've been dropped into the Alpine installer ISO.
|
||||
|
||||
|
||||
|
||||
|
||||
From here, you can run `setup-alpine` and follow the directions as usual. You will want to overwrite the boot media, so answer yes when it asks.
|
||||
|
||||
|
||||
|
||||
|
||||
At this point, you can reboot, and it will dump you into your new Alpine image. You might want to set up `cloud-init`, or whatever, but that's not important to cover here.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,11 +22,11 @@ Well, the simple answer is that they don't. You might hear differently from co
|
|||
|
||||
NFT platforms like ArtMagic try to make it look like it is possible to enforce restrictions on your intellectual property using NFTs. For example, [this NFT is listed as being limited to 1000 copies](https://nftmagic.io/view?asset=12588085591129036864):
|
||||
|
||||
|
||||
|
||||
|
||||
However, there is no mechanism to actually enforce this. It is possible that only 1000 instances of the NFT can be _sold_, but this does not restrict the actual number of copies to 1000. To demonstrate this, I have made a copy of this artwork and reproduced it on my own website, which exists outside of the world where the NFT has any enforcement mechanism.
|
||||
|
||||
|
||||
|
||||
|
||||
As you can see, there are now at least 1001 available copies of this artwork. Except you can download that one for free.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ As you may know, there are two mainstream ActivityPub servers that are in wide u
|
|||
|
||||
### Handling ActivityPub in a world without JSON-LD
|
||||
|
||||
|
||||
|
||||
|
||||
Instead, Pleroma has a module called `Transmogrifier` that translates between _real_ ActivityPub and our _ActivityPub internal representation_. The use of AP constructs in our internal representation is the origin of the statement that Pleroma uses ActivityPub internally, and to an extent it is a very truthful statement: our internal representation and object graph are directly derived from an earlier ActivityPub draft, but it's not _quite_ the same, and there have been a few bugs where things have not been translated correctly which have resulted in leaks and other problems.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Outside of Mastodon, the situation is quite different. Most of us see the softwa
|
|||
|
||||
But Mastodon is still problematic when it comes to innovation in the fediverse at large. Despite the ability that other fediverse software give to users and admins to present their content in whatever form they want, Mastodon presently fails to render the content correctly:
|
||||
|
||||
|
||||
|
||||
|
||||
The [patches I referred to earlier](https://github.com/tootsuite/mastodon/pull/10629) correct this problem by changing how Mastodon processes posts from remote instances. They also provide a path toward improving usability in the fediverse by allowing us to work toward phasing out the use of Unicode mathematical constants as a substitute for proper formatting. The majority of fediverse microblogging software has supported this kind of formatting for a long time, many implementations predating Mastodon itself. Improved interoperability with other fediverse implementations sounds like a good thing, right? Well, it's not aligned with the Mastodon vision, so it's rejected.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue