1xX69

Results 22 comments of 1xX69

"All warfare is based on deception." ― Sun tzu, The Art of War. Given that quote, isn't deception a fair part of the gameplay?

Cuz we have a diverse target audience, we can't assume that all players speak English (Chinese players for e.x.). So if such system will be implemented, it should support automatic...

I'm surprised and disappointed that this feature is still not supported. How do you guys even use hurl productively without this?

> is there a way to read stream more gracefully on the server such that the error on RST_STREAM is propagated? Given the current implementation and the [hotfix](https://github.com/hyperium/hyper/pull/3275) it should...

> While this may be an expected behavior While it was an expected behavior on the client, it wasn't an expected behavior on the server.

We could develop a censorship tool with _federated_ communication (so that each user could maintain their own blacklists or subscribe to existing ones). It could be a browser extension or...

- Hacksoftware chose[^1] the `ResourceAction` pattern. - Google chose[^2] the `ActionResource` pattern. [^1]: https://github.com/HackSoftware/Django-Styleguide?tab=readme-ov-file#naming-convention-1 [^2]: https://github.com/aip-dev/google.aip.dev/blob/master/aip/general/0133.md#guidance

> Would this be for GraphQL, gRPC, JSON API? Regardless, my first immediate take is that, after so many years, I prefer to do `ResourceAction` so that things naturally stick...

With resource-specific services: ``` iam.example.com/ ├── AccountService/ │ ├── create_account() │ ├── delete_account() │ ├── get_account() │ └── suspend_account() └── ApiTokenService/ ├── create_api_token() ├── refresh_api_token() └── revoke_api_token() ```

Sometimes, the names for request messages can become a little weird, for example [`SearchSearchAds360StreamRequest`](https://github.com/googleapis/googleapis/blob/3acfdb6166a7101691cdf812bf8f8a67a2084fde/google/ads/searchads360/v0/services/search_ads360_service.proto#L119-L137)