Thanks, that was an interesting read! I always felt IPFS wasn’t ready yet, but the value it tries to provide of being a file system, I’ve found no real alternative to. Very good to read that iroh is willing to look beyond the IPFS spec to provide its values with better performance. I hope it works out.

Ever heard of IPFS? I really hope that will take off some time.

I think some more info is necessary on the DNS configuration. You’ve made an AAAA type record pointing to the ipv6 address of the server (not the router)?

I definitely did not run into this many issues when I installed it… Just kinda worked for me, so I’m not sure where you should investigate

Been running Wayland for 5 years on my development laptop (sway, Intel GPU, blacklisted the nvidia gpu). At the start I’ve had a couple of issues, nothing too bad. Haven’t had any issues for over 2 years. Switched to Linux on my gaming PC about a year ago, KDE plasma on Wayland but do most of my gaming from a steam gamescope session. Very happy overall with Wayland, glad it exists. Sharp text on a fractionally scaled display for reading code was just too compelling at the time and it only improved.

Oh interesting & unfortunate. I can confirm I use one display, running it on my TV. I must say, big picture on my desktop session gets closer to the experience than when I initially set this up. I hope they add the quick settings overlay to the normal big picture mode some time. I might switch back to running on my desktop session.

I haven’t had the issue with the menu, never had as far as I remember. It might be because of the way you set up the session. If you try installing the aur package I linked and start that session, the menu hopefully just works as it did for me.

I’m using this package: https://aur.archlinux.org/packages/gamescope-session-steam-git Looking at the source here: https://github.com/ChimeraOS/gamescope-session-steam/blob/main/usr/bin/steamos-session-select

You can see it looks for a script to shutdown steam or defaults to normal shutdown. I pointed os-session-select to a script that restarts my sddm service, before shutting down steam, so it returns me into the default session. It was a bit finicky though and I hacked a systemd service into it to ensure the script didn’t get killed.

Hope this helps. Might clean it up some time and put it in a repository/on the aur.

EDIT: I was inspired by ChimeraOS; it uses that os-session-select for its main project as well to return to the gnome desktop.

https://github.com/zsh-users/zsh-autosuggestions

Maybe Firefox, Thunderbird or Steam are running in XWayland and that causes different behaviour between them. Just guessing.

I think the argument is pretty solid as an alternative to writing PKGBUILDs yourself. Sure it doesn’t hold up for people unfamiliar, but Arch is build on the idea of getting yourself familiar with it.

I have some days off until new years. Will try to put it up and update this comment. Interested to hear what improvements people come up with!

Using Garuda Linux with KDE. Installed this package: https://aur.archlinux.org/packages/gamescope-session-steam-git

Wrote some scripts that performs the switching like it’s being done on ChimeraOS & the Steam Deck. Want to release them in a repository some time, but they’re awfully hacky right now.

Explained by someone that doesn’t know the technical side super well.

1: It’s a new protocol for displaying. The main difference from X11, as I understand it, is a simplification of the stack. Eliminating the need for a display server, or merging the display server and compositor.

2: Some things impossible (or difficult) with X11 are much better supported in Wayland. Their not necessarily available, as the Wayland protocol is quite generic and needs additional protocols for further negotiation. Examples are fractional scaling & multiple displays with differing refresh rates.

Security is also improved. X11 did not make some security considerations (as it is quite old, maybe justifiably so). In X11 it’s possible for any application to “look” at the entire display. In Wayland they receive a specific section that they can draw into and use. (This has the side-effect of complicating stuff like redshifting the screen at night, but in my experience that has fully caught up).

3: If you’re interested, are in desktop application development (but I have no experience in that regard) or have a specific need for Wayland.

4: I think X won’t die for a long long time if “ever”. I’m not super familiar with desktop app development, but I don’t think it requires more work to keep supporting X.

On the other hand, most of the complaints about Wayland I’ve heard were ultimately about support. At some point, when you’re a normal user, the distro maintainer should be able to decide to move to Wayland without you noticing, apart from the blurriness being gone with fractional scaling.

Seems like they at least could’ve made the page have a no-cache header so you don’t have to wipe the cache & history by hand.

Here’s why

Human rights

Alternatively: Hauk

(No idea how they compare)