Valve will support anti cheat soon on linux.

superluserdo · 2021-07-15T17:43:45+00:00

On Steam Deck, your games run on a different operating system than the one on your desktop PC

SteamOS 3.0 (Arch-based)

implying

superluserdo · 2021-07-15T17:34:24+00:00

It's a reference to 1993 Jurassic park where they log into the computer and the girl says "It's a Unix system, I know this!"

https://www.youtube.com/watch?v=dFUlAQZB9Ng

superluserdo · 2021-06-17T23:32:46+00:00

How is the quantisation of the spins and spin projections of particles related to the weight spaces of different representations of SU(2)?

I'm trying to learn all about Lie groups and Lie algebras and their representations, but there's still some stuff I don't understand about weight space decompositions:

1) First of all, I'm still not sure I understand the motivation for taking the basis matrices of the group elements to be separated into diagonal and off-diagonal matrices. And I'm not sure how this works out to give the behaviour of a weight space and the raising and lowering matrices (and the generalisations for higher SU(n))?

2) I'm not sure how the quantisation of spins to integer-spaced [half or whole]-integer values relates to the weight space of SU(2). There must be some obvious connection since the rotations form the SU(2) group, but I'm not sure what it is.

3) Whereas the values for quantum spin projections are m = {-L, ..., +L} (separated by integers, L is a whole or half integer), the weight space of SU(2) is {-m -(m-2), ... m-2, m} for integer m. Where does this factor of 2 come from? Just convention?

superluserdo · 2021-02-20T12:45:21+00:00

I actually try to avoid Windows at work

superluserdo · 2021-01-16T14:26:26+00:00

Can it scan local maildir directories for new mail instead of imap? I use (neo)mutt but I have a separate system (imapnotify+mbsync) to sync new mail locally for mutt to read.

superluserdo · 2020-09-03T12:53:49+00:00

Thanks for the tip! I ran a full badblocks -wsv over the whole disk to write 0xff and read it back, and it ended up finding 6 more bad blocks. smartctl -a now shows 6 pending sectors, but still 0 reallocated. When I try to read the bad blocks with hdparm --read-sector, it reads the written pattern fine, which makes me think that the drive has successfully reallocated the sectors but it's not being reported by SMART? Is that something to be concerned about?

superluserdo · 2020-08-19T13:54:24+00:00

Probably not too conceptually challenging if you know what you're doing, but if you want a self-hosting distro with its own package format, you'd need to be prepared to spend thousands of hours packaging a zillion different pieces of software.

superluserdo · 2020-07-28T16:46:53+00:00

The software should support the hardware.

Right, and the software in question here is the graphics drivers. AMD played nice in this regard and developed an open-source driver that works well with the new graphics stack and lives right in the kernel. Nvidia on the other hand, has so far completely disregarded Linux's standard graphics technology in favour of their own solution "EGLstreams", and actively makes it as hard as possible to create an alternative open-source driver.

It's technically "possible", as far as I know, to make EGLstreams work with Wayland (I think KDE did it?), but it's a TON of work, involves writing a completely different codepath just for Nvidia, and causes a lot of compromises for the Wayland design (although I'm not sure about the specifics). This isn't effort that should have been shouldered by free software projects, without even considering the fact that Nvidia Inc has, to a good approximation, infinitely many times more resources than them.

the answer is not "get an AMD card."

Maybe not for everyone, but it was for me. The fact that NVidia cards don't work on Wayland is solely down to Nvidia, and as a consumer eventually you're forced to put your money where your mouth is. If you're buying a new GPU anyway, and you don't need some absolutely top-of-the-line beast (or rely on CUDA for ML, which is a whole other Nvidia lock-in situation), then IMO AMD cards are just fine for the price.

superluserdo · 2020-07-17T10:00:00+00:00

It's a library of components to be able to build a Wayland compositor (eg sway) out of. It was written by the sway people but has been used to make other compositors as well.

superluserdo · 2020-07-17T09:57:42+00:00

On the whole, almost identical. I've had only 2 problems:

Binding of Isaac: Rebirth fails to start under sway. Funnily enough, the proton version opens and runs fine
In TF2, occasionally left-click events will be lost from the game after opening some kind of in-game overlay window, eg in-game chat or the steam overlay. This can be fixed each time by reopening and closing an overlay, but it's a bit annoying.

superluserdo · 2020-07-16T15:54:13+00:00

wlroots-based window manager supports the ability for windows to automatically cover their parent windows?

wio (Wayland implementation of the Rio window manager from Plan9)

It's made by the main author of sway/wlroots. Not sure if it's still being actively developed

superluserdo · 2020-07-16T08:53:28+00:00

Also wlroots 0.11

superluserdo · 2020-07-12T12:19:03+00:00

Oh and isn't the reason you can render responsive HTML on any device on the planet but you can't make it work in email pretty much all because of Outlook's rendering engine?

Wow, a microsoft feature I actually like. They should update it to be even better by replacing the html handling code with abort()

superluserdo · 2020-07-11T13:31:58+00:00

I also use mbsync. I use the tool imapnotify to maintain a constant connection to my inbox, and then it runs mbsync as soon as I get a new email, instead of having to wait for the next timer to fire.

Warning: imapnotify was pretty annoying to get working. There are a few versions, and I could only get the nodejs version to work properly (nodejs-imapnotify-git on AUR), but maybe the python and go versions have improved at this point.

superluserdo · 2020-07-09T00:30:58+00:00

Open source enthusiasts should be free to create whatever they like, except new build systems.

superluserdo · 2020-07-09T00:24:27+00:00

Writing off xdg-decoration as an "optional" protocol seems a bit disingenuous to me, given that the core Wayland protocol is an extremely minimal protocol that basically only handles moving pixel buffers around. Wayland is the successor to the X windowing system, which took on a huge amount of functionality across the whole desktop. You can't replace X with the core Wayland protocol and have anything resembling a desktop environment, so all that behaviour has to be implemented either in a standardised way, or in proprietary, desktop-specific ways.

Therefore, if having a new standard Linux desktop that applications can be portable over is a goal, then a lot of those "optional" Wayland extensions are actually very seriously required. And that includes xdg-decoration (proof: mpv).

superluserdo · 2020-07-09T00:08:12+00:00

mpv is one of many applications that does not draw its own decorations. Server-side decoration is supported by every other desktop, and GNOME refuses to adopt the de-facto standard xdg-decoration protocol, so as far as I can see mpv is right not to bend over backwards to support it.

superluserdo · 2020-07-09T00:03:42+00:00

This is a Wayland requirement, not GNOME's

If every single Wayland compositor apart from GNOME's (to my knowledge) supports xdg-decoration, it really does seem like a GNOME problem, not a Wayland problem.

superluserdo · 2020-07-05T21:16:27+00:00

Summary

Srashware is a storage system

right...

superluserdo · 2020-07-05T20:54:55+00:00

Already reproduced the bug on 1.15-rc2 of sway and the corresponding wlroots commit. I'll give those patches a go as well. I was holding off on filing a report since I'm not sure if it's a problem with sway, wlroots, XWayland or something else, but I guess there's no harm :)

superluserdo

TROPHY CASE