I’ve been playing with the idea of basic search for our basic sites on the basic testnets.
(I’m aware of: this thread, but hoping to get more feedback on some implementation ideas).
Human centric search
So right now, while safe is small indexing could be quite simple. A json file of sites + meta tags (for describing content).
And I’ve made basic steps into a super simple react app for searching this file.
You would maintain your own index. Useful to you, not super useful for all.
Now if that index could reference others you trust… Well then it could periodically ping them and you’re combining your indexes with other peoples. So you get more results that way. And they can do the same.
Any ‘search site’ would be combining a lot of (trusted) people’s indexes. Or indeed just use your own index (which you would need to maintain).
That for me, is basic ‘human centric’ search. No scraping. People maintaining their own lists. Sharing as they find it useful.
You could even have multiple search options in an app (your index, a global index, an index specific for X).
This, theoretically would be nice for garnering results on things that people liked enough to put into their own index AND you only use indexes that you like, and perceive value in.
Bonus: if your list is popular, you get GET rewards (with PtP). Lists could even be weighted with project decorum (web of trust), for example.
That is the theory behind the idea I’m toying with.
List Control: control your list, and what lists you use.
Algorithm Control: no reason you couldnt implement your own algo to get better personalized results.
List Rewards: with PtP, you get rewarded for good content.
SAFE: search is done via the app locally, no search history for anyone to get into.
No ads: Unless you want them. I guess an app could let people bid to show you ads if you wanted. Then you’d get a cut. (I guess that could be it’s own app).
I’ve been thinking about this purely in the small ‘now’ sense, where it would probably work for this forum’s uploaders. But to be useful the idea has to scale. Periodic GET requests would help, but the real problem would be maintaining a list on a user’s computer AND THEN searching any sizeable list. (No PC can match google’s result crunching power).
For a PC for a while this would be fine. This would not work for mobile users. Not realistically.
Can anyone see any other problems / advantageous here? Does it make sense at all? Anyone have any suggestions for overcoming the scaling issue?
I’m thinking to get to grips with the current SAFE API and implement a simple POC (shouldn’t be too complex). But before I fire in, feedback would be appreciated!
(I’d suggest that perhaps you would still use one ‘site’ that would leverage lists as above, but would handle it’s computation on larger scale to tackle larger ‘searches’. But that also feels like a cop out. Surely there is a better / SAFEr way?)