nemunaire
nemunaire
I support the request of @harryzcy. The current implementation is really annoying and creates lots of issues inherent to the way `go.mod` evolve. There are many side-effects introduced regularly by...
If this can be acceptable for an end user project, as the only implication is that this project requires a recent compiler, what about libraries? With this option enabled by...
It's not the feature that is criticized, but its activation by default. As @rarkins mention, people need that to perform usual modules update smoothly. And I'll be glad not to...
This is what @harryzcy writes in first post: https://go.dev/doc/modules/gomod-ref#go-syntax > ## Syntax > > go minimum-go-version > > minimum-go-version > : The minimum version of Go required to compile packages...
Will you accept a pull request implementing a smarter `go x.xx`, to be used by default instead of the current feature, based on the `max(max deps required version,current module version)`?
Perhaps you should consider this example: go 1.19 will be out next month. All projects (end user project and modules on which end user projects depends) will move to a...
Yes, this is all about Go module authors I and Go people rely on. For our own projects, the impact of this feature is negligible as we can choose to...
rmfakecloud could run either on HTTP and HTTPS, so deprecating `STORAGE_URL` in favor of a variable with less information is awkward. Moreover, you can use the `net/url` go package to...
What you're describing is a small variation of the [3rd setup variant](https://ddvk.github.io/rmfakecloud/remarkable/setup/#edit-router-dns-entries). As a sysadmin myself, I wasn't also convinced by installing a proxy on my tablet, so I run...
> 3rd setup variant still requires running a reverse-proxy on the reMarkable. No, no proxy/reverse-proxy on reMarkable. The only reverse-proxy is the one to redirect ingress traffic on the server...