Test dat.js

[eklem]

https://docs.datproject.org/docs/browser-intro

Look into how

• [ ] one user can create a search-index (the actual data)
• [ ] that user can (?) continue the process in another browser
• [ ] that user can share read access to the search-index (actual data) + search engine name

This way, people that starts search engines can get to a point where they think their search engine could be usable for others, and then go from there.

Share address could be [username].nowsearch.xyz/[enginename]. For the user with write access, the engine will also always be accessible through nowsearch.xyz/[enginename]

[eklem]

Will be superceded by Dat SDK. The longer time it takes before I start, the biggeer chance it will be using the SDK and not Dat.js.

[eklem]

Check out the hypertrie example

[eklem]

Basing it on hypertrie will be good for later use cases too, having the possibility for multiwriter scenarios where you can have several people contributing to data for a search engine.

[eklem]

So, Hyperdrive v10 could be the base for this, storing the data that should be indexed. Creating a new JSON-file for i.e. every 1000 item / document. If you want to colaborate we could do some behind the scene mounting of each colaborator's Hyperdrive into the others Hyperdrive. This way you could easily connect and de-connect colaborative search engines. I.e. making a recipe search engine, you're invited to someone elses.

Stuff that could be interesting, and possible to grasp for users:

• Syncing your own search engines between browsers on different gadgets (phone, laptop, work-computer, SmartTV, etc)
• Letting others see (sync with) your search engine
• Collaborate on a search engine, keeping ownership of the content you've added.

Syncronisation part

• Could be a paid service, but this means storing other peoples content on our server.
• Starting with only syncing when having the search engine open in browsers on both gadgets.
• Other ways of making money: Connecting domains to a search engine. This could possibly work without any sync-service on the server, only browsers. Could be a way of growing search engines organically, starting with your own private search engine, and gradually opening up for some friends and then the public, and also having several contributors.
• Maybe a server client for self hosting of content (serving as a sync seed), also making sure nobody stores illegal stuff on our server.

[eklem]

Need to wait for browser-version to land.

[eklem]

Hyperdrive to solve the file and folders synchronization. And dat-store to keep a backup seed going. Could be a wrapper around client, making sure the proper URL is used, etc.

https://github.com/datproject/dat-store

[eklem]

Dat or hyper stuff is focusing too much on node.js-stuff, and the browser things seems to lag behind. Will drop that idea for now and look into making something simpler with Webtorrent.