goldberg_emulator VS WASI

For a lot of games you can simply copy out of Steamapps/common and run the exe and it'll run like a standalone copy.

For games that use steam features, you can drop in a steam emulator[0] to shim the API calls. I use this for when I want to run multiple versions of the base game with different mods.

Typically this works fine as long as there's no real Drm/anticheat (which is common in multi player games but rare for single player).

So this should allow you to clone parts of your library for your son to play (as well as consolidate your many accounts).

[0] https://gitlab.com/Mr_Goldberg/goldberg_emulator/blob/master...

Goldberg steam emu

I highly recommend you go to https://gitlab.com/Mr_Goldberg/goldberg_emulator to find more information.

I tried to use Goldberg Emulator and I can't enable the overlay for it. How do I turn on the steam overlay because otherwise I won't be able to invite my friend?

What do you mean?

Why do you think you can't find Goldberg Steam emulator on Steam/Xbox/Playstation/Switch? (https://gitlab.com/Mr_Goldberg/goldberg_emulator)

Hint: it's used to play games without Steam DRM :)

Do you say that Valve's been a bully for years as well for trying to block Goldberg from Steam?

You would do the same if people made it easy to illegally distribute and use your products for free

And Nintendo is forced to do something to protect 3rd party studios/publishers as well

Any VPN will do (I used to use NeoRouter back in the day, but now I use OpenVPN to my cloud server or my home router), and you may be able to get some traction with Steam releases using Goldberg. https://gitlab.com/Mr_Goldberg/goldberg_emulator

I'm not gonna put the actual instructions for cracking here since that's already on the sites of the tools you'll be using. I will only link the tools here and the rest will be up to you. The main tools for cracking are going to be Steamless, and Goldberg emulator. These tools can be a bit tedious on their own but someone has graciously made an auto cracker that requires you to download the first 2 tools and then automates the process for you.

No clue, I'm using the Goldberg Steam Emulator. If you're asking what the Steam Emulator does, it allows the game to run without Steam installed, usually replaces the original steam(_api64/_api/client/client64).dll(s).

I have no idea about cracking games but try Goldberg Emulator. I use it for pirating DLCs but I think you can use it too. Also, its easy to use.

Hmm. I have a question. Would this work if the game had used say... the goldberg emulator for the steam drm bypass?

WASI Co-chair here. Nothing in WASI is "somehow blocked by Google", or indeed blocked by anyone at all. Graphics support in WASI hasn't been developed simply because nobody has put energy into developing graphics support in WASI.

At the end of 2023 we counted around 40 contributors who have been working on WASI specifications and implementations: https://github.com/WebAssembly/meetings/blob/main/wasi/2023/... . That is a great growth for our project from a few years ago when that issue was filed, but as you can see from what people are working on, its all much more foundational pieces than a graphics interface. Also, if you look at who is employing those contributors, its largely vendors who are interested in WASI in the context of serverless. That doesn't mean WASI is limited to only serverless, but that has been the focus from contributors so far.

By rolling out WASI on top of the WASM Component Model we have built a sound foundation for creating WASI proposals that support more problem domains, such as embedded systems (@mc_woods and his colleagues are helping with this), or graphics if someone is interested in putting in the work. Our guide to how to create proposals is found here: https://github.com/WebAssembly/WASI/blob/main/Contributing.m... .

> As I understand it, it's not even really possible today to make WebAssembly do anything meaningful in the browser without trampolining back out to JavaScript anyway, which seems like a remarkable missed opportunity.

That's the underlying messy API it's built on. There are specs to make the API more standardized like https://github.com/WebAssembly/WASI

But overall, yeah, it feels like a shiny new toy everyone is excited about and wants to use. Some toys can be fun to play with, but it doesn't mean we have to rewrite production systems in it. Sometimes, or most of the time, toys don't become useful tools.

Snapshot Preview 1 is the standard all tools are building to right now. The specification is available here: https://github.com/WebAssembly/WASI/blob/main/legacy/preview...

It's pretty unreadable though!

Preview 2 looks like it will be a big change, and is just being finalised at the moment. I'd expect that when preview 2 is available there will be an improvement in the quality of documentation. I'm not sure how long it will take after release for tools to start switching to it. I'd expect Preview 1 will still be the main target at least for the rest of this year.

> Like WTF does this mean? The repo tells me nothing

Directly above the sentence you quoted:

"Interposition in the context of WASI interfaces is the ability for a Webassembly instance to implement a given WASI interface, and for a consumer WebAssembly instance to be able to use this implementation transparently. This can be used to adapt or attenuate the functionality of a WASI API without changing the code using it."

> and I've still yet to see a clear write-up about what WASI is.

In the same document: [0]

> WTF is wit?

The first link in that document ("Starting in Preview2, WASI APIs are defined using the Wit IDL.") is [1].

> I click on "legacy" and I see preview0 and preview1, which are basically unreadable proto-specs.

The README for the legacy directory [2] clearly explains what they are.

> Where's a single well-written WASI spec?

"Development of each API happens in its own repo, which you can access from the proposals list." [3]

> Whatever WASI is doing, I don't like it.

Clearly not - you've gone out of your way to ignore all of the documentation that answers your questions.

> And neither does AssemblyScript team apparently

The AssemblyScript team have a bone to pick with WASI based on their misunderstanding of what WASI is for (it is not intended for use on the web) and WASI's disinterest in supporting UTF-16 strings. You can see for yourself in [4].

[0]: https://github.com/WebAssembly/WASI/tree/main#wasi-high-leve...

The Bytecode Alliance initiated a sub-project called the WebAssembly System Interface (WASI). WASI is an API that allows WebAssembly access to system features such as files, filesystems, Berkeley sockets, clocks, and random numbers. WASI acts as a system-level interface for WebAssembly, so incorporating a runtime into a host environment and building a platform is easier.

We are excited to contribute back to Wasmtime and the component model, as well as to new projects and proposals emerging in this space (such as new Wasm proposals, like WASI Preview 2, wasi-keyvalue, wasi-sql or wasi-cloud).

I've been reading the following repositories.

https://github.com/WebAssembly/WASI/blob/main/Proposals.md