#KevinMarks_A suggestion that a fragmention highlight the exact text and not the containing element has been made
#petermolnarvoxpelli, cweiske I'm taking the search conversation over here: I honestly thought of a dead simple regex search field that just does a regex over text files
#Loqipetermolnar: GWG left you a message 2 weeks ago: I agree
#petermolnarinstead of fancy indexed things like Solr
#voxpelliwell, I'm rather having a constructive discussions about benefits and drawbacks of different solutions than just someone disregarding it for the single fact that it's not independent enough for them
#petermolnarvoxpelli yes, and we all depend on the DNS system
#petermolnarbut that is infrastructure, which we are doomed to depend on
#petermolnarand I'm refusing to view Google as infrastructure
#petermolnarbecause if I do, I'll need to accept the fact that we're in deep shit, where private companies are the actual infrastructure providers and that William Gibson's future is indeed about to happen
#voxpellinot Google specifically, but that kind of search-engines are in their nature something that's suitable to not self-host
#voxpellis/suitable to not self-host/not suitable to self-host/
#petermolnarI'm not convinced X search provider will show the "proper" results
#voxpellithere is http://commoncrawl.org/, but it lacks coverage and frequent recrawls and is mainly meant to try out new algorithms with
#petermolnarwhen I want explicit word in Google results, I'm having a hard time
#petermolnarso my reasoning against depending on services like this is that you cannot rely on them
#petermolnarI could say Google = non-deterministic results
#voxpelliat some point we will probably get Twitter-like search within the IndieWeb as well and that will also have to be more or less centralized (with more actors than in the current search space though, but still not something every hosts themselves)
#cweiskeusing the REST API to have the MP endpoint on a different server, or internally using the REST API?
#GWGThey implemented REST API infrastructure. So a bunch of functions to create custom APIs.
#cweiskeah. I didn't read the "infrastructure" part in the first comment
#KevinMarks_A web search engine can give better results for a given site as it has the link graph of the rest of the web to inform it about that site
#KevinMarks_Also the linguistic analysis derived from the whole web
singpolyma, KevinMarks and miklb joined the channel
#voxpellithinks about the possibility of connecting his node.js micropub endpoint with a wordpress rest api publisher - hmm
#miklbvoxpelli interesting. I looked at a WP plugin that syncs WP with a jekyll github repo
#voxpellimiklb: I'm thinking one could "just" replace the Jekyll formatting and GitHub pushing with a formatter/pusher for the WP APi or any other similar API – mostly a case of mapping everything from A to B (and in the future the reverse as well)
#voxpellicould be fun to maybe do a proof of concept for that against some other API, like Twitter
#miklbI showed someone from GitHub the jekyll-admin gem last week at a patchwork event and his first reaction was "eww, looks like WordPress" :)
#voxpellimiklb: then show them Quill + Micropub and they're like: "yay, looks like Medium" ;)
#voxpelliat work I decided to wrap all our SVG embedding up into a template and for now make that template just embed them inline, and then later maybe we could move to some more DRY mehcnaism when supports for that gets improved