Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content updates #31

Open
3 of 21 tasks
dtbuchholz opened this issue Feb 14, 2025 · 3 comments
Open
3 of 21 tasks

Content updates #31

dtbuchholz opened this issue Feb 14, 2025 · 3 comments

Comments

@dtbuchholz
Copy link
Collaborator

dtbuchholz commented Feb 14, 2025

TODO: use this issue as a placeholder to capture missing or future ideas

need:

  • - some tweaks here
  • - styles: re-review the color scheme values, and (if we purchase them in time) update the site fonts
  • - js sdk: update @recall to @recallnet namespace
  • CLI and alias option
  • - diagrams: need some more visuals on how things work or different flows, e.g., showing credit approval flows / scenarios
  • - grammar: need to fix periods vs non-periods ending sentences, inconsistenly—and also, a general grammar sweep

plugins:

  • - include the eliza trading agent, and any change mark mightve made to the existing plugin
  • - Story protocol + Eliza + Recall guide
  • - add more examples with S3 plugin (e.g,. web2 frameworks) since the adapter probably works with many of them

misc:

  • - encryption: Lit, Threshold, and/or client-side examples (likely longer-term, unless we show of js/rust sdk)
  • - sources: put together a real example, relating to the listed use cases (pipelines etc)
  • - protocol: need a bit more information on the "core" actors, like the low-level wasm blobs actor and how it works
  • - links: need to implement link checker for any broken internal links

ai/llm features:

  • - add "copy" button to each page, to extract the md content
  • - and/or do the same for the full site via the existing llms-full.txt endpoint
  • - fix embedding script to only run on merges to main

faq page

  • - how does it ensure the credibility of the information being exchanged? is there a consensus mechanism or some form of validation process?
  • - what is the biggest problem Recall solves for agent devs
  • - what is an AI agent intelligence network?
  • - are you an L2/L1? how do you compare to other blockchain architectures?
  • - why Recall (vs other competitors)?
@dtbuchholz
Copy link
Collaborator Author

dtbuchholz commented Feb 19, 2025

some more input around data verifiability (see question here)

So Recall is more of a decentralized AI verification and knowledge-sharing platform. How does it ensure the credibility of the information being exchanged? Is there a consensus mechanism or some form of validation process?

and these:

  • what is the biggest problem Recall solves for agent devs
  • what is an AI agent intelligence network?
  • are you an L2/L1? how do you compare to other blockchain architectures?
  • why Recall (vs other competitors)?

@dtbuchholz dtbuchholz changed the title Launch content updates Content updates Mar 12, 2025
@dtbuchholz
Copy link
Collaborator Author

see also this friction log: here

@dtbuchholz
Copy link
Collaborator Author

also, we need more details around competitions, and general flow improvements. see this, to start https://gist.github.com/andrewxhill/fc7a2f16684842f4bebc2de235e449e7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant