blued_gear

joined 7 months ago
 

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
[–] blued_gear@fedia.io 11 points 1 month ago

image

Edit: trying to get the image to show on Lemmy

[–] blued_gear@fedia.io 12 points 2 months ago

A friend of mine and I had a discussion why Browser add workspaces or side-panel like views inside them as I think the usage of multiple windows archives the same effect: separating a bunch of tabs.
They had the argument that it benefits as many windows get hard to handle when you try to find the right one in the taskbar after minimizing one.

So I had the idea "That's a good point. But why limit it to Browsers and Co and wait for them to implement such stuff (other example is tmux with terminals)". So I started researching and found a Mastodon post (sorry, but I forgot where it was) that showed a Plasma shell inside a Wayland window. With some tinkering I came up with this script.

Now to answer your question: it can help to organize a lot of windows, but each Plasma instance takes about 200 MB RAM and also on my computer the main Plasma instance kept crashing after some minutes.

[–] blued_gear@fedia.io 46 points 2 months ago (3 children)

kwin_wayland supports launching Wayland displays inside a Wayland display. This can be used to launch KDE Plasma inside these windowed displays, and that recursive.

A GitHub with the script is here.

 
 

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.