Just implemented e2e encryption for plan, annotation, and diff sharing of coding agents (share with your colleagues, etc), modeled after https://privatebin.info/ https://github.com/backnotprop/plannotator/pull/203. - Source: Hacker News / 5 months ago

Is this basically https://privatebin.info/. - Source: Hacker News / over 1 year ago

If your like me. Find an actual use case for it and go from there. Easier to line when there is an end goal/project at the end of completion. Check out privatebin, sets up a secureway to share information. Https://privatebin.info/ Should hopefully be able to get your toes wet. Source: over 2 years ago

You're welcome! I'd recommend PrivateBin if you're looking for a pastebin service to use. Source: about 3 years ago

One of the things that always bugged me about image hosting services is that they're almost never open source. This very unlike Pastebin services where you have Microbin and PrivateBin. A lot of popular pastebin services either use PrivateBin or Rentry under the hood. Source: about 3 years ago

Anecdotal, but I have built from scratch a fairly large OpenAPI-compliant service using the Goa dsl (https://goa.design) and a coding agent and I've suspected for a while that the reason I've been as productive as I have with few blind alleys is that Goa kept the mistake surface pretty constrained. I also like not having the model generate boilerplate, as Goa's tooling does all that so much more cheaply. YMMV. - Source: Hacker News / 5 days ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / about 2 years ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 2 years ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 3 years ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 3 years ago