Content
@
https://warpcast.com/~/channel/ottp
0 reply
0 recast
0 reaction
Open to the Public
@ottp
We're looking for developers / technical writers to help us improve our docs. We'll reward those who provide thoughtful, high-quality feedback at our discretion. 1. Review docs at docs.opentothepublic.org or github.com/opentothepublic/docs. 2. Create a PR and provide your feedback. Amount: 50 USDC Deadline: 2025-05-01 @bountybot
5 replies
1 recast
7 reactions
john
@know
Can direct links not be made between Subjects and Blocks?
1 reply
0 recast
1 reaction
ting.⌐◨-◨
@ting
Hi! Thanks for the question! Think of blocks as data. Every object (Project, Proposal, Milestone, Contribution) contains one or more blocks. So, subjects are connected to blocks in that way. Do you have a specific use case in mind?
1 reply
0 recast
1 reaction
john
@know
I guess if multiple people were working on one project - and one designed and one coded, those two blocks in the same project would be worth tying to each subject at the granular level of blocks
2 replies
0 recast
1 reaction
ting.⌐◨-◨
@ting
The most granular level would be the contribution, so all the basic details of who did what individually or together. This can be onchain or offchain data. It's modular and not nested, so it could be approached in many ways. Here are just two examples. Example 1: - Team: Higher - Project: Farcaster frame - Collaborators: designer, developer - Each person adds an individual contribution (makes an attestation) and then verifies each others. Example 2: - No specified project - The designer adds a contribution (makes an attestation) for all collaborators involved. The developer then verifies, updates, or revokes. It's worth thinking about if there's a single piece of data that's not tied to a contribution that would need to be linked together. 🤔 cc: @naaate
1 reply
0 recast
2 reactions
john
@know
I'm imagining a project where there is no 'team', it's totally open and people are just verifying eachothers contributions
0 reply
0 recast
0 reaction
