Comments (1)
Orbit community call
date: Tue 21st of August, 2018
notetaker: @RichardLitt
moderator: @shamb0t
Participants
- Richard (@RichardLitt)
- Shams (@shamb0t)
- Huy (@huyhoangCSUH)
- Tim (@coyotespike)
Agenda
-
Haad and Thiago are feeling under the weather, we think, so just us today.
-
@RichardLitt: Update on acl work (@thiago, @shamb0t)?
- orbitdb-archive/ipfs-log#145
- @haadcode and @shamb0t will be working on this this week. Closed one PR, opened up a new one.
- Still working on it. The actual ACL may just be a wrapper, instead of having the fxs implemented in a module.
- A concrete implementation without allowing a random function to be passed in.
- Also some little superficial changes.
-
@RichardLitt: Update on indexing request orbitdb/orbitdb#220
-
@rjharmon: doc fixes for onboarding errors orbitdb-archive/orbit-db-docstore#10
- Shamb0t will be working on this starting on Monday
-
Questions (Huy@colony: https://github.com/huyhoangCSUH):
- What is the Index in the store?
- Either you have to know them in advance (the only way currently.) There's an issue on general indexing, which may refer to the same thing.
- The docstore references the same kind of issues. If I open a DB, and I want ot index on title or location, then I need to open an array.
- You have to know the fields a priori; the manifest might be a good place to put this.
- What if we indexed it not by the names of the fields, but a field in the manifest on the app level that might help? @shamb0t
- Imagine we have some info we need, shared among those db notes, such as indexing (on various fields; title, id, etc.)
- Currently, there is no way to know from the db itself which field has been indexed. If you have implemented the db yourself, this is not a problem. How could we know which field has been indexed before opening the Db?
- A self-describing index. Tim thinks it is a great idea.
- @shamb0t: should we keep it as index or indices, or a field like meta, which should be known before at the app level?
- Anything other than indices that you would need?
- Tim: I can't think of anything, but I think of the meta field as insurance, or future proofing - it lets us add extra properties besides the index type in the future.
- Is the index of
docstore
stored in the_index
field of thestore
object? It looks like the manifest doesn't store indexed field.- The store index and the search index are different. The store index is built as each store fast-forwards over the CRDT log. Shams may store this index as a key-value store and put the address in the manifest of each store, so that each node does not have to build the index from scratch.
- How does the current index in
docstore
work? Is it stored in memory when the database is loaded?- Yes, basically everything is built in memory.
- More explanation on
mapper
inquery()
ofdocstore
. Does it help retrieving only certain fields? As of now, it seems thequery()
function returns all fields in the objects. Should we use mongoDB style?- Huy will open an issue proposing higher-level queries to implement.
- Discussion on generalizing indexing: orbitdb/orbitdb#437
- What is the Index in the store?
-
@RichardLitt: Logo update
-
@RichardLitt: PR about process for making these community notes, feedback would be good #18
-
Gitter channel! https://gitter.im/orbitdb/welcome
-
Privacy?
- Right now, it's all public. We're looking at Read only access, but that's far off. For now, encrypt before throwing stuff in.
- We are looking into proxy-read encryption, and write access is the ACL stuff. But still big, not auditing, and more work to do.
from welcome.
Related Issues (20)
- OrbitDB Community Call: August 6 1400 UTC
- Repo Health Checks HOT 7
- OrbitDB Community Call: August 20, 1400UTC HOT 4
- Basic example of chat functionality using OrbitDB HOT 1
- OrbitDB Community Call: Tuesday September 3rd at 1400UTC
- OrbitDB Community Call: Tuesday September 17th at 1400UTC
- OrbitDB Community Call: Tuesday October 1st at 1400UTC
- Add bridged badges to all repositories with Gitter badge HOT 1
- OrbitDB Community Call: October 29 1400UTC
- OrbitDB Community Call: November 12 2019 1400 UTC HOT 1
- OrbitDB Community Call: November 26, 2019 at 1400 UTC
- OrbitDB Community Call: December 10th, 2019 at 1400 UTC
- OrbitDB Community Call: January 7th, 2020 at 1400 UTC Community Call
- OrbitDB Community Call: January 21
- OrbitDB Community Call: February 4th at 1400UTC
- OrbitDB Community Call: February 18 HOT 1
- OrbitDB Community Call: March 3rd
- OrbitDB Community Call: March 31st, April 14, April 28
- Could not validate signature
- Documentation compilation HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from welcome.