update page
This commit is contained in:
speedie
parent
ce34e0bf07
commit
33244631c3
53
articles/post33.php
Normal file
53
articles/post33.php
Normal file
|
|
@ -0,0 +1,53 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<?php include '../php/header.php';?>
|
||||
<title>Why I don't support RiiConnect24. </title>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="description" content="RiiConnect24 is not what it seems. Most Nintendo Wii hackers sort of look up to the RiiConnect24 team and why not? They're the face of many modern Wii projects. They however are doing some pretty sketchy things such as violating copyleft free software licenses.">
|
||||
<meta name="author" content="speedie">
|
||||
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
||||
</head>
|
||||
<body>
|
||||
<div class="content">
|
||||
<h2>Why I don't support RiiConnect24.</h2>
|
||||
<h4>2022-05-20</h4>
|
||||
<p>As you may be familiar with if you've been following me for a while, I usually cover free software and/or minimalism. Today however, it's going to be a little different. This time it's Nintendo Wii related. If you're only here for free software, you can just skip this post but for people who are a part of <a href="/ff.html">Forwarder Factory</a> or simply found my post elsewhere, this is probably worth the read.</p>
|
||||
<p>For those who aren't into Wii but still wanna follow along for.. some reason, RiiConnect24 is a team of people behind Wii restoration, preservation and other popular projects. This blog post of mine explains why I'm against them and dislike their actions.</p>
|
||||
<h4>Disclaimer</h4>
|
||||
<p>I would also like to add, just in case this blog post of mine becomes remotely popular, please do NOT go ahead and hate on RiiConnect24. Despite the ethical flaws that will be shown, they really do not deserve it and you're not helping me by doing so. Please DO contact them and try to help them fix the mentioned issues however. Despite the claims I'm about to make and the facts, RiiConnect24 is behind great projects like the revived Nintendo Channels but this does NOT allow them to violate free software copyleft licenses among other things.</p>
|
||||
<p>RiiConnect24 is not what it seems. Most Nintendo Wii hackers sort of look up to the RiiConnect24 team and why not? They're the face of many modern Wii projects such as the revived official Nintendo channels, WiiMod Lite, and the 'wii.guide' website which at first seems fairly innocent. In fact, I've had that exact same opinion on them for a long time. I simply saw them as 'modern' Wii hackers.</p>
|
||||
<h4>Violating the GNU General Public License v2</h4>
|
||||
<p>This was never a big issue (well it is but no one actually noticed) but one RC24 project called 'WiiMod Lite' violates the GNU GPLv2 license. Many months ago, an Issue was created on the GitHub by user <strong>jornmann</strong> named 'Potential GPLv2 License Violation'.</p>
|
||||
<p>As you can probably guess, WiiMod Lite violates the GNU GPLv2 license of WiiMod Lite which is <i>based on Yet Another Wad Manager Mod</i> which is <i>based on WAD Manager 1.7. Of course, waninkoko chose to license his software, WAD Manager <i>(1.7)</i> under GPLv2.</i>.</p>
|
||||
<p>TLDR; If a project licensed under the GPLv2 license is forked, the fork cannot have its license changed. This means a fork can also not be proprietary. This is the part <a href="https://github.com/riiconnect24/wiimodlite">WiiMod Lite</a> violates. No matter what you think about non-free software, this is not okay and the original author of WiiMod Lite clearly picked this license because they are (as good people should be) against proprietary software.</p>
|
||||
<h5>jornmann: GPLv2 requires the programs source to be disclosed and the license to be the same (GPLv2). WML is not licensed under GPLv2, and is proprietary. This is why it violates the license.</h5>
|
||||
<h5>Artuto: Well we are not the original author nor have the source code or even the ability to relicense ¯_(ツ)_/¯.</h5>
|
||||
<h5>jornmann: Then, as I've said before, contact the original author.</h5>
|
||||
<h5>larsenv: We've tried to get ahold of the original author (who is Chinese) to no avail. I even asked someone from China to help contact them on the forum that they visit (tvgzone), but they couldn't register because they couldn't get a confirmation email for their account. I wanted the source code, but it's not my fault that they didn't share the source code.</h5>
|
||||
<h5>jornmann: Well, that doesn't change the fact that you are still in violation of the GPLv2 license.</h5>
|
||||
<h5>Artuto: There is nothing we can do, we cannot just magically generate the source code.</h5>
|
||||
<p>I think it's pretty clear what they're doing. They're trying to repost this old but according to them 'great' WAD manager while POSSIBLY knowing that the developer isn't gonna care if they don't follow the license. And since the developer of the software is no longer around, RiiConnect gets ALL the credit because of course they uploaded the binary to their GitHub. Are you getting it yet?</p>
|
||||
<p>Finally, Their excuse for doing this is essentially 'we couldn't find the source code and can therefore do whatever we want with this project'. Not having source code is not an excuse and if you don't have the source code, you shouldn't be recommending it. Don't you think it's ironic how RiiConnect is all about using modern software that's actively being maintained yet they recommend a WAD manager which hasn't and won't be updated in years. In fact, looking at the closed Issues for the RC24 WML repo, you can see most issues were closed with a 'We or anyone can't do X because the source code is missing' notice.</p>
|
||||
<h4>wii.guide is very biased</h4>
|
||||
<p>Yep, and it doesn't stop there because RiiConnect24 also owns and maintains <a href="https://wii.guide">wii.guide</a> which is the guide recommended by nearly everyone in the <i>modern</i> Nintendo Wii Homebrew/hacking scene.</p>
|
||||
<p>I really dislike guides like this becoming popular because sure, it does mean there's <i>one guide that you can rely on that will be updated</i> but it also means that you can get a lot of people to use certain software for any reason. This is exactly what has happened with WiiMod Lite. The only reason I can think of as for why people use WiiMod Lite is that it's recommended by the guide and most new people read wii.guide anyway.</p>
|
||||
<p>Since I hacked my Wii before wii.guide was even a thing, I didn't even know this WAD manager existed before I actually read wii.guide years after hacking Wii consoles. I guess saying this is also sort of biased because it's my own experience however my point is that most people wouldn't be using WiiMod Lite if wii.guide wasn't recommending it.</p>
|
||||
<p>Now, before you think I'm just 'hating' to hate, I would like to mention that wii.guide existing is great. No longer do users have to worry about bricking their Wii because of a guide that hasn't been updated in 12 years telling you to install 20 cool awesome wads w/o Priiloader/BootMii@Boot2 but I wish wii.guide was less biased and offered alternatives to THEIR software so for example YAWWM instead of WiiMod Lite.</p>
|
||||
<p>If all they did was recommend RiiConnect24, I wouldn't mind because there really is no alternative to the RC24 services as of 2022.</p>
|
||||
<h4>Conclusion</h4>
|
||||
<p>So, after all of that ranting, what do I actually think of RiiConnect24?</p>
|
||||
<p>Well, I really like what RiiConnect is doing in terms of preservation and keeping Nintendo services up and running. This has given you a lot of respect among Wii users including myself. The problem is that this still doesn't allow you to completely ignore a license. It doesn't matter if the developer of X software is gone. If you don't have the source code, you're violating the license and should therefore not continue hosting X software.</p>
|
||||
<p>As for being biased, I can sort of excuse that, even though it is a problem because they can get anyone to use anything.</p>
|
||||
<p>However, wii.guide is still the only Wii guide worth using so really, I'd love to see it get improved.</p>
|
||||
<p>Finally, do I hate RiiConnect24? No, I believe the people who are working on their projects simply want the best for us however like I said, they've been doing some <i>sketchy</i> stuff so that's what this post was made for.</p>
|
||||
<p>I would like to thank you for reading this post,</p>
|
||||
<p>If you wanna make a change, consider sharing this post with the RiiConnect24 people so that they can improve the problems I've discussed. If you have any more problems with RiiConnect24 and/or the people behind it that you'd like to share then please do so by <a href="mailto:speedie@duck.com">sending me an email</a>.</p>
|
||||
<p>If you wanna support me and my work, consider <a href="/donate.html">donating anonymously here</a>.</p>
|
||||
<p>Thank you for reading and have a super based day!</p>
|
||||
</div>
|
||||
</body>
|
||||
<footer>
|
||||
<?php include '../php/footer.php';?>
|
||||
</footer>
|
||||
</html>
|
||||
2
blog.php
2
blog.php
|
|
@ -37,7 +37,7 @@
|
|||
<h5><a href="articles/post14.php">Why I switched license from MIT to GPLv3</a>, written on 2022-06-05 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="articles/post13.php">Open source: Fake freedom.</a>, written on 2022-06-05 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="articles/post12.php">I HATE APPLE!!!</a>, written on 2022-05-23 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="rc24.php">Why I don't support RiiConnect24.</a>, written on 2022-05-20 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="articles/post33.php">Why I don't support RiiConnect24.</a>, written on 2022-05-20 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="articles/post11.php">Smartphones are only smart because you're dumb.</a>, written on 2022-05-04 by <a href="index.php">speedie</a></h5>
|
||||
<h5><a href="articles/post10.php">xinit is bloated</a>, written on 2022-04-30 by <a href="index.php">speedie</a></h5>
|
||||
<h4>Archived blog articles/posts (articles/posts 1-9)</h4>
|
||||
|
|
|
|||
BIN
img/notif.png
Normal file
BIN
img/notif.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
BIN
img/rchat-tput.png
Normal file
BIN
img/rchat-tput.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.1 MiB |
BIN
img/rchat.png
Normal file
BIN
img/rchat.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 628 KiB |
BIN
img/rchatdebloater.png
Normal file
BIN
img/rchatdebloater.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.9 MiB |
BIN
img/rfarmi.png
Normal file
BIN
img/rfarmi.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.6 MiB |
25
projects/libspeedwm.php
Normal file
25
projects/libspeedwm.php
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<?php include '../php/header.php';?>
|
||||
<title>libspeedwm</title>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="description" content="libspeedwm is a minimal program for interacting with speedwm through the shell.">
|
||||
<meta name="author" content="speedie">
|
||||
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
||||
</head>
|
||||
<body>
|
||||
<div class="content">
|
||||
<h1>libspeedwm</h1>
|
||||
<p>libspeedwm is a minimal program for interacting with speedwm through the shell. It allows you to run signals but also perform actions. It is written in C because speedwm itself is written in C. It only has one dependency; libX11 used to set the root window name.</p>
|
||||
<h2>Why should I use libspeedwm?</h2>
|
||||
<p>While yes, you <em>can</em> run signals manually (speedwm -s "#cmd:10"), this is slightly risky. If speedwm gets updated and its signals get changed, your script will be using the old signals potentially breaking your script completely. libspeedwm solves this because libspeedwm can and will be updated alongside speedwm which means all of the actions are going to work on the latest version.</p>
|
||||
<h2>What are the downsides of libspeedwm?</h2>
|
||||
<p>This does come with a few downsides though. First is that libspeedwm will be a dependency for your script/project. It is an external dependency and is not bundled with speedwm itself.</p>
|
||||
<p>Secondly, if the user is on an old speedwm version, the libspeedwm version must also be old or scripts will break just the same as using signals normally. This comes with a huge problem: there are bugs in the old libspeedwm version.</p>
|
||||
</div>
|
||||
</body>
|
||||
<footer>
|
||||
<?php include '../php/footer.php';?>
|
||||
</footer>
|
||||
</html>
|
||||
108
projects/rchat.php
Normal file
108
projects/rchat.php
Normal file
|
|
@ -0,0 +1,108 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<?php include '../php/header.php';?>
|
||||
<title>rchat </title>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="description" content="rchat or rautafarmi chat is a command-line rautafarmi instance client with Vim keybinds written in Bash. rchat has color support, $EDITOR support, xshbar integration, and message logging support as well as .Xresources (xrdb) and notification support through patching.">
|
||||
<meta name="author" content="speedie">
|
||||
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
||||
</head>
|
||||
<body>
|
||||
<div class="content">
|
||||
<h1>rchat</h1>
|
||||
<p>rchat is a command-line rautafarmi instance client with Vim keybinds written in Bash. (also works in zsh)</p>
|
||||
<img src="../img/rchat.png" alt="image">
|
||||
<p>It is very customizable and is customized through editing with an editor.</p>
|
||||
<h1>Features</h1>
|
||||
<ul>
|
||||
<li>Vim keybinds</li>
|
||||
<p>rchat was designed with Vim keybinds in mind. To enter a message, you use Insert mode and Vim keybinds to navigate.</p>
|
||||
<li>Color support</li>
|
||||
<p>rchat has support for fancy colors. If you wanna change the colors it's really easy to do.</p>
|
||||
<li>Write text in $EDITOR</li>
|
||||
<p>"In addition to simply entering text, you can do :e and write text in your defined $EDITOR.</p>
|
||||
<li>xshbar integration</li>
|
||||
<p>rchat has integration with xshbar plugins. This means you can get messages on your status bar.</p>
|
||||
<li>Multiple-instance support</li>
|
||||
<p>rchat supports multiple instances including custom ones. Simply add one.</p>
|
||||
<li>Message logging</li>
|
||||
<p>rchat logs all messages in /tmp/rchat-history. This combines messages across multiple instances.</p>
|
||||
<li>Only messaging, not bloat</li>
|
||||
<p>rchat is written in Bash, making it easy to configure with any editor. If the default features aren't enough, you can download and patch in patches that you can find below..</p>
|
||||
</ul>
|
||||
<h1>Installation</h1>
|
||||
<p>To install rchat, If you run Arch Linux or any distributions based on it, you can simply get it from the AUR (although it may be slightly outdated). Package is maintained by nezbednik and as of 0.4, is fully up-to-date. If you use 'yay', run 'yay -S rchat'. Then you can just begin using it.</p>
|
||||
<p>If you run Gentoo Linux, you can add <a href="overlay.html">my overlay</a> using layman and then just emerge it. The ebuild is maintained by me so it should be up-to-date.</p>
|
||||
<p>I recommend installing it by cloning the repository.</p>
|
||||
<p><code>cd ~</code></p>
|
||||
<p><code>git clone https://codeberg.org/speedie/rchat</code></p>
|
||||
<p><code>cd rchat</code></p>
|
||||
<p><code>make install</code></p>
|
||||
<h1>Usage</h1>
|
||||
<p>See Installation, then simply run it in a terminal. To join the default instance, simply type ':j'.</p>
|
||||
<p>To set a different instance, type ':set instance' and then enter your instance. If the instance is invalid or you wanna set it back, type ':set instance default'.</p>
|
||||
<p>From here, you can read the documentation by typing ':help'.</p>
|
||||
<h1>Patches</h1>
|
||||
<p>rchat doesn't come with features I believe a lot of people won't use. If you need more, you can use the GNU 'patch' command with one of these .diff files below.</p>
|
||||
<h3>Xresources</h3>
|
||||
<p>This patch enables .Xresources support for rchat. It allows setting the following values:
|
||||
<ul>
|
||||
<li>rchat.color1</li>
|
||||
<li>rchat.color2</li>
|
||||
<li>rchat.color3</li>
|
||||
<li>rchat.color4</li>
|
||||
<li>rchat.color5</li>
|
||||
<li>rchat.color6</li>
|
||||
<li>rchat.instance</li>
|
||||
<li>rchat.refresh</li>
|
||||
<li>rchat.linecount</li>
|
||||
<li>rchat.sep (1.0 only)</li>
|
||||
</ul>
|
||||
<p>If you use rchat 0.5, use the 0.5 patch.</p>
|
||||
<p>If you use rchat 1.0 or 1.1, use the 1.0 patch.</p>
|
||||
<p>Simply apply as usual.</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-xresources-0.5.diff">rchat-xresources-0.5.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-xresources-1.0.diff">rchat-xresources-1.0.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-xresources-1.2.diff">rchat-xresources-1.2.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-xresources-1.3-r2.diff">rchat-xresources-1.3-r2.diff</a></h4>
|
||||
<h3>Notifications</h3>
|
||||
<img src="../img/notif.png" alt="image">
|
||||
<p>This patch enables support for notifications in rchat using 'notify-send'. Make sure to install 'libnotify-send' before using.</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-notification-0.5.diff">rchat-notification-0.5.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-notification-1.0.diff">rchat-notification-1.0.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-notification-1.3-r2.diff">rchat-notification-1.3-r2.diff</a></h4>
|
||||
<h3>Open URL</h3>
|
||||
<p>This patch adds a ':open' feature which opens the last URL displayed in your terminal.</p>
|
||||
<p>Really simple, but also extremely useful if you want to view links quickly.</p>
|
||||
<p>1.1 version likely compatible with 1.0!</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-openurl-1.1.diff">rchat-openurl-1.1.diff</a></h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-openurl-1.2.diff">rchat-openurl-1.2.diff</a></h4>
|
||||
<h3>Art</h3>
|
||||
<img src="../img/rfarmi.png" alt="image">
|
||||
<p>This patch adds support for art in rchat that runs before you join an instance. The art is placed in $HOME/.config/rchat/rchat_art and will run if present. The file can contain ANSI escape codes if you want colors.</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-art-1.2.diff">rchat-art-1.2.diff</a></h4>
|
||||
<h3>Tput colors</h3>
|
||||
<img src="../img/rchat-tput.png" alt="image">
|
||||
<p>This patch replaces the ANSI escape codes with tput commands. This allows for more colors and also allows you to separate your rchat color scheme from your terminal color scheme (Useful if you use Pywal).</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-tputcolors-1.3-r2.diff">rchat-tputcolors-1.3-r2.diff</a></h4>
|
||||
<h3>Hide status</h3>
|
||||
<img src="../img/rchatdebloater.png" alt="image">
|
||||
<p>This patch removes the rchat (vernum), separator and instance status from the chat area. This means messages are going to fill up the entire terminal window minus one line (used for the Insert mode).</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-hidestatus-1.41.diff">rchat-hidestatus-1.41.diff</a></h4>
|
||||
<h3>Insert mode is editor</h3>
|
||||
<p>This patch replaces insert mode (i) with :e (Editing the message in $EDITOR). This may be useful if you prefer to edit messages in an editor like Vim or Emacs or need multiple lines very often. You can still access the regular Insert mode by pressing e though.</p>
|
||||
<h4>Author: speedie</h4>
|
||||
<h4><a href="https://codeberg.org/speedie/rchat/raw/branch/patches/rchat-itoedit-1.41.diff">rchat-itoedit-1.41.diff</a></h4>
|
||||
</div>
|
||||
</body>
|
||||
<footer>
|
||||
<?php include '../php/footer.php';?>
|
||||
</footer>
|
||||
</html>
|
||||
Reference in a new issue