tobi
tobi
So how would this look if we did it with open telemetry (which seems like a good idea btw): i guess we would do something like: ```go ctx, span :=...
Oh, look at that: https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation/github.com/gin-gonic/gin
@daenney is it OK with you if I close this PR for now, and instead we can move discussion to this opentelemetry issue i created? https://github.com/superseriousbusiness/gotosocial/issues/1230
Neat :eyes: I'm gonna put a Future Tech label on this one because it won't be an immediate priority, but something to consider in the future :)
I'm gonna close this since, at this point, it looks unlikely to be something we'll ever implement. But we can always open it again later if we change our minds...
Hmm, do we really need this? What are the advantages of it, since we always package the binary in a tar along with the assets? It seems to me that...
> so I don't have to move assets in place separately, being careful not to overwrite some local changes in the process mm fair enough yeah, that use case makes...
> go doesn't produce smol binaries well, normally it does, the issue in GtS's case is the large amount of generated code from go-fed (i believe) -- which is something...
I'm gonna convert this to a draft btw, since it's still in progress :)
Will try and get time to review this soon and help you out -- been v. busy the last days with admin and getting 0.6.0-rc1 out