@onlinepersona If you say so. Who am I to judge your reading comprehension better than yourself? It’s a good thing that you acknowledge it - that leaves room for growth 😉

@onlinepersona “Just don’t make the assumption everybody thinks like you do.” <– just by saying that, you have made the exact same assumption and are requesting (nay, demanding) that status quo is kept. 🤷‍♂️

@onlinepersona @iturnedintoanewt It would be most effective if you’d take your own advice - If *I* am searching through the start menu, *I* will be looking for applications first, files second and random directories absolutely last.

@FauxLiving and what OP is doing doesn’t require much - but I was’t commenting on OP’s post, I was commenting on the reply claiming the Frame was ready for a full OS. Which it isn’t.

@FauxLiving the Quest3 runs Android which is a lightweight Linux with a fairly opimosed proprietary graphics engine. It’s literally a powerful embedded device. It’s still too feeble for a full OS. The MQ3 struggles with the high-resolution, high-action games like Asgard’s Wrath 2, not having enough CPU power for the location detection PLUS running the game. The Steam Frame is no different in that aspect, the difference being Steam realizes it and are’t trying to gaslight you about the situation.

@bjoern_tantau @artyom How do you get that to compute?

The Steam Frame is a “streaming first” headset - *because* the onboard chip is too feeble for a full onboard OS gaming support.

That means it is a tethered device (WiFi or Wire - still a tether)

The Meta Quest series all support tethering (Wired - OR - WiFi) and the older Occulus devices RELY on a tether. The PS VR can be used on a PC with SteamVR so there’s no stopping it from being used like that too.

I find your computing erroneous.

@albertye better contrast

@albertye Maybe the colour scheme?

I have a similar issue with Chromium with Plasma and the dark MacOS theme

@caseyweederman @Bro666 Remember - from the proper POV, everyone’s an asshole :)

@caseyweederman @Bro666 that only means one of three things:
a) your sample size of Linux users is too small
b) the echo chamber of Linux users you measure yourself against is too homogeneous (and y’all happen to be nice guys)
or c) you really aren’t a nice guy and you just look down on all Windows users equally.

There’s a lot of nice Windows users - and there’s a lot of not-so-nice Linux users. Don’t get confused when measuring up people - judging a whole group from your POV isn’t good at all.

@Bro666 @Ephera this is it exactly. Those that take it the other way have a much too strong bipartisan way of thinking - everything is on exaggerated scales of a vs b, attacking the person, not the subject.

💪👏🏻 well said!

@who @Bro666 Well, it’s good then that your opinion doesn’t matter? No, it’s not too soon. X11 was a WELL KNOWN security risk *30 years* ago. For 30 years I’ve been managing systems, knowing that even an unprivileged compromise might lead to a machine leaking more than a sieve with its mesh missing.

Will it be disruptive? No. Will it change *your* workflow? Sure, at least in part, if you’re a streamer or have some very borderline needs.

X11 is a cancer long overdue.

@bytesonbike @Bro666 No, but a lot of people have said "I can’t create without Photoshop/Final Cut/Logic/Motion - applications that are Apple-first or Apple-only (and some of them, most of them, come from Apple).

@BlackLaZoR @schnurrito That is not a function of a UI - that’s a function of NetworkManager (or whatever network stack your distro uses).

As for WireGuard - it does that automagically across all platforms and all network stacks I’ve used it on so far - so if it’s not doing it for you, then you got something screwed up somewhere else, deeper down.

@idriss @Saapas It’s still an upgrade we’ve known for over two decades that we needed. The X protocol is inherently insecure by design - showing its age. If Wayland manages to nudge us a little closer to the reality of today, that’s a good thing - even if it comes bundled with some diaper rash.

@opensuse @[email protected] @[email protected]

Sorry for not having time to sift through 20000+ lines of logs…