I only dislike the ability for service providers to enforce a “security level”. Those should be the exclusively under my (the user) control. Sending preferred default (hints) would be cool, but not enforcement.

That a webpage can basically prevent me from using a passkey if the passkey is stored in software (a password manager for example) is complete bullshit. Especially if there is still username/password as alternative which is clearly worse. Sure, hardware tokens are the ultimate security. But it should be up to me and not them if I want that level of security.

I would say yes. I have colleagues who have a hard time solving some tasks with an agent. Then I take a stab at it and succeed almost immediately. We both have the same freedom to choose and customize the available tools, but apparently my setup and usage is better.

I generally like their outcome, but hate the boilerplate. I think I need somewhere around 20 lines over two different files which would otherwise be a one-liner in a cron file.

Typically scales fractional to the user count and often in steps. These costs stay relatively stable no matter if you have 1 or 10000 players (for example), then rise a bit to support 18000 players, etc. And they should not start out high enough to require a loan just for them.

If you build an MMO and get a sudden influx of millions on players… ok. Then maybe. But they typically also grow somewhat organically.

Each user causing you direct costs that even increase with their usage is… not optimal. But hey, it’s worth a shot, I guess.

If the game uses the Steam SDK, they “of course” can at least check that the request comes from an authorized game (SSO via Steam). But sure, people who bought the game can still easily troll the dev, unless they also employ some kind of anti-cheat system. But from what it sounds like even then a troll could simply play the game excessively and then ramp up costs for the dev.

Only if the client is making the requests directly. If your own infrastructure is in between (which it should), you can limit the kind of requests and their rate at will.

Of course that’s an architecture I am not sure someone who develops something like this has on their mind.

But loans don’t scale with the amount of players and played hours. They purely factor into the cost of development and support.

Actually sounds like the perfect use case for a model like Jev. I think Jevos should be able to handle that locally.