I'd think so. 3k is so many pixels to compute and send 60 times a second.

But this video says the effect on battery life in their test was like 6%, going from 4k to 800x600. I can imagine that some screens are better at saving power when running at lower resolutions... but what screen manufacturer would optimize energy consumption for anything but maximum resolution? 🤔 I guess the computation of the pixels isn't much compared to the expense of having those physical dots. But maybe if your web browser was ray-traced? ... ?!

Also, if you take a 2880x1800 screen and divide by 2 (to avoid fractional scaling), you get 1440x900 (this is not 1440p), which is a little closer to 720p than 1080p.

I got interested, so I spent some time looking into what's going on here. I'm not intimately familiar with X11 or Wayland, but I figured out some stuff.

Why sudo ip netns exec protected sudo -u user -i doesn't work for X11 apps

Short answer: file permissions and abstract unix sockets (which I didn't know were a thing before now).

File permissions: when I start an X11 login session, the DISPLAY is :0 and /tmp/.X11-unix/ has only 1 file X0. This file has 777 access. When I start my wayland session with Xwayland, the DISPLAY is :1 and /tmp/.X11-unix/ has 2 files X0 (777) and X1 (755). I can't figure out how to connect to display :0, so I guess I'm stuck with :1. When you change to a different (non-root) user, the user no longer has access to /tmp/.X11-unix/X1.

Abstract unix sockets: When I start my wayland/xwayland session, it creates abstract unix sockets with ids @/tmp/.X11-unix/X0 and @/tmp/.X11-unix/X1. See ss -lnp | grep Xwayland. The network namespace also sandboxes these abstract unix sockets. Compare socat ABSTRACT-CONNECT:/tmp/.X11-unix/X1 STDIN and sudo ip netns exec private socat ABSTRACT-CONNECT:/tmp/.X11-unix/X1 STDIN.

When you do sudo ip netns exec protected su - user, you loose access to both the filesystem unix socket /tmp/.X11-unix/X1 and the abstract unix socket @/tmp/.X11-unix/X1. You need access to one or the other for X11 applications to work.

I tried using socat to forward X1 such that it works in the network namespace... and it kinda works. sudo ip netns exec protected socat ABSTRACT-LISTEN:/tmp/.X11-unix/X1,fork UNIX-CONNECT:/tmp/.X11-unix/X1. It appears having ABSTRACT-LISTEN before UNIX-CONNECT is important, I guess it would be worth it to properly learn socat. With this sudo ip netns exec protected su - testuser -c 'env DISPLAY=:1 xmessage hi' works, but sudo ip netns exec protected su - testuser -c 'env DISPLAY=:1 QT_QPA_PLATFORM=xcb kcalc' does not work. 😞

Changing the file permissions on /tmp/.X11-unix/X1 to give the user access seems to work better.

Wayland waypipe

Waypipe works as advertised. But it's still a little bit tricky because you need to have two separate processes for the waypipe client and server, wait for the waypipe socket to be created, adjust file permissions for the waypipe socket file, and set (and probably mkdir) XDG_RUNTIME_DIR.

waypipe -s /tmp/mywaypipe client &
sleep 0.1
chgrp shared-display /tmp/mywaypipe
chmod g+w /tmp/mywaypipe
sudo ip netns exec protected su - testuser -c 'mkdir -p -m 0700 /tmp/runtime-testuser && env XDG_RUNTIME_DIR=/tmp/runtime-testuser waypipe -s /tmp/mywaypipe server -- env QT_QPA_PLATFORM=wayland kcalc'
kill -SIGINT %1

Combined

into this script https://github.com/vole-dev/grabbag/blob/main/run-netns-user-wayland.bash

Completely tangential tip, but in the very-limited video editing I've done recently: I've used Davinci Resolve, rendered as .mov, and then used ffmpeg to render to my actual desired format. e.g. h264 w/ aac audio so I can upload to Youtube:

ffmpeg -i input.mov -c:v libopenh264 -profile:v high -c:a aac -pix_fmt yuv420p output.mp4

I do think that finding the right flags to pass to ffmpeg is a cursed art. Do I need to specify the video profile and the pix_fmt? I don't know; I thought I did when I adventured to collect these flags. Though maybe it's just a reflection of the video-codec horrors lurking within all video rendering pipelines.

edit: there may also be nvidia-accelerated encoders, like h264_nvenc, see ffmpeg -codecs 2>/dev/null | grep -i 'h\.264'. I'm not sure if the profile:v and pix_fmt options apply to other encoders or just libopenh264.

Flipping through my watched list, here are some romance anime I liked, varying levels of drama and comedy:

• Clannad and Clannad: After Story
• Skip and Loafer
• The Dangers in My Heart
• Toradora!
• My Love Story with Yamada-kun at Lv999
• Lovely Complex
• Taisho Otome Fairy Tale
• Tsuki ga Kirei
• Kimi ni Todoke: From Me to You
• Blue Spring Ride
• Sing "Yesterday" for Me

And maybe some that might not quite be what you were expecting:

• ReLIFE
• A Lull in the Sea
• One Week Friends
• The World God Only Knows
• Amagami SS
• Anohana: The Flower We Saw That Day
• Call of the Night

Edit: also looking forward to A Sign of Affection, which is airing this season

/home is not deprecated, it's optional but common. Here is the section from FHS: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s08.html

It is annoying that you can't necessarily connect to all instances from your favorite instance, but this is also what makes the fediverse great compared to more centralized social media. Even though dessalines decided to delist ani.social, ani.social still exists and is still connected to instances other than lemmy.ml.

Although seemingly distorted views of reality coming from the main lemmy dev team do concern me.

The way Demons think in this show is a lot like LLM Chat AIs like ChatGPT work. They don't really think too much, not in the way humans do, but they excel at producing something that humans approve of. If you don't probe them too much, they look just like humans. But if you probe too far you see that their behavior is a facade and that their underlying thoughts are not like humans, and they don't necessarily even understand the words they use to appease humans. What happens when their facade improves? If a demon spent its entire life perfectly acting as a nice and thoughtful human, never causing any harm, would you still call it a monster?

Demons and LLM Chat AIs differ in what their underlying thoughts are. LLM Chat AIs generally want approval. On the other hand, Demons want to survive and eat humans. They use language to manipulate humans and get what they want.

I find it a little sad that the double entendre of the title was lost in translation. From the beginning I understood the title to refer to Frieren watching her friends pass away of old age. Then this scene comes around and lets us know that 葬送のフリーレン is not just the title of the story; it's the nickname for Frieren, like The Undertaker or something like that; a name that conveys the destiny of demons that cross Frieren's path.

Update: I've now watched the available episodes of Berserk of Gluttony and Ragna Crimson. Both are good fun.

Berserk of Gluttony so far has not been much more than an edgy fantasy power-fantasy. But it's executed well and has been enjoyable. I think it's a little darker than the typical power-fantasy. The bad-guys are laughably evil and I'm not sure if the plot is going anywhere interesting.

Ragna Crimson is more story focused. I supposed this show also has the makings of a power-fantasy, but it has not leaned too heavily into the wish fulfillment aspect. The characters are more interesting. The bad-guys are also laughably evil here, but in a way that's more pure (literally being monsters helps, I guess), and thus a bit more horrifying. Every reward has a price, and you often do not know what that price actually is.

Anime Corner rankings have always been strange. That being said, I was pushing off watching episode 2 of Spy x Family because I just wasn't interested for some reason. I did get around to watching episode 2 and it was great.

Hm, I had written off Ragna Crimson and Berserk of Gluttony based on instinct, but it looks like they might be worth a try.

I'm almost happy for Getou, at least he looks happy now. It looks like we're done watching Gojo and Getou's past and are going back to the main story timeline.