blued_gear

joined 7 months ago
sorted by: new top controversial old
6
LocalPiped: Packaged Piped to run locally (github.com)
 

As a regular user of Piped, it got very annoying when Google blocked almost all the public instances. As even Invidious is affected, I decided to run Piped on my local machine with my residential IP, so that it won't get blocked so easily.
To make the process of running such an instance as easy as possible for me and also other Piped enjoyers, I created LocalPiped, a project to deploy all the server components via AppImage.

You can download prebuild AppImages here.
For a description on how to make the database persistent, see the README in the Repository.

Please be aware, that most of the privacy-advantages do not apply anymore, as the application has to run via your own IP.
This also means that you might need split-tunneling if you use a VPN.

It is also possible, to use the application on an Android Phone:

  1. you need Termux
  2. in Termux, install PRoot Distro
  3. with PRoot Distro, install Fedora: proot-distro install fedora
  4. switch into Fedora: pd sh fedora
  5. update packages and install wget and java-21: dnf update; dnf install wget java-21-openjdk-headless
  6. download the AppImage: wget -O LocalPiped.appimage https://projects.chocolatecakecodes.goip.de/blued_gear/localpiped/-/package_files/16/download
  7. make it executable: chmod +x ./LocalPiped.appimage
  8. extract the contents of the AppImage (as it is not possible to use fuse in normal Termux): ./LocalPiped.appimage --appimage-extract && mv squashfs-root LocalPiped && rm LocalPiped.appimage
  9. run it: cd LocalPiped; ./AppRun
3
Bocchi BlueScreenOfDeath (cloud.disroot.org)
submitted 7 months ago* (last edited 7 months ago) by blued_gear@fedia.io to c/animemes@ani.social
0 comments fedilink
 

Some of you may heard about the new BSOD feature of Systemd.
But I sure you never had a BSOD which shows you in such a "sympathetic" way that your computer fucked up.

With my mod of systemd-bsod, instead of getting a QR-Code which helps you to find more info about the problem, your PC will just show you the middle-finger.
(The error-message is still displayed.)

The source of the animation is this GIF

View in Nextcloud

A meta-package to prevent out-of-sync mesa-freeworld in c/fedora@lemmy.ml
[–] blued_gear@fedia.io 1 points 7 months ago

I really have no idea.

Also I have to admit that my approach is quite conservative.
Not every mesa update may be incompatible with the freeworld packages, but my package holds them back until RPMFusion published an update themselves.

4
A meta-package to prevent out-of-sync mesa-freeworld (copr.fedorainfracloud.org)
 

Maybe some of you already had the problem: mesa-freeworld from RPM-Fusion can be out of sync with the standard mesa packages.
Once this led to a black screen after reboot for me.

So, I decided to create a metapackage which pins the versions of all mesa dependencies to be compatible with mesa-freeworld.
I published a Copr Repo with it, in case others think it is useful.