You are reading content from Scuttlebutt
@aljoscha %Ar7gwhhG6k5VDKE25LEtILMu3Gpnj+dX3oH/jvwl6GU=.sha256

Is there a URI scheme for referring to scuttlebot messages? I'd think I remember seeing ssb://hash, but could not find this anywhere.

In related news, after reading this discussion on IPFS URIs, I now understand why the scuttleverse seems to move so much faster than the ipfs.

User has not chosen to be hosted publicly
@Dominic %cx4sDkZEor3BJWlF6GfwXCStXSul3fPbxlLG+MDv2yQ=.sha256

I think @dinosaur found the solution here url-friendly variant of base64 we can just convert to base64, then regexp to make it url friendly. We'll just make everything also accept friendly64 the same as base64. Also, we could maybe accept names as well as sigils, like /blob/{friendly64} then it will be easy to share. Not as ugly as URI encoding.

Oh I didn't realize that post was from 4 months ago!
what would we have to change?

  • ssb-ref (which provides functions to validate ids)
  • multiblob (which stores blobs)
  • secure-scuttlebutt (where it retrives messages)
  • ssb-markdown

that might do it?

@aljoscha %DQ7cotJpKiPo5r0E3LRUSp/InUBxnrzPTZq97pehtpA=.sha256

If changing things is an option, you might also want to check out multiformats in general and multihash specifically. Sharing some standards with the ipfs could be a good idea.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
Join Scuttlebutt now