Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc…
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc…)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
Beehaw.org gaming
Lemmy.ml gaming
lemmy.ca pcgaming
- 1 user online
- 112 users / day
- 418 users / week
- 1.12K users / month
- 3.95K users / 6 months
- 1 subscriber
- 12.5K Posts
- 86.7K Comments
- Modlog
I think Proton has something of that nature, so games running inside Wine talk to the native Linux Steam binary.
WINE doesn’t really isolate apps. Valve may have done some degree of compatibility work or not for the Windows Steam library, but the game running under WINE doesn’t have any real restrictions on its ability to talk to Linux software. As long as the Steam Windows library and the Linux Steam client use some form of IPC mechanism that works on both platforms, like TCP sockets, it should “just work”, same way a Windows web browser running in WINE would “just work” when talking to a Linux webserver on the same machine.
But if someone’s having to set up a 32-bit VM running a different MacOS guest OS, then they’re not gonna be able to run Steam in the guest (due to the Chrome requirements that Valve mentioned), and I don’t believe that programs using the Steam library can talk to Steam on another host normally.
I’m just saying the “steamlib proxy” concept you mentioned is not only possible but has at least one implementation. The fact that Wine isn’t true isolation doesn’t really change anything (maybe other than the exact details of the underlying IPC channel, which could use some kind of optimized shared memory magic) unless I’m misunderstanding something.