Guidelines to create from Go > SDK ?

[adriens]

Describe the problem/question

I'm currently considering to implement privatebin sharing facilities from a cli written in Go.

I wonder if there are some docs, guidelines or code samples or even better a SDK ?

Did you use the FAQ section?

• Yes, I have read the FAQ and I found no solution/answer there.

What you did?

I found the following related resources :

• https://github.com/fopina/privatebin
• https://github.com/safing/go-privatebin
• 🌟 https://pkg.go.dev/github.com/gearnode/privatebin/privatebin#pkg-functions

What happens

👉 Which option would you officially recommand ❔

What should happen

No response

Additional information

No response

Server address

No response

Server OS

No response

Webserver

No response

PrivateBin version

No response

Browser and version

No response

Local operating system and version

No response

Issue reproducibility

No, I cannot reproduce it on https://privatebin.net.

[elrido]

The JSON-LD REST API is documented in the wiki and so is the payload format including the mode of encryption.

As I'm not a Go-user a can't say much on these solutions. The second listed one seems an outdated fork of the first one. The gearnode solution got linked to by a community member in our Third-party clients list in the wiki and it seems fairly active looking at the github repo. Also linked is pbin, but it didn't get updated in some years. The API hasn't changed in years either, so it is likely all of these solutions still work just fine with current versions of privatebin.

[adriens]

So you would recommant to directly talk to API : no special advice for any specifi Go module ?

[elrido]

I'm not aware of any go modules. Do any of the above linked project separate the API into a module or library at all or is it just integrated into the CLI? I'm not a Go developer, so I'm really not the one that can give any solid advice on that front.

It is a very simple REST API, though, you don't even need to care about authentication, sessions or any other state. If all you need to do is create pastes, there is a single POST request you need to implement.

What is admittedly more challenging is implementing the cryptography correctly, if you get it right, created pastes decrypt, if not they simply wont and it is always tricky to figure out why, as the resulting payload will in either way be indistinguishable from random noise. I would recommend to look at how the existing implementations did that or possibly even re-use their code for your use case, if the license of the picked solution is compatible to the one you apply to your project.

[rugk]

And in any case: If you or someone else publishes a code, feel free to link it. The best place is the already mentioned third-party clients list in the wiki. You can also ping the author(s) of the go clients here or so to make them aware or somehow else ask them.

[adriens]

Sure, if we do, we will. In case we integrate privatbin into an open-source software, would you be interested to get notofied, eg. in a section "They used it in their software" ?

[rugk]

Maybe. In any case you can link/discuss it here or in a new PR.

[gearnode]

Maintainer of this third library here. The latest version is available at go.gearno.de/privatebin/v2, though be aware that this linked version is deprecated.