You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@ओषधिः %cWgB4Mp6+0AjO8y3NTUpBxRlTrhHbgCbjM3Db8TuwEk=.sha256

@decentral1se (patchwork) @trav

props to getting started and adjusting later as needed

I'm looking at the json of %X8nTwnG9sNsSYsIO9pTA3hhd0qGULu2b2NFC75Do4wU=.sha256 now

also just made a test post for an old bungee cord %rYIldAHOS/9LxlZ27Xr8lnUZXif9AzMBFJ2CYpULjjo=.sha256

the behavior in patchwork seems to be that my post is not displayed in the main feed or on my profile, even though it has a "text" field, I imagine because the type of the post I made is "nft-mint" and is not a known type

but if I search the ID of the post in patchwork, I can see the raw json

{
"type": "nft-mint",
"text": "an old bungee cord"
}

I guess an advantage of using type="post", and then just adding additional fields for nft/token stuff, is that the posts will appear in existing clients

on the other hand, having a specific "type" for what you are doing for your application feels like a good pattern as a opposed to overloading the type="post" with many different things

for instance "gatherings" have type="gathering"
e.g.
ssb-server get %t1dGJg+...

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