Fix internal links
This commit is contained in:
parent
d4ed6492ad
commit
4849f13a6c
4
content/.obsidian/graph.json
vendored
4
content/.obsidian/graph.json
vendored
@ -28,10 +28,10 @@
|
||||
"nodeSizeMultiplier": 1.42708333333333,
|
||||
"lineSizeMultiplier": 1.171875,
|
||||
"collapse-forces": false,
|
||||
"centerStrength": 0.328125,
|
||||
"centerStrength": 0.296875,
|
||||
"repelStrength": 14.1666666666667,
|
||||
"linkStrength": 1,
|
||||
"linkDistance": 250,
|
||||
"scale": 0.07178423896278742,
|
||||
"scale": 0.13187606777463332,
|
||||
"close": false
|
||||
}
|
||||
@ -21,5 +21,5 @@ We, as a team are looking to bring our programming and robots to the next level
|
||||
It's time for a change, but what do we change to?
|
||||
|
||||
## Part 2
|
||||
The followup can be found [HERE](/frc/2019/06/24/LanguageHunt2.html).
|
||||
The followup can be found [HERE](@/blog/2019-06-24-LanguageHunt2.md).
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ aliases:
|
||||
- /blog/languagehunt2
|
||||
---
|
||||
|
||||
This is a very short post, just to explain the result of [The language Hunt](/blog/frc-languages).
|
||||
This is a very short post, just to explain the result of [The language Hunt](@/blog/2019-04-30-FRC-Languages.md).
|
||||
|
||||
## Our choice
|
||||
For our upcoming 2020 season and for the forseeable future, we have chosen Java as our programming language for direct hardware interfacing, and Python for networking, vision, and other smaller tasks.
|
||||
|
||||
@ -22,7 +22,7 @@ Bill's notebook is a large (about 580 posts) collection of random thoughts, idea
|
||||
> *"If you are looking to burn something, fire may be just the ticket"* - Bill Wurtz
|
||||
|
||||
## Choosing the right tool for the job
|
||||
If you haven't noticed yet, Im building a neural net to generate notes based on his writing style and content. Anyone who has read [my first post](/blog/2018/06/27/becomeranter) will know that I have already done a similar project in the past. This means *time to reuse come code*!
|
||||
If you haven't noticed yet, Im building a neural net to generate notes based on his writing style and content. Anyone who has read [my first post](@/blog/2018-06-27-BecomeRanter.md) will know that I have already done a similar project in the past. This means *time to reuse come code*!
|
||||
|
||||
For this project, I decided to use an amazing library by @minimaxir called [textgenrnn](https://github.com/minimaxir/textgenrnn). This Python library will handle all of the heavy (and light) work of training an RNN on a text dataset, then generating new text.
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ This is exactly the kind of question I randomly ask while sitting in the middle
|
||||
|
||||
## Geting started
|
||||
|
||||
To get started, I needed a few things. Firstly, I have a laptop running [a Linux distribution](/about/#my-gear). This allows me to use [SSH](https://en.wikipedia.org/wiki/Secure_Shell) and [SCP](https://en.wikipedia.org/wiki/Secure_copy). There are Windows versions of both of these programs, but I find the "linux experience" easier to use. Secondly, I have grabbed one of [5024](https://www.thebluealliance.com/team/5024)'s [robots](https://cs.5024.ca/webdocs/docs/robots) to be subjected to my experiment. The components I care about are:
|
||||
To get started, I needed a few things. Firstly, I have a laptop running Linux. This allows me to use [SSH](https://en.wikipedia.org/wiki/Secure_Shell) and [SCP](https://en.wikipedia.org/wiki/Secure_copy). There are Windows versions of both of these programs, but I find the "linux experience" easier to use. Secondly, I have grabbed one of [5024](https://www.thebluealliance.com/team/5024)'s [robots](https://cs.5024.ca/webdocs/docs/robots) to be subjected to my experiment. The components I care about are:
|
||||
|
||||
- A RoboRIO running 2019v12 firmware
|
||||
- 2 [TalonSRX](https://www.ctr-electronics.com/talon-srx.html) motor controllers
|
||||
|
||||
@ -17,7 +17,7 @@ aliases:
|
||||
- /blog/drivetrain-navigation
|
||||
---
|
||||
|
||||
This post is a continuation on my "Notes from FRC" series. If you haven't already, I recommend reading my post on [Converting joystick data to tank-drive outputs](/blog/2020/08/03/joystick-to-voltage). Some concepts in this post were introduced there. Like last time, to see the production code behind this post, check [here](https://github.com/frc5024/lib5k/blob/ab90994b2a0c769abfdde9a834133725c3ce3a38/common_drive/src/main/java/io/github/frc5024/common_drive/DriveTrainBase.java) and [here](https://github.com/frc5024/lib5k/tree/master/purepursuit/src/main/java/io/github/frc5024/purepursuit/pathgen).
|
||||
This post is a continuation on my "Notes from FRC" series. If you haven't already, I recommend reading my post on [Converting joystick data to tank-drive outputs](@/blog/2020-08-03-Joystick-to-Voltage.md). Some concepts in this post were introduced there. Like last time, to see the production code behind this post, check [here](https://github.com/frc5024/lib5k/blob/ab90994b2a0c769abfdde9a834133725c3ce3a38/common_drive/src/main/java/io/github/frc5024/common_drive/DriveTrainBase.java) and [here](https://github.com/frc5024/lib5k/tree/master/purepursuit/src/main/java/io/github/frc5024/purepursuit/pathgen).
|
||||
|
||||
At *Raider Robotics*, most of my work has been spent on these three subjects:
|
||||
- Productivity infrastructure
|
||||
@ -62,7 +62,7 @@ $$
|
||||
\Delta\theta = \arctan(\Delta y, \Delta x) \cdot \frac{180}{\pi}
|
||||
$$
|
||||
|
||||
Notice how a polar coordinate containing these values: $\big[\begin{smallmatrix}\Delta d \\ \Delta\theta\end{smallmatrix}\big]$ is very similar to our joystick input vector from the [previous post](/blog/2020/08/03/joystick-to-voltage): $\big[\begin{smallmatrix}T \\ S\end{smallmatrix}\big]$. Converting our positional error into a polar coordinate makes the process of navigating to any point very simple. All we need to do is take the [Hadamard product](https://en.wikipedia.org/wiki/Hadamard_product_(matrices)) of the coordinate matrix with a gain matrix to make small adjustments to the output based on the physical characteristics of your robot, like the amount of voltage required to overcome static friction. This is a very simple P-gain controller.
|
||||
Notice how a polar coordinate containing these values: $\big[\begin{smallmatrix}\Delta d \\ \Delta\theta\end{smallmatrix}\big]$ is very similar to our joystick input vector from the [previous post](@/blog/2020-08-03-Joystick-to-Voltage.md): $\big[\begin{smallmatrix}T \\ S\end{smallmatrix}\big]$. Converting our positional error into a polar coordinate makes the process of navigating to any point very simple. All we need to do is take the [Hadamard product](https://en.wikipedia.org/wiki/Hadamard_product_(matrices)) of the coordinate matrix with a gain matrix to make small adjustments to the output based on the physical characteristics of your robot, like the amount of voltage required to overcome static friction. This is a very simple P-gain controller.
|
||||
|
||||
$$
|
||||
input = \begin{bmatrix}\Delta d \\ \Delta\theta\end{bmatrix}\circ\begin{bmatrix}K_t \\ K_s \end{bmatrix}
|
||||
@ -90,4 +90,4 @@ For a real-world example of this method in use, check out 5024's robot (bottom r
|
||||
|
||||
---
|
||||
|
||||
I hope someone will some day find this post helpful. Most papers about this topic went way over my head in 10th grade, or were over-complicated for the task. If you would like me to go further in depth on this topic, [contact me](/about/) and let me know. I will gladly help explain things, or write a new post further expanding on a topic.
|
||||
I hope someone will some day find this post helpful. Most papers about this topic went way over my head in 10th grade, or were over-complicated for the task. If you would like me to go further in depth on this topic, [contact me](/contact) and let me know. I will gladly help explain things, or write a new post further expanding on a topic.
|
||||
|
||||
@ -56,4 +56,4 @@ This is almost entirely accomplished by a shell script and a custom CI script.
|
||||
|
||||
---
|
||||
|
||||
If you have any questions about this system, want me to write another post about it, or would like me to walk you through setting up a notes workspace of your own, [contact me](/about)
|
||||
If you have any questions about this system, want me to write another post about it, or would like me to walk you through setting up a notes workspace of your own, [contact me](/contact)
|
||||
|
||||
@ -18,7 +18,7 @@ aliases:
|
||||
- /blog/reading-a-bitmap
|
||||
---
|
||||
|
||||
Recently, @rsninja722 was telling me about [a project](https://github.com/rsninja722/file2bmp) he was working on. The basic idea is that you pass a file into his program, and it generates a bitmap of the binary data. This was inspired by [an old post of mine](/post/ef7b3166) where I did the same thing with a horribly written Python script and the library [`pillow`](https://github.com/python-pillow/Pillow).
|
||||
Recently, @rsninja722 was telling me about [a project](https://github.com/rsninja722/file2bmp) he was working on. The basic idea is that you pass a file into his program, and it generates a bitmap of the binary data. This was inspired by [an old post of mine](@/blog/2019-09-11-Buildingimgfrombin.md) where I did the same thing with a horribly written Python script and the library [`pillow`](https://github.com/python-pillow/Pillow).
|
||||
|
||||
Both of us are currently teaching ourselves the **C** programming language. Him, for a break from JavaScript. Me, for no particular reason. As somebody who mostly lives in the world of high-level C-family languages (C++ and Python), learning C has been a challenging, fun, and rewarding experience. I enjoy immersing myself in *"the old way of doing things"*. This means sitting down with my Father's old [*ANSI Standard C Programmer's Reference*](https://archive.org/search.php?query=external-identifier%3A%22urn%3Aoclc%3Arecord%3A1028045558%22) book, and looking up what I need to know through a good old appendix full of libc headers and their function lists.
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ I don't remember [Curseforge](https://curseforge.com/) existing back when I used
|
||||
|
||||
My main goal for the updated version of CorePack was to design it in such a way I could make a CI pipeline generate new releases for me when mods are updated. This requires programmatically pulling information about mods, and their JAR files using a buildsystem script. Since this project involves working with a large amount of data from various external sources, I once-again chose to use [Bazel](https://bazel.build), a buildsystem that excels at these kinds of projects.
|
||||
|
||||
While Curseforge provides a very easy to use API for working with mod data, @Wyn-Price (a fellow mod developer) has put together an amazing project called [Curse Maven](https://www.cursemaven.com/) that I decided to use instead. Curse Maven is a serverless API that acts much like my [Ultralight project](/blog/2020/09/17/ultralight-writeup). Any request for an artifact to Curse Maven will be redirected, and served from the [Curseforge Maven server](https://authors.curseforge.com/knowledge-base/projects/529-api#Maven) without the need for me to figure out the long-form artifact identifiers used internally by curse.
|
||||
While Curseforge provides a very easy to use API for working with mod data, @Wyn-Price (a fellow mod developer) has put together an amazing project called [Curse Maven](https://www.cursemaven.com/) that I decided to use instead. Curse Maven is a serverless API that acts much like my [Ultralight project](@/blog/2020-09-17-Ultralight-writeup.md). Any request for an artifact to Curse Maven will be redirected, and served from the [Curseforge Maven server](https://authors.curseforge.com/knowledge-base/projects/529-api#Maven) without the need for me to figure out the long-form artifact identifiers used internally by curse.
|
||||
|
||||
Curse Maven makes loading a mod (in this case, [`fabric-api`](https://www.curseforge.com/minecraft/mc-mods/fabric-api)) into Bazel as easy as:
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ aliases:
|
||||
- /blog/minecraft-irc
|
||||
---
|
||||
|
||||
As I talked about in my post [about Minecraft modpack development](/blog/2020/10/24/corepack-development), I got back in to playing Minecraft earlier this year. I primairly play on a server full of friends, where the server owner has [dynmap](https://github.com/webbukkit/dynmap) installed. Dynmap is a handy tool that provides a near-real-time overview of the minecraft world in the form of a webapp. I always keep Dynmap open on my laptop so I can chat with whoever is online, and see whats being worked on.
|
||||
As I talked about in my post [about Minecraft modpack development](@/blog/2020-10-24-CorePack-Development.md), I got back in to playing Minecraft earlier this year. I primairly play on a server full of friends, where the server owner has [dynmap](https://github.com/webbukkit/dynmap) installed. Dynmap is a handy tool that provides a near-real-time overview of the minecraft world in the form of a webapp. I always keep Dynmap open on my laptop so I can chat with whoever is online, and see whats being worked on.
|
||||
|
||||
While dynmap has a built-in chat log, and the ability to send chats, the incoming chat messages do not persist, and the outgoing chat messages don't always show your in-game username (but instead, your public IP address). Since I always have an IRC client open, I figured that making use of my IRC client to generate a persistent chat log in the background would be a good solution. Unfortunately, I could not find anyone who has ever built a `Minecraft <-> IRC` bridge. Thus my project, [chatster](https://github.com/Ewpratten/chatster), was born.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ In terms of versions, I am running Fabric Loader version `0.10.6+build.214`, and
|
||||
|
||||
## Network Protocol Translation
|
||||
|
||||
One of my least favorite parts of playing on multiple multiplayer servers is the need to constantly switch Minecraft versions to accommodate every server version I am playing on. For example, the server I talk about in my post about [Minecraft chat over IRC](/blog/2020/11/21/minecraft-irc) is running version `1.16.3`. You may have played on some high-end servers like [Hypixel](https://hypixel.net/) or [MCCTF](https://www.brawl.com/front/), where you can connect with any client version you want. These servers are both running [Network Protocol Translation](https://en.wikipedia.org/wiki/Protocol_converter) plugins that will convert between Minecraft server protocol versions as packets are sent and received.
|
||||
One of my least favorite parts of playing on multiple multiplayer servers is the need to constantly switch Minecraft versions to accommodate every server version I am playing on. For example, the server I talk about in my post about [Minecraft chat over IRC](@/blog/2020-11-21-Minecraft-IRC.md) is running version `1.16.3`. You may have played on some high-end servers like [Hypixel](https://hypixel.net/) or [MCCTF](https://www.brawl.com/front/), where you can connect with any client version you want. These servers are both running [Network Protocol Translation](https://en.wikipedia.org/wiki/Protocol_converter) plugins that will convert between Minecraft server protocol versions as packets are sent and received.
|
||||
|
||||
This can also be set up on the client instead of the server, allowing a single client to connect to multiple server versions. I run both the [Viaversion](https://github.com/ViaVersion/ViaVersion) and [Multiconnect](https://github.com/Earthcomputer/multiconnect) mods, which together allow my `1.16.4` client to play on servers all the way down to `1.8.0`.
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; pic
|
||||
|
||||
This robot brought us all the way to the finals of our only competition this year (before the world got shut down). It was only in the finals that we finally lost our winning streak (and strong #1 place) due to some questionable scoring and a broken component on one of our teammate's robots.
|
||||
|
||||
On the software side of this machine, [I pushed to switch the core development language over to Java](/blog/2019/06/24/languagehunt2), which went very well, and the team seems to be on track to stay with this new language and toolset for the forseeable future. This year, we pushed very hard towards our goal of letting software handle as much of the "hard work" of operation as possible. In previous years, our robots mainly acted as stupidly expensive RC cars with custom controls, but this year, we wanted to offload tasks prone to human error to computers.
|
||||
On the software side of this machine, [I pushed to switch the core development language over to Java](@/blog/2019-06-24-LanguageHunt2.md), which went very well, and the team seems to be on track to stay with this new language and toolset for the forseeable future. This year, we pushed very hard towards our goal of letting software handle as much of the "hard work" of operation as possible. In previous years, our robots mainly acted as stupidly expensive RC cars with custom controls, but this year, we wanted to offload tasks prone to human error to computers.
|
||||
|
||||
We were able to design a fully autonomous shooting system using high-speed computer vision, real-time path planning, and ball trajectory models to allow our operators to make the robot score game pieces by pressing and holding a single button. On top of this scoring system, *Darth Raider* featured fully autonomous and real-time-error-correcting spatial navigation, allowing us to input a list of goal coordinates for the robot to navigate to efficiently. The final large autonomously controlled system of this robot was known as the "hopper"; a long tunnel for storing and stacking balls. This system was 100% software controlled, and made use of an amazing predictive sorting system developed by @rsninja722 that would perfectly align balls as they were fed in to the robot. Below is a clip taken from semi-finals where we wrote an experimental system that allowed us to essentially use two completely separate robots as one, effectively doubling our gamepiece storage capacity from our max 4 balls to 7. (Big thanks to the [Falcons](https://www.thebluealliance.com/team/5032) for letting us subject them to this experiment.)
|
||||
|
||||
@ -66,11 +66,11 @@ During a rewrite of this website I did earlier this year, I implemented a new se
|
||||
- Web
|
||||
- Pipeline -->
|
||||
|
||||
All the code I have written this year has lead to the need to build a plethora of common software libraries in my three main languages: Python, Java, and C/C++. Through the process of building these, I have picked up many new skills like: properly unit-testing software, [building reliable library distribution systems](/blog/2020/09/17/ultralight-writeup), and extensively documenting code.
|
||||
All the code I have written this year has lead to the need to build a plethora of common software libraries in my three main languages: Python, Java, and C/C++. Through the process of building these, I have picked up many new skills like: properly unit-testing software, [building reliable library distribution systems](@/blog/2020-09-17-Ultralight-writeup.md), and extensively documenting code.
|
||||
|
||||
In the web world, I have learned to work with [JamStack](https://jamstack.org/), and have deployed many serverless / lambda-powered web applications, mostly based on [Flask](https://github.com/pallets/flask) or [Jekyll](https://jekyllrb.com/). A list of my repositories that use these technologies can be found [here](https://github.com/search?l=&q=user%3AEwpratten+filename%3Anow.json&type=code).
|
||||
|
||||
I have also picked up low-level programming for systems running on the [AVR Microprocessor architecture](https://en.wikipedia.org/wiki/AVR_microcontrollers). I have found AVR programming to be a fun and generally easy way to learn about very low-level computing: interrupts, timers, I/O, serial busses, memory management, etc. I also used this as an opportunity to learn how to use a powerful new build system developed by Google, called [*Bazel*](/categories?c=bazel). Many of my projects this year have been shifting over to build with *Bazel* as I really enjoy the build environment and tooling available. I have also used *Bazel* to build [my popular school note-taking system](/blog/2020/08/23/notetaking-with-latex).
|
||||
I have also picked up low-level programming for systems running on the [AVR Microprocessor architecture](https://en.wikipedia.org/wiki/AVR_microcontrollers). I have found AVR programming to be a fun and generally easy way to learn about very low-level computing: interrupts, timers, I/O, serial busses, memory management, etc. I also used this as an opportunity to learn how to use a powerful new build system developed by Google, called [*Bazel*](/categories?c=bazel). Many of my projects this year have been shifting over to build with *Bazel* as I really enjoy the build environment and tooling available. I have also used *Bazel* to build [my popular school note-taking system](@/blog/2020-08-23-Notetaking-with-LaTeX.md).
|
||||
|
||||
A list of the over 200 personal projects I have worked on this year (including unfinished projects) can be found with [this query](https://github.com/search?l=&q=user%3AEwpratten+created%3A%22%3E+2020-01-01+%3C+2021-01-01%22&type=repositories).
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ As I continue to write more and more Java libraries for personal and public use,
|
||||
- Slow builds
|
||||
- No easy way to publish custom artifacts or use custom groups
|
||||
- Sometimes unusably long cache policy
|
||||
- [Ultralight](/blog/2020/09/17/ultralight-writeup)
|
||||
- [Ultralight](@/blog/2020-09-17-Ultralight-writeup.md)
|
||||
- Has a file transfer limit
|
||||
- Uses my personal API keys to interact with GitHub
|
||||
- No way to automate package updates
|
||||
@ -41,7 +41,7 @@ As a student, I prefer not to do the sensible solution--*spin up an [Artifactory
|
||||
|
||||
## What makes a maven server special?
|
||||
|
||||
Really, not much. As outlined in my [previous maven-related post](/blog/2020/09/17/ultralight-writeup), a maven server is just a simple webserver with a specific directory structure, and some metadata files placed in specific locations.
|
||||
Really, not much. As outlined in my [previous maven-related post](@/blog/2020-09-17-Ultralight-writeup.md), a maven server is just a simple webserver with a specific directory structure, and some metadata files placed in specific locations.
|
||||
|
||||
Let's say we wanted to publish a package with the following attributes:
|
||||
|
||||
|
||||
@ -20,18 +20,22 @@ aliases:
|
||||
- /blog/qmk-vortex-core
|
||||
---
|
||||
|
||||
Last fall, I [purchased my first mechanical keyboard](/blog/2020/11/06/vortex-core), the [Vortex Core](https://mechanicalkeyboards.com/shop/index.php?l=product_detail&p=3550), and have been loving it ever since. Well, almost loving it. There are a few "quirks" of the keyboard that I wasn't super fond of, like: occasionally not sending `KEY_UP` commands back to the computer, or the badly documented and maintained system for building custom layouts.
|
||||
Last fall, I [purchased my first mechanical keyboard](@/blog/2020-11-06-Vortex-Core.md), the [Vortex Core](https://mechanicalkeyboards.com/shop/index.php?l=product_detail&p=3550), and have been loving it ever since. Well, almost loving it. There are a few "quirks" of the keyboard that I wasn't super fond of, like: occasionally not sending `KEY_UP` commands back to the computer, or the badly documented and maintained system for building custom layouts.
|
||||
|
||||
In my previous post on this keyboard, I had mentioned @ChaoticEnigma's fork of [QMK](https://github.com/qmk/qmk_firmware) for the core. This custom firmware had been sitting on my mind for a while, and I finally decided to try it out on my keyboard. This post will cover the process of loading QMK on to a non-supported Vortex Core keyboard.
|
||||
|
||||
The following are all the steps required to complete this process. Make sure to **read them all before getting started**. As per usual when I am outlining ways to modify hardware, you might brick your keyboard doing this so: *be careful*.
|
||||
|
||||
1. [Compiling the toolchain](#compiling-the-toolchain)
|
||||
2. [Compiling the firmware](#compiling-the-firmware)
|
||||
3. [Finding debugging hardware](#finding-debugging-hardware)
|
||||
4. [Connecting to the core's JTAG interface](#connecting-to-the-core-s-jtag-interface)
|
||||
5. [Unlocking the keyboard](#unlocking-the-keyboard)
|
||||
6. [Flashing QMK](#flashing-qmk)
|
||||
<!-- no toc -->
|
||||
- [Compiling the toolchain](#compiling-the-toolchain)
|
||||
- [OpenOCD](#openocd)
|
||||
- [Pok3rtool](#pok3rtool)
|
||||
- [Intermediary firmware](#intermediary-firmware)
|
||||
- [Compiling the firmware](#compiling-the-firmware)
|
||||
- [Finding debugging hardware](#finding-debugging-hardware)
|
||||
- [Connecting to the core's JTAG interface](#connecting-to-the-core-s-jtag-interface)
|
||||
- [Unlocking the keyboard](#unlocking-the-keyboard)
|
||||
- [Flashing QMK](#flashing-qmk)
|
||||
|
||||
## Compiling the toolchain
|
||||
|
||||
|
||||
@ -94,4 +94,4 @@ The entire configuration process is outlined in the Dire Wolf [user manual](http
|
||||
|
||||
## Need help?
|
||||
|
||||
If you happened to follow this guide and need more configuration help, [send me a message](/about).
|
||||
If you happened to follow this guide and need more configuration help, [send me a message](/contact).
|
||||
|
||||
@ -130,7 +130,7 @@ Here is the new and improved list of my project ideas that never saw the light o
|
||||
- `amprdns`
|
||||
- An alternate DNS service, only avalible to 44net hosts
|
||||
- `betaroute`
|
||||
- A peer-to-peer routing tool (example implementation of [this RFC](/rfc/modern-repeater-linking))
|
||||
- A peer-to-peer routing tool
|
||||
- `MiwuStickers`
|
||||
- A custom sticker pack
|
||||
- `shoot-to-interact`
|
||||
|
||||
@ -11,7 +11,7 @@ aliases:
|
||||
- /blog/personal-pbx
|
||||
---
|
||||
|
||||
Over the past few months, I have built my own [internet backbone router](/blog/amprnet-bgp) (and an [internet exchange](https://ffixp.net)). So logically, the next step is to branch off into telephony... *right?*
|
||||
Over the past few months, I have built my own [internet backbone router](@/blog/2021-11-14-amprnet-bgp.md) (and an [internet exchange](https://ffixp.net)). So logically, the next step is to branch off into telephony... *right?*
|
||||
|
||||
Eh, even if I never get any practical use out of any of this in the end, at least its content for the blog.
|
||||
|
||||
|
||||
@ -11,6 +11,6 @@ aliases:
|
||||
- /blog/ferris-sweep
|
||||
---
|
||||
|
||||
After getting myself in to the world of customized mechanical keyboards with my [vortex core](/blog/2020-11-6-vortex-core) two years ago, I have proceeded to dive further into the hobby by [modifying keyboard firmware](/blog/qmk-vortex-core) and eventually building myself a TG4X for daily use. The TG4X has been a great keyboard, and my muscle memory has completely switched over to the quirks of using a 40% layout in daily use.
|
||||
After getting myself in to the world of customized mechanical keyboards with my [vortex core](@/blog/2020-11-06-Vortex-Core.md) two years ago, I have proceeded to dive further into the hobby by [modifying keyboard firmware](@/blog/2021-03-14-QMK-Vortex-Core.md) and eventually building myself a TG4X for daily use. The TG4X has been a great keyboard, and my muscle memory has completely switched over to the quirks of using a 40% layout in daily use.
|
||||
|
||||
<!-- Of course, I shall not settle for a whole 45 keys on my keyboard, **we must go smaller!**. Thus, I have built my very own customised [ferris sweep](#) -->
|
||||
|
||||
@ -139,4 +139,3 @@ Try it yourself!
|
||||
mtr -rwc 1 rickroll.as204466.va3zza.com
|
||||
```
|
||||
|
||||
For more AS204466 projects, view [my networking page](/as204466).
|
||||
|
||||
@ -15,6 +15,6 @@ aliases:
|
||||
- /blog/as398057
|
||||
---
|
||||
|
||||
Last year, I [dipped my toes in BGP](/blog/amprnet-bgp) while learning how to set up the infrastructure needed to route a public IPv4 address prefix to the world. A lot has changed since then, and I have fallen further into the world of network engineering and backbone routing.
|
||||
Last year, I [dipped my toes in BGP](@/blog/2021-11-14-amprnet-bgp.md) while learning how to set up the infrastructure needed to route a public IPv4 address prefix to the world. A lot has changed since then, and I have fallen further into the world of network engineering and backbone routing.
|
||||
|
||||
At the time of writing my last post, I had been singlehomed on [Vultr](https://www.vultr.com/)'s network via their *byoip* (Bring Your Own IP) plan, and was peering with them using one of their private ASNs.
|
||||
|
||||
@ -16,7 +16,7 @@ aliases:
|
||||
- /blog/personal-ases
|
||||
---
|
||||
|
||||
As a [network operator](/network), I keep a fairly close eye on what my peers are up to. This is mainly to make sure nobody is doing something *too* stupid near my network, but also just out of curiosity. Its nice to know what other people are up to, both as a sanity check on my own network, and as a view into new things I could try out.
|
||||
As a network operator, I keep a fairly close eye on what my peers are up to. This is mainly to make sure nobody is doing something *too* stupid near my network, but also just out of curiosity. Its nice to know what other people are up to, both as a sanity check on my own network, and as a view into new things I could try out.
|
||||
|
||||
I was recently inspired by [Hurricane Electric](https://he.net/)'s webpage that provides [statistics on IPv6 adoption](https://bgp.he.net/ipv6-progress-report.cgi) to create a website to display info about personal [Autonomous System Numbers](https://en.wikipedia.org/wiki/Autonomous_system_(Internet)). This site both caught my interest due to being a pretty raw plain-text website (can you tell, I like simple webpages?), and due to containing a ton of interesting information.
|
||||
|
||||
@ -73,4 +73,3 @@ All of this data comes from a cron job of mine. Check out the live data on my AS
|
||||
|
||||
[as-stats.ewpratten.com](https://as-stats.ewpratten.com/) (see also: [archived version](https://web.archive.org/web/as-stats.ewpratten.com/))
|
||||
|
||||
To read more about my own network, see [my networking page](/network).
|
||||
|
||||
@ -16,7 +16,7 @@ aliases:
|
||||
- /blog/ampr-vultr-bgp
|
||||
---
|
||||
|
||||
Since I briefly [waved my hands over this topic](/blog/amprnet-bgp/) last year, I have gotten many emails and DMs from fellow amateur radio operators asking for help announcing their own `/24`s to the world.
|
||||
Since I briefly [waved my hands over this topic](@/blog/2021-11-14-amprnet-bgp.md) last year, I have gotten many emails and DMs from fellow amateur radio operators asking for help announcing their own `/24`s to the world.
|
||||
|
||||
This post is aimed at existing operators of AMPRNet who wish to BGP announce a `/24` or larger of IPv4 space from a Virtual Private Server (VPS). The VPS provider I have chosen for this process is [Vultr](https://www.vultr.com/?ref=8932365), since they are highly recommended in the AMPRNet community and have free BGP sessions for their machines upon request.
|
||||
|
||||
|
||||
@ -18,11 +18,12 @@ aliases:
|
||||
It recently occurred to me that [Obsidian](https://obsidian.md) is capable of editing *any* type of markdown document store, not just its own note "Vaults". So, as a test I've been using it to interface with the source files that make up this website.
|
||||
|
||||
This post largely exists for the sake of figuring out how Obsidian behaves when forced into an environment that doesn't entirely agree with the "obsidian way of doing things".
|
||||
[test link](@/blog/2023-07-07-ampr-vpn.md)
|
||||
|
||||
---
|
||||
- Editing extra field is hard
|
||||
- Hot reload works very nicely (with auto-save when typing!)
|
||||
- Editing properties is pretty nice
|
||||
- Graph is very good
|
||||
-
|
||||
- Handling Zola @-links
|
||||
- Plugin hot-reload
|
||||
-
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user