Rename /images to /img

This commit is contained in:
Anthony Wang 2022-05-02 10:35:34 -05:00
parent d3c81489d9
commit 2f6bba3191
Signed by untrusted user: a
GPG key ID: BC96B00AEC5F2D76
57 changed files with 39 additions and 39 deletions

View file

@ -20,6 +20,6 @@ export QT_QPA_PLATFORM=wayland
Now enjoy your super unbloated standalone compositing Wayland window manager with `kwin_wayland konsole`. Need XWayland? To add that extra bloat, just pass the `--xwayland` flag.
![KWin standalone](/images/kwin-standalone.png)
![KWin standalone](/img/kwin-standalone.png)
All set! Now you can flex your very unbloated WM in all of its glory. It's Wayland, too! Now try getting some work done...

View file

@ -13,17 +13,17 @@ It's the day! Plasma 5.21 is out!
First, let me flex my `neofetch` to answer all your burning questions about my OS:
![neofetch](/images/neofetch.png)
![neofetch](/img/neofetch.png)
Now, time for the update. The big one. The closest thing to a point update in a rolling release. And...
![yay](/images/yay.png)
![yay](/img/yay.png)
Lots of updates, but Plasma 5.21 is not one of them.
Digging a bit deeper, it looks like it's still in [testing](https://wiki.archlinux.org/index.php/Official_repositories#Testing_repositories). Looks like we need to enable it first. Hopefully my computer doesn't explode or something when I do this...
![yay with testing](/images/yay-testing.png)
![yay with testing](/img/yay-testing.png)
There we go! Looks like Linux 5.11 is part of this sweet deal too! Let's break our rolling release! I mean, what could go possibly wrong? It's *only* 1263.42 MiB of packages. And I don't have a backup ready. Great!
@ -31,31 +31,31 @@ A few minutes and a reboot later...
OK, the boot looks good, no black screens or anything. Plasma (looks like the X11 session got renamed from Plasma to Plasma X11) on X started up extra fast... and we're in!
![Plasma 5.21](/images/plasma-5.21.png)
![Plasma 5.21](/img/plasma-5.21.png)
Some first impressions: The new Breeze Twilight theme looks awesome! I love hybrid light-dark themes! The application launcher is also organized a lot better now.
![The new system monitor](/images/system-monitor.png)
![The new system monitor](/img/system-monitor.png)
The system monitor app looks pretty good too and seems infinitely customizable, although wasn't the old Ksysguard working just fine? Whatever.
![The firewall configuration settings](/images/firewall.png)
![The firewall configuration settings](/img/firewall.png)
Now for the new firewall configuration settings... looks like I need to install a firewall first! A few minutes later... what a nice place to insert a giant picture of Konqi! Moving on.
The settings app has generally been cleaned up some more. There's a few other new settings, such as software updates, where I can now enable automatic updates to break my rolling release! How nice!
![New Application Launcher](/images/plasma-5.21-app-launcher.png)
![New Application Launcher](/img/plasma-5.21-app-launcher.png)
The biggest disappointment is the new Application Launcher. While I think it is a bit better organized, it's also less keyboard-friendly. Previously, after doing a search, you could press the down key once to select the second option shown. Now, you need to press the down key *twice*, injecting extra keystrokes in an area where keystroke efficiency is key (no pun intended).
Now for some Wayland...
![Plasma 5.21 Wayland](/images/plasma-5.21-wayland.png)
![Plasma 5.21 Wayland](/img/plasma-5.21-wayland.png)
Of course. The screen scaling is all wacko when I try to scale apps up 1.5x. Native Wayland apps look perfectly fine, but everything else, including much of Plasma, still looks pretty bad. Apparently it's a result of [this bug](https://bugs.kde.org/show_bug.cgi?id=389191) and it looks like two years later, it still hasn't been resolved yet.
![Plasma crash](/images/plasma-crash.png)
![Plasma crash](/img/plasma-crash.png)
And finally, we got a crash! Hooray! Just like last time I tried Wayland. Looks like the next update will be the one where Wayland is finally usable?

View file

@ -11,7 +11,7 @@ tags: ["Linux", "KDE"]
A few days ago, I wanted to record my screen, and in process, I discovered [this bug](https://bugs.kde.org/show_bug.cgi?id=417575). It doesn't seem like a very complicated bug, right? Just look through the code, find out what's wrong, and send in a pull request! Or is it that easy?
![The bug](/images/spectacle.png)
![The bug](/img/spectacle.png)
The first issue is that [Spectacle's code](https://invent.kde.org/graphics/spectacle) is not exactly the most readable code out there, but I was able to identify [line 209 in `GUI/KSMainWindow.cpp`] as the critical line. So what is `mScreenrecorderToolsMenuFactory` and what does `fillMenuFromGroupingNames` do?
@ -62,7 +62,7 @@ Note that the top `com.obsproject.Studio` has different capitalization than `com
Great, so how do we fix it now? None of the KDE codebases are properly designed to be able to handle uppercase names like these, so this is bound to cause more problems in the future. One easy fix could be to convert the names to lowercase before calling the KService functions, but who knows how many bugs are currently plaguing KService because of this? I don't really want to meddle with KService so I think I'll create a pull request for KNewStuff.
![Fixed!](/images/spectacle-patched.png)
![Fixed!](/img/spectacle-patched.png)
Time to send in a [pull request](https://invent.kde.org/frameworks/knewstuff/-/merge_requests/115) (or merge request as they call it on GitLab)! The actual patch is tiny: just add a `.toLower()` on line 122 of `kmoretools/kmoretools.cpp`. So little for so much hard work!

View file

@ -7,7 +7,7 @@ tags: ["linux", "fun", "algorithms", "computer-science"]
---
![A stupid idea on Matrix](/images/install-every-arch-package-matrix.png)
![A stupid idea on Matrix](/img/install-every-arch-package-matrix.png)
Challenge accepted. Let's do it!
@ -232,15 +232,15 @@ Alright, let's reboot and check out our new and improved Arch Linux system!
The first obstacle that we encounter is that most display managers, with the exception of [LXDM](https://wiki.archlinux.org/title/LXDM), don't have a scrollbar for selecting the desktop session (Because when would you ever have that many sessions installed?). So, let's `sudo systemctl start lxdm` and choose one of the 44 desktop sessions to explore.
![A very bloated LXDM](/images/bloated-lxdm.webp)
![A very bloated LXDM](/img/bloated-lxdm.webp)
Surprisingly, KDE Plasma starts up pretty snappily, but 10 different background services also popped up in the system tray. Memory usage is pretty high, but what can you expect? We also have over 30 different terminals to choose from for our `neofetch` screenshot.
![A very bloated KDE](/images/bloated-kde.webp)
![A very bloated KDE](/img/bloated-kde.webp)
Now let's have some real fun with this system:
![All apps](/images/all-apps.webp)
![All apps](/img/all-apps.webp)
Endless fun!

View file

@ -9,15 +9,15 @@ tags: ["Linux", "Windows"]
*Originally posted on my [old blog](https://git.exozy.me/Ta180m/blog/src/branch/main/_posts/2020-12-25-linux-office.md)*
![LibreOffice hate](/images/libreoffice-hate.png)
![LibreOffice hate](/img/libreoffice-hate.png)
OK, LibreOffice may not be the most loved application out there, but it's enough for most people. I use LibreOffice even on Windows! However, there is one thing about it that bothers me: the hideous icons! At first, I thought it might be caused be anti-aliasing or my screen scaling (currently set at 1.5x so everything's not tiny) but nope! The icons stayed hideous no matter what I did. Finally, after a bit of digging around in the settings, I found the root cause:
![LibreOffice icon settings](/images/libreoffice-settings.png)
![LibreOffice icon settings](/img/libreoffice-settings.png)
Can you see it? The icon style was set to `Breeze`, which presumably uses bitmap icons, while I was in fact looking for the infinitely scalable `Breeze (SVG)` vector icons. Switching to vector icons did the trick, and now LibreOffice doesn't look hideous anymore! The question is, why is the default the ugly bitmap icons?
![LibreOffice icons](/images/libreoffice-icons.png)
![LibreOffice icons](/img/libreoffice-icons.png)
People bash LibreOffice all the time for its imperfect compatibility of Office documents, but the important thing to remember is that *LibreOffice is not Microsoft Office!* If LibreOffice had focused less on being a Office clone and more on developing its own unique features, it would probably be in a much better shape right now. Millions of people are still using the basically-abandoned OpenOffice in 2020!

View file

@ -13,7 +13,7 @@ Matrix is great. It's secure. it's decentralized. The perfect free and open sour
Well, there's a few problems with this vision of the future. The first? To put it simply, no one uses Matrix. OK, maybe 100000 people use it at most, but that's nothing compared to the tens of millions of Discord users. The Arch Linux Matrix room recently hit a major milestone: 10000 people. And it's the third largest Matrix room! A sad reminder about how small Matrix still is.
![A milestone](/images/arch-matrix-room.png)
![A milestone](/img/arch-matrix-room.png)
Arch's status as the third largest Matrix room should also send a message about Matrix's current demographics. Most of the top rooms are either cryptocurrency or Linux focused. So if you want to chat with smart people, hang out on Matrix! The thing about all conversations is that they devolve to the lowest common denominator of the participants involved, so Matrix conversations can get pretty degenerate sometimes, but nowhere as idiotic as Discord.
@ -21,7 +21,7 @@ There are occasional spammers, but large rooms usually have mods that will quick
Matrix also has a thriving developer community, and there's some great bot frameworks out there (maybe even better than Discord!) but most public rooms hate bots, so you'll probably get banned.
![A bot ban](/images/matrix-bot-ban.png)
![A bot ban](/img/matrix-bot-ban.png)
Well anyways, that's a brief overview of Matrix. It has all the ingredients of a great free and open source chat service: a large hosted server at matrix.org, the option to self-host, a great amount of developer tools, end-to-end encryption, and more. The only thing missing is the people. Until more people start using it, you'll be held hostage to the [network effect](https://en.wikipedia.org/wiki/Network_effect) of other chat services. We've been making some progress, such as the Arch room hitting 10k, but it's a long and difficult road ahead. The vision is there; whether it's possible to accomplish is being answered right now.

View file

@ -15,7 +15,7 @@ Let's start with the term "bloat". What does it even mean? Wikipedia offers a fe
What about package counts?
![Wise words](/images/package-count.png)
![Wise words](/img/package-count.png)
It's actually really easy to get a very low package count: just install Windows and you can brag about having zero packages installed. Beat that!

View file

@ -19,7 +19,7 @@ Yeah, if you were expecting something big, another huge leap forward, this updat
However, Plasma 5.22 did manage to shrink the clock on the panel, so it's now harder to read. Of course, the screenshot below still makes it seem big.
![The clock shrunk!](/images/clock.png)
![The clock shrunk!](/img/clock.png)
Also, there was a "Reboot to apply updates" icon in the system tray after every boot that started showing up, but the following commands fixed it. Warning: it will reboot your computer.

View file

@ -13,7 +13,7 @@ I've had a Wacom tablet for a long time now, but there's just never been a legit
Well everyone, I've finally found a great use for it. It's quite obvious, actually: Krita, KDE's finest drawing and painting app! The touchscreen and stylus do work, if you count working as having a terrible drawing experience on a cramped screen since Krita likes overwhelming you with its menus and dockers which also take up a ton of valuable screen real estate. Also, the slightly better control of the stylus you can get with an actual Wacom tablet really helps too. (My laptop's touchscreen, which also coincidentally happens to be made by Wacom, is crying right now.) Behold the terrible drawing I did with the touchscreen and stylus. It's really terrible, just saying.
![The horror!](/images/zebruh.png)
![The horror!](/img/zebruh.png)
OK, so why I am even using Krita in the first place? Well, since school's starting to wrap up now, I've suddenly had a lot more free time, perfect for exploring Krita with my sister! Anyways, here's some takeaways about Krita:
@ -29,5 +29,5 @@ OK, so why I am even using Krita in the first place? Well, since school's starti
Here's the horrible drawing I promised. It's horrible in so many different ways, just saying...
![The horror! Oh no!!](/images/llama.png)
![The horror! Oh no!!](/img/llama.png)

View file

@ -16,13 +16,13 @@ It's been over a week since I've completed my build and switched over many thing
### Remote desktop
![VNC](/images/vnc.png)
![VNC](/img/vnc.png)
VNC works perfectly. OK, fine, I haven't figured out clipboad sharing yet, but other than that, it's perfect. I also tried Xrdp but didn't have much luck. There's also X2Go which bundles some extra perks like sound and clipboard sharing, but the image quality is blurry at times. Oh well, VNC is better anyways!
### Nextcloud
![Nextcloud](/images/nextcloud.png)
![Nextcloud](/img/nextcloud.png)
Nextcloud is basically a huge hammer that tries to attack every nail. For most cases, a more specialized tool would be better, but Nextcloud can still give you a surprisingly functional solution to... file sharing, real-time collaborative document editing, photo management, chat, email client, contacts, calendar, music streaming, notes, tasks, forms, maps, Matrix client, and RSS client. So yeah, Nextcloud knocks down quite a few bowling pins with one gigantically overpowered bowling, or perhaps more accurately, wrecking ball.
@ -30,7 +30,7 @@ I anticipated a painful setup process for such a large monolith, but it went sur
### Gitea
![Gitea](/images/gitea.png)
![Gitea](/img/gitea.png)
Gitea is one of the most boring things I've ever self-hosted. It just simply works! All my problem solving skills are simply going to waste... And I still don't know how to pronounce that name...
@ -38,7 +38,7 @@ On a more serious note, I'm currently using it to mirror all my GitHub repositor
### QEMU/KVM
![Virtual Machine Manager connected to my home server](/images/vmm.png)
![Virtual Machine Manager connected to my home server](/img/vmm.png)
Awww yeah, my favorite long acronym! QEMU/KVM is awesome, but I didn't know it was *this awesome*! Now I can run all my virtual machines on my laptop, but actually on my home server, without my laptop's fans spinning up loudly!
@ -57,7 +57,7 @@ And don't get me started on `mx-puppet-discord`. It may have seemed like just a
### DIY cloud gaming
![SuperTuxKart, streamed from the "cloud"](/images/stk.png)
![SuperTuxKart, streamed from the "cloud"](/img/stk.png)
As crazy as it sounds, this is actually nearly usable! The only thing preventing this from working perfectly are my [terrible GPU](/posts/worst-first-build-part-4) and the limitations of VNC, since proprietary cloud gaming services use their own protocols optimized for low latency. I can get sound using X2Go, but it doesn't always work well. Plus X2Go's image quality is not the best. Still, we'll see how this goes, since it's pretty promising!

View file

@ -29,7 +29,7 @@ That said, for the small niche of self-hosting enthusiasts, it's fun, thrilling,
## So what now?
![Gitea](/images/gitea.png)
![Gitea](/img/gitea.png)
Well, Gitea actually provides us with a good step in the right direction. Gitea has a feature to *mirror* repositories from GitHub to your self-hosted instance, so it's not too difficult to mirror your entire GitHub user to Gitea. You can self host *and* reap the benefits of GitHub's [network effect](https://en.wikipedia.org/wiki/Network_effect) at the same time. And if your GitHub repos were ever to get taken down like [youtube-dl](https://github.com/github/dmca/pull/8127), you'll still have all the perks of self-hosting a mirror.

View file

@ -11,7 +11,7 @@ tags: ["Hardware"]
Last Wednesday, March 10th, was going to be *the day*. The day I finally could complete a functioning (but incomplete) build. My slightly overpriced RAM sticks (RAM prices were creeping upward sinisterly so I decided I probably shouldn't wait longer. Probably a bad move, too, but whatever.) were arriving, and it was going to be momentous. I was going to boot up an Arch USB drive, SSH in, and get the party going.
![A low-quality image of the build, sans RAM, courtesy of an terrible iPad camera](/images/build.jpg)
![A low-quality image of the build, sans RAM, courtesy of an terrible iPad camera](/img/build.jpg)
Yeah... that didnt exactly happen.
@ -69,4 +69,4 @@ It looks like my only options now are: asking more people to borrow their GPU, b
It's quite frustrating that the only obstacle in the way of finishing my build is a GPU for an hour. I guess I now have a $666 mega paperweight sitting in my living room. Perfect!
![Another low-quality image of the build](/images/build2.jpg)
![Another low-quality image of the build](/img/build2.jpg)

View file

@ -13,7 +13,7 @@ The [Great GPU Shortage](https://www.digitaltrends.com/computing/gpu-shortage-q3
But finish my build I did, with a GPU that ended up costing a grand total of... **$0**. (OK, maybe a dollar for the gas I used, but it was basically free.) How'd I do it? It's actually surprising simple.
![Easy free GPU](/images/free-gpu.png)
![Easy free GPU](/img/free-gpu.png)
1. Join a Discord with people in your area. (I normally don't recommend Discord since it's a privacy nightmare, but welp, [network effects!](https://en.wikipedia.org/wiki/Network_effect))

View file

@ -13,13 +13,13 @@ It's time to go full circle! I first started planning my build using [Logical In
Here's some anticlimactic images of the completed build:
![Image 1](/images/finished-build.jpg)
![Image 1](/img/finished-build.jpg)
![Image 2](/images/finished-build2.jpg)
![Image 2](/img/finished-build2.jpg)
![Image 3](/images/finished-build3.jpg)
![Image 3](/img/finished-build3.jpg)
![Image 4](/images/finished-build4.jpg)
![Image 4](/img/finished-build4.jpg)
Here's the writeup that I did for the build:

View file

@ -51,7 +51,7 @@ export DISPLAY=:0 # set the display
Here's SuperTuxKart in all its glory running in a container with full graphical acceleration!
![SuperTuxKart in a container](/images/nspawn-supertuxkart.png)
![SuperTuxKart in a container](/img/nspawn-supertuxkart.png)
And that's it! Now you have a fast, simple way to test GUI graphically accelerated apps without messing with your host OS. (I still haven't gotten sound to work yet, but it shouldn't be *that* hard...)

View file

Before

Width:  |  Height:  |  Size: 3.8 MiB

After

Width:  |  Height:  |  Size: 3.8 MiB

View file

Before

Width:  |  Height:  |  Size: 106 KiB

After

Width:  |  Height:  |  Size: 106 KiB

View file

Before

Width:  |  Height:  |  Size: 149 KiB

After

Width:  |  Height:  |  Size: 149 KiB

View file

Before

Width:  |  Height:  |  Size: 3.2 MiB

After

Width:  |  Height:  |  Size: 3.2 MiB

View file

Before

Width:  |  Height:  |  Size: 70 KiB

After

Width:  |  Height:  |  Size: 70 KiB

View file

Before

Width:  |  Height:  |  Size: 216 KiB

After

Width:  |  Height:  |  Size: 216 KiB

View file

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 20 KiB

View file

Before

Width:  |  Height:  |  Size: 108 KiB

After

Width:  |  Height:  |  Size: 108 KiB

View file

Before

Width:  |  Height:  |  Size: 112 KiB

After

Width:  |  Height:  |  Size: 112 KiB

View file

Before

Width:  |  Height:  |  Size: 8.8 KiB

After

Width:  |  Height:  |  Size: 8.8 KiB

View file

Before

Width:  |  Height:  |  Size: 130 KiB

After

Width:  |  Height:  |  Size: 130 KiB

View file

Before

Width:  |  Height:  |  Size: 2.5 MiB

After

Width:  |  Height:  |  Size: 2.5 MiB

View file

Before

Width:  |  Height:  |  Size: 2.9 MiB

After

Width:  |  Height:  |  Size: 2.9 MiB

View file

Before

Width:  |  Height:  |  Size: 2.4 MiB

After

Width:  |  Height:  |  Size: 2.4 MiB

View file

Before

Width:  |  Height:  |  Size: 2.4 MiB

After

Width:  |  Height:  |  Size: 2.4 MiB

View file

Before

Width:  |  Height:  |  Size: 562 KiB

After

Width:  |  Height:  |  Size: 562 KiB

View file

Before

Width:  |  Height:  |  Size: 50 KiB

After

Width:  |  Height:  |  Size: 50 KiB

View file

Before

Width:  |  Height:  |  Size: 270 KiB

After

Width:  |  Height:  |  Size: 270 KiB

View file

Before

Width:  |  Height:  |  Size: 48 KiB

After

Width:  |  Height:  |  Size: 48 KiB

View file

Before

Width:  |  Height:  |  Size: 114 KiB

After

Width:  |  Height:  |  Size: 114 KiB

View file

Before

Width:  |  Height:  |  Size: 19 KiB

After

Width:  |  Height:  |  Size: 19 KiB

View file

Before

Width:  |  Height:  |  Size: 27 KiB

After

Width:  |  Height:  |  Size: 27 KiB

View file

Before

Width:  |  Height:  |  Size: 212 KiB

After

Width:  |  Height:  |  Size: 212 KiB

View file

Before

Width:  |  Height:  |  Size: 4.9 MiB

After

Width:  |  Height:  |  Size: 4.9 MiB

View file

Before

Width:  |  Height:  |  Size: 142 KiB

After

Width:  |  Height:  |  Size: 142 KiB

View file

Before

Width:  |  Height:  |  Size: 110 KiB

After

Width:  |  Height:  |  Size: 110 KiB

View file

Before

Width:  |  Height:  |  Size: 770 KiB

After

Width:  |  Height:  |  Size: 770 KiB

View file

Before

Width:  |  Height:  |  Size: 492 KiB

After

Width:  |  Height:  |  Size: 492 KiB

View file

Before

Width:  |  Height:  |  Size: 45 KiB

After

Width:  |  Height:  |  Size: 45 KiB

View file

Before

Width:  |  Height:  |  Size: 114 KiB

After

Width:  |  Height:  |  Size: 114 KiB

View file

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 1.2 MiB

View file

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 1.2 MiB

View file

Before

Width:  |  Height:  |  Size: 33 KiB

After

Width:  |  Height:  |  Size: 33 KiB

View file

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

View file

Before

Width:  |  Height:  |  Size: 48 KiB

After

Width:  |  Height:  |  Size: 48 KiB

View file

Before

Width:  |  Height:  |  Size: 1.1 MiB

After

Width:  |  Height:  |  Size: 1.1 MiB

View file

Before

Width:  |  Height:  |  Size: 206 KiB

After

Width:  |  Height:  |  Size: 206 KiB

View file

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

View file

Before

Width:  |  Height:  |  Size: 722 KiB

After

Width:  |  Height:  |  Size: 722 KiB

View file

Before

Width:  |  Height:  |  Size: 119 KiB

After

Width:  |  Height:  |  Size: 119 KiB

View file

Before

Width:  |  Height:  |  Size: 117 KiB

After

Width:  |  Height:  |  Size: 117 KiB

View file

Before

Width:  |  Height:  |  Size: 723 KiB

After

Width:  |  Height:  |  Size: 723 KiB