Václav Pavlín
@vpavlin
Dear Farcaster-verse, can you help me test an app I created? It's called Qaku - Q&A over Waku - https://qaku.app It is a stateless webapp which only relies on @Waku_org for short-lived Q&As. It is fully decentralized - the only infra is Waku Network and Qaku browser instances. It uses Event Sourcing approach to resolve current state and Waku Store protocol as a "database" (hence the short-liveness of the Q&A as they go eventually dumped from Store nodes) Please go an play around with it, create a Q&A, record feedback and let me know what works, what doesn't and what do you think in general. I'd like to push for Qaku to be actually used internally, but would appreciate feedback from random humans of the world:) Here is an existing Q&A, so you can post your feedback there, so that we get a big one:) https://qaku.app/q/X0d906767/4brh37 Github: https://github.com/vpavlin/qaku PS: If you want to help, pelase retweet:)
1 reply
0 recast
0 reaction
Václav Pavlín
@vpavlin
1. Initial load will take a bit longer becasue the Waku node is discovering peers from scratch and that takes some time. Subsequent loads should be much faster. 2. If you get stuck with a spinner spinning, reload, there is some race condition somewhere and I did not spend enough time to find it yet:) 3. Check the browser console (F12) for errors, Websocket connection failed errors are expected - some nodes are still in discovery DHT, but not actually online, so connecting to them fails. Errors about Store query failed with status code: 300 are also known and are related to bad nodes in the network, js-waku team is looking at how to mitigate using bad Store nodes
0 reply
0 recast
0 reaction