I wanna post my idea for decentralised search again.

[bri7@social.treehouse.systems]

it is then important that we begin treating search indexes as static assets, rather than an opaque api endpoint. something that is inspectable, scorable, filterable, cachable, archivable

don’t like that a search engine doesn’t show you exact phrases, or doesn’t index ‘{‘

frustrations aroumd being unable to find the music group “The The”?

you can fix it if you have the indexes and the indexers

sieze the means of discovery

[bri7@social.treehouse.systems]

Seize The Means Of Discovery

[bri7@social.treehouse.systems]

let’s do for search indexes what RSS did for blogs, make site indexes statically findable, generatable, cachable and aggregatable

[oblomov@sociale.network]

@bri7 you mean something like the sitemap.xml or something more sophisticated?

[bri7@social.treehouse.systems]

@oblomov go back to first post in the thread please *facepalm*

[oblomov@sociale.network]

@bri7 oh damnit Tusky wasn't even showing me that this was a thread when I replied. I'll go read.

[oblomov@sociale.network]

@bri7 OK I've read the whole thread now 8-D

I wonder if a YaCy instance per website would do what you want.

[bri7@social.treehouse.systems]

@oblomov no

[bri7@social.treehouse.systems]

@oblomov YaCy is just a completely different thing from what I am talking about. So is sitemap.xml.

And yes people do usually bring YaCy up when i talk about this idea. It’s kind of discouraging, makes me think I am not explaining myself well enough

[oblomov@sociale.network]

@bri7 it's not the decentralized search per se, it's the search index, weighted web of trust, etc. AFAIK these are all things that YaCy provides (and ties together). Maybe you can clarify why something like a per-website YaCy instance does NOT fit the bill?