Will
In talking with mobile developer friends, i'm still worried that our regular polling is going to be a big battery drain for mobile use case. We should think about what...
what does this entail?
Is this a a point that's ready for a review?
* I am not aware of a travis instance running somewhere * happy to get github CI set up as well
This is presumably so that we can resume a seed several iterations in without replaying all of the random numbers previously generated to reach the same state.
Re-worked config over https://github.com/ryscheng/pdb/compare/bfabb76796eb1cba154823aa5259a96434ced6c6...pipelined-pir There are now both `ServerConfig` and `ClientConfig` extending a `CommonConfig` with properties that need to be in sync across the two. New trust domains just need...
it seems like conceptually it only needs to be leader -> follower1 leader -> follower2 ... that makes addition / replacement of followers easier since only one other node needs...
there is no user-generated content served from 'orchestrator.strn.pl'. It is only used for L1 registration / communications. As such, something like safe browsing would not help with an overzealous ISP...
There are already a couple factors that help mitigate the abuse potential of an L1 node. As an initial dynamic mitigation, L1s do not serve content from the combined/community-maintained https://badbits.dwebops.pub/...
In particular, the tickets themselves can likely be compatible with “privacy state tokens” - https://chromestatus.com/feature/5078049450098688 which is an API getting built-in browser support for how a user can get a...