Forem: Armstrong

Install and setup WireGuard VPN client on Ubuntu

Armstrong — Thu, 19 Dec 2024 16:41:57 +0000

Follow these steps to install and setup WireGuard VPN client on Ubuntu

Install the WireGuard VPN client

To install the VPN client, you need to run the following command

sudo apt install wireguard

Install ResolvConf

WireGuard relies on resolvconf to manage DNS settings when bringing up the VPN interface

sudo apt install resolvconf -y

Restart the resolveconf service

sudo systemctl restart resolvconf.service

Setup the VPN Configuration file

Move the VPN configuration files to the wireguard directory: /etc/wireguard

mv <location of config file>/<config_file.conf> /etc/wireguard/<config_file.conf>

💡 Ensure that the configuration file has a valid name. That is, no special characters only alpha-numeric characters are allowed. For example: my_vpn or my-vpn is not a valid file name. Instead use myVPN or myvpn or vpn001

Start up the WireGuard interface using the configuration file:

Change your directory to /etc/wireguard

sudo wg-quick up <config_file_name>

Replace <config_file_name> with the actual name of your configuration file (without the .conf extension). For example, if your file is myvpn.conf, the command would be:

sudo wg-quick up myvpn

You can stop the WireGuard VPN client by running the command: wq-quick down

Verify that the VPN client is running:

sudo wg

To stop the WireGuard VPN, run the following commands

sudo wg-quick down <config_file_name>

You should get a similar output as shown in the screenshot attachment below:

If you followed this tutorial to this point and you get the above result, pat your self on the back. You’ve made it. Now share this to others. Bis später!

Why the R1 Rabbit OS Device Isn't Worth the Hype

Armstrong — Mon, 17 Jun 2024 12:39:41 +0000

The debut of the R1 device promised a revolutionary gadget that could understand its owner and automate mundane visual tasks, a feature touted as a significant leap in mobile technology. When I pre-ordered the R1 device in January 2024, I had high expectations, fuelled by the considerable hype surrounding it. However, after receiving my order in June 2024, I found myself disappointed as the device fell short of my expectations. Below, I highlight key reasons why the Rabbit R1 device may not be the best choice for everyone, hoping to aid you in making an informed purchasing decision.

Limited Conversation Duration

Activating the voice prompt on the R1 device involves pressing and holding a button on the right-hand side. While this seems straightforward, the dual-purpose nature of this button—as both a voice activation and power button—results in a frustratingly short conversation window. Hold the button too long, and the device powers off, cutting off your interaction. Though there is an option to use an on-screen keyboard and images to communicate with the AI, this defeats the purpose of the device, as these tasks can be performed just as easily on a standard mobile device.

Limited App Connections

The R1 connects to apps like Spotify through its Large Action Model (LAM), which Rabbit describes as a method for the device to navigate and perform actions within apps based on user requests. This innovation aims to make the R1 more than just an information retrieval tool. However, the device currently supports only four apps: Uber for food, Spotify, DoorDash, and MidJourney. While Rabbit promises the ability to teach the device to use any app, the current limited app support significantly diminishes its value.

Device Color

Color plays a significant role in user experience, influencing emotions and behavior. The R1 device comes in red, a color that, while impactful, is not ideal for prolonged and diverse use due to its stimulating effects. Colors that promote calmness and clarity, such as blues and greens, would have been more appropriate, enhancing focus and comfort. While I was willing to overlook this in hopes that the device’s other benefits would outweigh my concerns, it unfortunately did not.

AI Issues

The AI in the R1 device is far from novel. There are instances where the AI fails to respond or leaves the user clueless about ongoing processes. This often happens when the AI doesn’t understand the context or specific words. Although the device sometimes indicates when it hasn’t understood a query, there are many occasions where no feedback is provided, leading to a poor user experience. Additionally, the R1 lacks GPS and navigation capabilities and performs basic tasks like setting reminders and sending emails poorly. The necessity of being online 24/7 to use the R1 is another significant drawback.

Poor Battery Life

The R1 device’s battery life is unimpressive. For a device primarily using voice prompts, I expected a longer battery life. However, I found that the battery depletes quickly even when the device is idle. For instance, after leaving the device unused overnight, it was completely drained by the next morning despite starting at 100% charge.

No USB Charging Cable

Another disappointing aspect was the lack of a USB charger and cable in the package. While this might have been a trade-off for a cheaper device, including a charger, even at an additional cost, would have been more user-friendly and cost-effective for the end user.

Confusing User Interface

The R1 device’s user interface is confusing and not user-friendly. The lack of a comprehensive user manual exacerbates this issue, leading to a frustrating user experience. The interfaces introduced by the R1 team are not intuitive, making navigation and usage more complicated than necessary.

In summary, while the R1 Rabbit OS device promised innovation, it falls short in several critical areas. Its limited conversation duration, poor app connectivity, unsuitable color choice, unreliable AI performance, lack of basic features, inadequate battery life, absence of essential accessories, and confusing user interface collectively contribute to a disappointing user experience. Potential buyers should carefully consider these drawbacks before purchasing the R1 device. The r1 device seems futuristic, but in my own honest opinion, it isn’t worth your time. Life with the r1 should be awesome, but it is a mess.

How to install and uninstall Davinci Resolve using Terminal on Linux

Armstrong — Fri, 08 Sep 2023 06:44:25 +0000

Are you struggling to install/uninstall Davinci resolve on Linux OS? This article will help you do just that. It has been written to be concise and clear and I would be worth your time.

What is Davinci Resolve?

According to the official website:

DaVinci Resolve is the world’s only solution that combines editing, color correction, visual effects, motion graphics and audio post production all in one software tool! Its elegant, modern interface is fast to learn and easy enough for new users, yet powerful for professionals. DaVinci Resolve lets you work faster and at a higher quality because you don’t have to learn multiple apps or switch software for different tasks. That means you can work with camera original quality images throughout the entire process. It’s like having your own post production studio in a single app! Best of all, by learning DaVinci Resolve, you’re learning how to use the exact same tools used by Hollywood professionals!

To learn more about the software, you can visit their official website here
For demonstration purpose, I will be using Kali Linux to show you how to install/uninstall Davinci resolve.The steps shown here should work on any Debian Linux system.

How to install Davinci Resolve

To install Davinci Resolve, navigate to their website here.
You should find a download button. Click the download button. You have to select the download based on the Operating System you are using. In this case, select the Linux operating system.
You might be presented with a registration form. Which is fine. Just fill out all the required fields with the appropriate information.
Once you are done filling the form, you can click the submit button and the download will begin automatically.

The application version at the time of writing is version 18 and the application size is 2.1GiB. So you should have enough disk space to cater for it.

Once you have downloaded it, you will need navigate to the download folder and extract the downloaded archive. Open your terminal using ctrl+alt+t or from the application launcher, search for the terminal program. Navigate to the download location. We will be using unzip command-line tool to extract the archive.

unzip DaVinci_Resolve_18.x.x_Linux.zip

To install the application, follow the steps below:

Once you are there, you need to write the following command as a root user to install Davinci Resolve

sudo ./DaVinci_Resolve_18.x.x_Linux.run -i

Once the command completes, it should create a desktop entry where you can launch your application. That's it! :)

How to uninstall Davinci Resolve

To uninstall Davinci Resolve, still in the extracted archive location, write the following commands:

sudo ./DaVinci_Resolve_17.1.1_Linux.run -u

That's it!

if you found this article helpful, don’t forget to like, follow, share and recommend this article to your friends and colleagues. Until we see again. :)

How to setup path aliases in Vite 2,3 & Typescript

Armstrong — Thu, 10 Aug 2023 04:31:22 +0000

As of August 2023, this approach still works with Vite version 2 and 3. So whenever I mention Vite, I am referring to the version 2 and 3. Let me know if you encounter any problems in the comment section.

Have you ever thought of how to get rid of imports resembling ../../assets/* or ../../../assets/* in your vite project? Well, this article will help you to do just that.

Reasons for Usage

Simplify referencing the project root.
Address module resolution errors when modifying files in directories.
Satisfy your curiosity

Alias Setup

In this guide, I'll use the alias @ to denote the project root. This approach is demonstrated using a React project scaffolded with Vite. The technique can be applied to Vue, AngularJS, or other frameworks supporting TypeScript. Learn how to scaffold a Vite app here.

Follow these steps to set up path aliases for TypeScript and Vite:

Steps to Follow

Open your project's tsconfig.json file.
Inside the compilerOptions section, add:

   "baseUrl": "src",
   "paths": {
       "@/*": ["./*"]
   }

This informs TypeScript to map module names matching the @/* pattern to src/* at runtime. Note that paths are resolved relative to the baseUrl value of the project.

Update your Vite configuration (vite.config.ts) as follows:

   import { defineConfig } from "vite";
   import { resolve } from "path";

   export default defineConfig({
       // ... other configurations
       resolve: {
           alias: {
               "@": resolve(__dirname, "src")
           }
       }
   });

Ensure you've installed @types/node for improved type checking.

Before:

   import { useState } from "react";
   import reactLogo from "./asset/react.svg";
   import "./App.css";

After:

   import { useState } from "react";
   import reactLogo from "@/asset/react.svg";
   import "@/App.css";

Your application should continue functioning correctly. Feel free to explore other options. If this guide was useful, let me know by commenting, sharing and giving a thumbs up.