user224

joined 2 years ago
[–] user224@lemmy.sdf.org 0 points 6 days ago

Sorry, I don't really understand what's going on in here. I just clicked because I've seen boykisser :3

Anyway, based on some of your posts, you might find !onehundredninetysix@lemmy.blahaj.zone and !femcelmemes@lemmy.blahaj.zone interesting.

[–] user224@lemmy.sdf.org 4 points 6 days ago

And my... where did I put it again? Shit, I always forget.

[–] user224@lemmy.sdf.org 1 points 1 week ago (1 children)

please take a look and tell me what you think

Sorry if it seems like I do, but I in fact do not have a brain.
I just found this tool gets the job done, and that's it.

I typically just use it in a pretty stupid manual way.

local$ waypipe -c zstd=6 ssh username@IP
remote$ export DISPLAY=:90
remote$ ./xwayland-satellite :90 &
remote$ xfce4-panel

Even the xfce4-panel discovery was an accident.
I was using waypipe before knowing about xwayland-satellite. I wanted to run an X program, so in the same shell I typed vncserver to, well, launch a VNC server. That invoked xfce4-session, BUT since the WAYLAND_DISPLAY was set, XFCE DE attached to waypipe rather than XTigerVNC, launching a full remote desktop over my local one.
And out of that, xfce4-panel proves pretty useful. I can easily launch other programs using GUI, and also see widgets on that panel.

Here's what I mean, if that sounds confusing:

Plasma panel (bottom) is local, XFCE panel (top and middle bottom) are remote.
Right, and you're probably wondering why that app launcher at the top looks shattered. Well, both can't be opened at once. If the application launcher goes out of focus, it closes.
But also, I use the shatter effect in KDE Plasma, so it doesn't go away immediately. This is just as close as I could get with screenshot timing.

[–] user224@lemmy.sdf.org 1 points 1 week ago (1 children)

I use it as a fallback when Catbox is down.
I typically can't use it either, but it seems to still cover majority of users.

[–] user224@lemmy.sdf.org 1 points 1 week ago

Just random cheap one - Schneider Ceod.
Writes smoothly, but I don't have experience with other pens.
Other than that I just have Stabilo beFab, but I think document ink has done some damage to it now.

[–] user224@lemmy.sdf.org 2 points 1 week ago (1 children)

Nah, Mallard can do that just fine: https://en.wikipedia.org/wiki/LNER_Class_A4_4468_Mallard#1938_speed_record

Speed record: 126 mph (203 km/h).

[–] user224@lemmy.sdf.org 7 points 1 week ago

RackNerd for my VPSs (3 of them right now)
Mullvad VPN
NextDNS

[–] user224@lemmy.sdf.org 6 points 1 week ago (3 children)

No, just Germany.

 
[–] user224@lemmy.sdf.org 7 points 1 week ago* (last edited 1 week ago)
#include <stdio.h>
#include <stdbool.h>

int main(){
        while(true){
                printf("Oh shit!\n");
        }
}
 

If you want to modify a pointer to pointer you need to pass a pointer to pointer to pointer.

I am lost.

 

TOTP Authenticator
Browser
Terminal emulator
Wireguard client

I've had the weird idea to use libpam-google-authenticator for both SSH and Sudo.
Hell, for one machine I don't even know the password. I just set it to a long random string. If I need root access, I can get a code from my phone!
That means I open it A LOT.

At one point I also had 4FA for fun. Or 3FA depending on how you look at it.
On server - pubkey + password + TOTP
On client the private key additionally encrypted with a different password.
Anyway...

[–] user224@lemmy.sdf.org 2 points 2 weeks ago (1 children)

More like taking sips from the bottle until "shit, that was all of it".

 
 

As usual, the answer is alcohol.
This DVD burned fine, but didn't read. I pressed my nail into the side to separate the 2 disc sections, then played around with it*, and finally stripped both the purple dye and reflective layer with isopropyl alcohol.

*I of course tried what it would do if re-inserted into the DVD drive. Single half wouldn't spin up. The spindle didn't have good enough grip. Placing the half with reflective layer back on top surprisingly made it read as a blank DVD, showing its (past) properties.
Trying to burn it again, unsurprisingly, resulted in I/O error.

 

 

At the end of 2023, the source code of GTA V has leaked. There were also some guides to build it from source.

Does anyone know if it was used in some way?

Just remembered it today when cleaning my phone's nearly full SD card, and GTAVSP.7z said hello.

 

I like the idea of X forwarding, but it doesn't work in real world anymore. As far as I know, it has to do many round-trips for everything. Launching something like LibreOffice Writer is funny, it will be loading bit by bit, icon by icon for several minutes. It was only usable for me on < 1ms network.

Unlike say VNC, it opens windows locally.

And now there's Waypipe which does the same thing, but for Wayland. And it actually works! Even better than VNC.

BUT, it doesn't work for X programs. It can somewhat work with rootful Xwayland... but that's basically a desktop for X-only programs.

Welp, I just wanted to check something on the remote desktop, so I launched VNC, and WOAH, I didn't expect to get XFCE invasion.
I didn't know XFCE can do Wayland now.

Anyway, this cursed thing does actually work pretty fine. xfce4-session works with Waypipe, good to know.

 
 

I accidentally untarred archive intended to be extracted in root directory, which among others included some files for /etc directory.
I went on to rm -rv ~/etc, but I quickly typed rm -rv /etc instead, and hit enter, while using a root account.

 

Edit 3: Tested with wg-quick on Arch, same issue re-occurs. So, let's say we have a peer on 192.168.1.1/24 with internal (wireguard) IP of 10.0.0.1/24, but we also want to route through it to rest of 192.168.1.0/24.
Instead of nice AllowedIPs = 10.0.0.0/24,192.168.1.0/24, it would have to be:
AllowedIPs = 10.0.0.0/24, 192.168.1.1/32, 192.168.1.2/31, 192.168.1.4/30, 192.168.1.8/29, 192.168.1.16/28, 192.168.1.32/27, 192.168.1.64/26, 192.168.1.128/25
Or there's something else going wrong. I only tried on Arch. Welp, as I said, it's not a thing that occurs with WG Tunnel on Android.

Edit 2: Hypothesis confirmed. Excluding the endpoint from AllowedIPs in NetworkManager solves the issue. However, this isn't a problem with 0.0.0.0/0, nor with WG Tunnel app on Android. I'll have to check with wg-quick. That seems most official.
Summary: NetworkManager tries to route traffic to WG peer over the same WG interface, and its /32 has to be excluded.

Edit: I noticed one thing, I'll try excluding the peer endpoint from AllowedIPs. It seems weird if it tries to connect to it over the interface between the 2 peers, which is of course impossible, but maybe? However, it is not matched by 0.0.0.0/0. Welp, time to experiment.

So, for 2 years I thought that NetworkManager Wireguard implementation is simply broken.
When I used a list of address ranges, like I should be (and am) able to do with Wireguard, I couldn't get any traffic through, however 0.0.0.0/0,::/0 would work.

Today I discovered something... interesting. It actually works... with a smaller list of AllowedIPs. Although even a larger list still ends up being shown by ip r.
So I went to AllowedIPs calculator as usual, created a desired list, pasted it in, and started removing IP ranges until I could ping a remote peer.

Problem solved? Well, no. I hoped it would be the limitation in number of routes, but it (also) seems to depend on route size.

Examples:
This is too much:
0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/3,160.0.0.0/5,168.0.0.0/6,172.0.0.0/12,172.32.0.0/11,172.64.0.0/10,172.128.0.0/9,10.147.0.0/24
Removing one of the routes, 172.128.0.0/9 makes it work.
0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/3,160.0.0.0/5,168.0.0.0/6,172.0.0.0/12,172.32.0.0/11,172.64.0.0/10,10.147.0.0/24

Time for mystery start. Keeping the same number of routes, but decreasing the size of one of them (second last) also makes it work:
0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/3,160.0.0.0/5,168.0.0.0/6,172.0.0.0/12,172.32.0.0/11,172.64.0.0/10,172.128.0.0/10,10.147.0.0/24

Naturally, I tried breaking up 172.128.0.0/9 into 172.128.0.0/10 and 172.192.0.0/10, which breaks it again.

So, it seems to depend on both number and size of the routes. After all, larger ones alone worked.

133
Vim Diesel (i.imgur.com)
submitted 1 month ago* (last edited 1 month ago) by user224@lemmy.sdf.org to c/lemmyshitpost@lemmy.world
 

Catbox appears broken, so Imgur again.

view more: next ›