i.e. you gotta pass the --localstore flag, and it has to point to the blobs folder of the running sbot
i.e. if you start a go-sbot with --repo "/var/ssb", then the blobs flag should be --localstore "/var/ssb/blobs", apparently
get works too, but has looks buggy
fixed the apparent error with has, hard to verify with a shitty bot tho ^^. i get what seems like a false negative tho
CC: @notplants
I'm pasting here what @cblgh had to say about blobs in cabal:
> i don't really remember what the issues we had with blobs was, but here's how you can do some basic stuff with it using sbotcli
```shell
[cblgh@howl]$ ./sbotcli blobs --localstore "~/.ssb-go/blobs" add blob-ul.txt
before=blobs locl=null
blobs.add="&skEdYtad6Ytg87x7u0h1LEe29LwUy/MC9oWofg4TUBY=.sha256"
```
> i.e. you gotta pass the --localstore flag, and it has to point to the blobs folder of the running sbot
>
> i.e. if you start a go-sbot with --repo "/var/ssb", then the blobs flag should be --localstore "/var/ssb/blobs", apparently
>
> `get` works too, but `has` looks buggy
>
> fixed the apparent error with `has`, hard to verify with a shitty bot tho ^^. i get what seems like a false negative tho
Once the add command has been executed (documented above), it returns a reference to the blob. This can then be used to compose and publish an about message:
./sbotcli publish about --image "&JlJHc9yeG1EpZA9fIPGLzUKDH0FeR39Ai57euhKT1G8=.sha256""@Sih4JGgs5oQPXehRyHS5qrYbx/0hQVUqChojX0LNtcQ=.ed25519"
Note that the ordering of the arguments is very important here, as are the inverted-commas (") around the references. The command will fail if the inverted-commas are ommitted.
Further notes from testing:
Once the `add` command has been executed (documented above), it returns a reference to the blob. This can then be used to compose and publish an `about` message:
```shell
./sbotcli publish about --image "&JlJHc9yeG1EpZA9fIPGLzUKDH0FeR39Ai57euhKT1G8=.sha256" "@Sih4JGgs5oQPXehRyHS5qrYbx/0hQVUqChojX0LNtcQ=.ed25519"
```
Note that the ordering of the arguments is very important here, as are the inverted-commas (`"`) around the references. The command will fail if the inverted-commas are ommitted.
./sbotcli publish about --image "&skEdYtad6Ytg87x7u0h1LEe29LwUy/MC9oWofg4TUBY=.sha256""@767fbfkQ7LUyNpXuR4uwvlAry+X8xSJ7CM3nNhjIrwI=.ed25519"
notes:
quotes around base64 input is important
the order of args is important for golang binaries: always, always flags before any final flagless arguments
adjust the blob ref passed with --image to your blob ref from ./sbotcli blobs add :)
publishing an about with the image
```sh
./sbotcli publish about --image "&skEdYtad6Ytg87x7u0h1LEe29LwUy/MC9oWofg4TUBY=.sha256" "@767fbfkQ7LUyNpXuR4uwvlAry+X8xSJ7CM3nNhjIrwI=.ed25519"
```
**notes**:
* quotes around base64 input is important
* the order of args is important for golang binaries: always, always flags before any final flagless arguments
* adjust the blob ref passed with `--image` to your blob ref from `./sbotcli blobs add` :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
CC: @notplants
I'm pasting here what @cblgh had to say about blobs in cabal:
Further notes from testing:
Once the
addcommand has been executed (documented above), it returns a reference to the blob. This can then be used to compose and publish anaboutmessage:Note that the ordering of the arguments is very important here, as are the inverted-commas (
") around the references. The command will fail if the inverted-commas are ommitted.publishing an about with the image
notes:
--imageto your blob ref from./sbotcli blobs add:)Latest working commands, using sbotcli-getsubset branch: