Sure, the steps are different depending on which i2p router you are using, for i2pd, you just have to add a file in your tunnels.d directory, or add an entry in your tunnels.conf and then reload the tunnel configuration. In Java i2p, you will have to do it through the gui.

Here is the link to the tunnel config for i2pd: http://i2pcraft.i2p/example/i2pdtunnel.html And here is a link to a screenshot of Java i2p: http://i2pcraft.i2p/img/config.png

The tunnel length can be reduced to 1 for better performance, but you will sacrifice some anonymity.

But once the tunnel is setup and running, you can use Minecraft 1.19.2, or a newer version with ViaFabricPlus and connect to 127.0.0.1:25565. Its an anarchy server, but its pretty chill, I heard there is an iron farm and trained villagers for anyone to use near spawn, but I havent seen them. It is a cracked server, so you will have to use /register and save your password somewhere.

The other server is at mc.r4sas.i2p, I couldnt copy any links from there, I think its down rn, but the instructions for i2pcraft should be pretty much the same, just a different address. But I think its a russian speaking server, all of the players ive seen on i2pcraft speak english.

I dont use the outproxies for ssh, but it should be possible to connect to my server using its clearnet address using one of the outproxies. I have i2pd running on my server 24/7, and an entry in the tunnels.conf file that points to 127.0.0.1:22 on the server. When I want to connect to it, Ill run another i2p router on whatever device im connecting to, and Ill put the “.b32.i2p” address into ssh while using the SOCKS proxy for it. It is possible to make a client entry in the tunnels.conf on whatever device you are connecting from, and you can even turn the hops down to 1, which will increase performance, but lower anonymity. I think by default the SOCKS proxy uses 3 hops, but it can be changed.

But it should totally be possible to run your own private VPN over i2p, but Ive never done it myself, I just use ssh to port forward all of my self hosted stuff.

There are exit nodes in i2p, but they are called outproxies. The most popular ones are exit.stormycloud.i2p, purokishi.i2p, and outproxy.acetone.i2p. To setup an outproxy, you will have to setup software external to i2p, i2p routers by themselves will never exit. It is possible to visit onion domains inside of i2p, StormyClouds’s outproxy has support for this, but from what ive heard, its recommended to use none of these, and to just use the tor browser if you need to access onion sites or the clearnet anonymously.

There are many use cases for i2p besides eepsites and torrenting, pretty much anything that runs on TCP can prolly be ran on i2p. For example, I run my servers ssh over i2p, so if my ip address were to change for whatever reason, the i2p address will remain the same. There are also IRC services, internet radio stations, there are even 2 public Minecraft servers.

Nheko is my favourite client, it uses QT and is written in C++, its lightweight and works well on my machines with low resources, it also respects my system theme

deleted by creator

sudo sed -i 's/libalpm.so.14/libalpm.so.15/g' /usr/bin/paru

I think it kinda looks like a lollipop

What a bunch of cringe edgy antinatalist nonsense. Think about the future, if you don’t have kids, who are we gonna feed to the machine a few decades from now?

I figure that the administrators of your homeserver could see your IP address, I doubt that it would be sent to anyone you are just chatting with.

Ive only had to setup a nvidia system once, so I might be missing some packages, but I think pacman -Rns nvidia nvidia-utils lib32-nvidia-utils should get rid of all of it.

WARNING: doing this will absolutely DESTROY YOUR SYSTEM, PERMANENTLY!!!

But if you wish to continue, you can erase all the EFI variables using the rm utility, I dont think you will be able to completely zero out the chip on the system from inside of Linux as its read-only.

But to delete all the EFI variables, cd into /sys/firmware/efi/efivars, if this directory is not availiable, either the efivarfs is not mounted, or you are booted in legacy BIOS mode. But once you are in this directory, run chattr -i ./* as root or sudo to remove the immutable bit on all the files, then run rm ./* as root. This WILL break your system. Only do this if you know how to restore your system using like a chip programmer.

This happened to me too. I had to grab the box that comes up and resize it like I would with a normal window, mine glitched a lot when I tried it, try resizing it as far as you can, it will try and glitch back, but just keep fighting it until it becomes a usable size, then log out of Plasma and log back in, and then you can size it back down to a normal size. Hopefully there will be an official fix for this soon

What about something like this:

for i in /media/johann/5461-000B/DCIM/100MEDIA/*.AVI; do newpath="$HOME/Public/240321/$(basename "$i" | sed 's/^IMAG/240321_/g')"; ffmpeg -i "$i" -ss 00:00:00 -t 00:00:20 "$newpath" && rm "$i"; done

If its just / owned by the mint user, you should just able to run chown root:root / as root/sudo, dont use -R. This should make root become the owner of /. Now if all files and directories in the partition are owned by the mint user, this might be a bigger problem

Alright, could you see what the root variable is in the grub console before manually setting it by running echo $root, and if it prints anything, could you run ls / in the grub console and see if you see like home dev etc, or the directories you would expect to see in / inside linux, and if you do see anything, could you run ls /boot/grub/ and see if you see grub.cfg. But if you are already inside linux, go ahead and install grub with --removable, it wont overwrite your current installation. I dont want you to format the efi partition, incase something goes wrong and you wont be able to boot into linux at all

I think anything that can be done with a fresh format can be done with the current one, when you ran grub-install after the issue with not running it as root, did you only do it with --removable? If so, the old grub is might be getting picked over the new grub installed at the removable fallback path, because it has a proper entry in the boot order. I dont know what key it is on your system, but if you can get into the boot order menu where it shows all the different boot devices, like where you can pick where you want to boot from, id look for one that just says something like "UEFI boot " or something like along those lines, it wont say like grub or your distro name, if there is such an option available, could you try booting from that option?

Oh its no worries, it sounds like you just need to regenerate the grub config, you can do this by running

sudo grub-mkconfig -o /boot/grub/grub.cfg

or if your distro has it, you can just run

sudo update-grub

then grub should see the config on boot and put you in the normal graphical menu

This is definitely strange, but the EFI system partition will have to be mounted to install grub to it, maybe the disk got mounted as read only, could you try explicitly mounting it as rw with this command

sudo mount /dev/nvme0n1p1 /boot/efi -o rw

and then see if you can make a file as root by doing

sudo touch /boot/efi/test

if it doesnt fail on a permissions error, try installing grub again with --removable incase this error has something to do with it trying to tell the firmware what disk to look in like this

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable

hopefully this will run without error and install grub, and if it does id run it again without the removable flag

As long as the kde neon partition is still there, recovery should be possible. You will need a way to boot into a linux environment like a installation media of just about any distro, where you will be able to mount your kde neon install, chroot in, and reinstall grub. Now I dont know your system or how you have it setup, but I can try and give some basic instructions.

So first things first, you are gonna want to get into a linux environment and open a terminal and start a root shell, this may be different depending on your environment, but its pretty much just:

sudo bash

or

su -l root

now if either of these ask you for a password, and its not presented somewhere, you may have to search on the internet for like installation disk default password, but hopefully sudo is just setup to run without one.

Now that you are in the root shell, you need to find the name of the block device that corresponds with your kde neon partition, the lsblk utility can be used to list all detected block devices, you are gonna want to find the one with the same size as your kde neon partition, this will likely be the one. Now if your partition has a label on it, you can use ls to look into the /dev/disk/by-label/ directory and see if you see your partitions label there, if so, you can just mount it like this:

mount /dev/disk/by-label/example-label /mnt

If the /dev/disk/by-label/ directory does not exist, it just means that none of the partitions are labeled. If you are having trouble determining what partition has your data, you can try mounting each one and looking inside, and unmounting them if it doesnt have your kde neon install like this:

mount /dev/sda1 /mnt
ls /mnt
umount /mnt

sda1 is just an example here, it may be different on your system.

Now when you have found the partition that has your kde neon install and mounted it to /mnt, you can now cd in and bind mount the special directories like this:

cd /mnt
mount -t proc /proc proc/
mount -t sysfs /sys sys/
mount --rbind /dev dev/

now if you are booting using UEFI, you will have to bind mount the efivars directory with this command:

mount --rbind /sys/firmware/efi/efivars sys/firmware/efi/efivars/

Now with everything mounted, you should be ready to chroot in and reinstall grub, you can chroot with this command:

chroot /mnt /bin/bash

Now that you are in your kde neon install, you can reinstall grub, the installation process may vary depending on if you are booting legacy BIOS or UEFI, to install grub on bios, you would run:

grub-install --target=i386-pc /dev/sda

now /dev/sda is just an example here, but you want to install it to the main disk, dont install it to a partition like sda1 or something.

But if you are on efi, there may be an extra mount involved, the EFI system partition, now if the EFI system partition gets mounted automatically in normal circumstances, you should be able to just run:

mount -a

this command will mount the partitions listed in the /etc/fstab file. If the partition was destroyed, it will have to be recreated. If it is not listed in the fstab and is not automatically mounted, you may have to seek it out manually with lsblk, it should be the smallest partition, use the mount command to mount it to /boot/efi, creating this directory if it does not already exist. If you have to create one, just make a partition with at least 16 megs of space, and format it as a FAT partition, you can use the mkfs.msdos or mkfs.fat command line utilities like this:

mkfs.msdos /dev/sda2

where /dev/sda2 is the free space that is gonna be used for the system partition, this command is destructive, and will overwrite any data on the partition, so make sure you enter the one with just free space.

Once you know what partition is your efi system partition, and you have mounted it to /boot/efi in the chroot, you can now install the UEFI version of grub, you can use this command

grub-install --target=x86_64-efi --efi-directory=/boot/efi

and for good measure/backup incase grub cant tell your firmware where it is located, you can install it to the removable media path where your firmware will look if it doesnt have any entries with this command:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable

And finally, once you have installed grub for either UEFI or BIOS, you can generate the config file, like this:

grub-mkconfig -o /boot/grub/grub.cfg

Now you can reboot using the reboot command like this:

reboot

it should take care of unmounting everything for you, make sure you remove whatever installation media if you are using any from your system. And hopefully it should just boot into the normal grub menu and start your kde neon install.

I was thinking about that too, I cant think of much this ID is good for other than fingerprinting users. It just sucks that there isnt much of anything that can be done about it without a rooted device or privacy rom.