This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will block this actor and hide all of their past and future posts. Are you certain you want to block this actor?
This action will block this object. Are you certain you want to block this object?
#serci 8 hashtags
It has been a while since I worked on #serci, but here is a new feature, I've been thinking about for a while but didn't have time to implement it until today: Extended options for search engines.
https://src.jayvii.de/pub/serci/commit/4a990c43d256913923eed1acc1c206e470b54df2.html
This is actually quite a small (but IMO useful) feature that let's serci parse additional text to the search engine, besides the search term. Or, as another way to think about it, it gives the user more options to tell serĉi your intent. Options are added to the keyword with the ":" separator.
Say, you want to search explicitly on the German version of Wikipedia. You can do that now with !wp:de
Or you want to translate from German to Italian with DeepL. Just use !deepl:de/it
On yesterday's #serci Update post (https://social.jayvii.de/objects/MVKQo4c6huo), today I finished a massive overhaul of the web-frontend for this Meta² search engine.
Besides looking a lot slicker, it should be a lot easier to understand for new users now. The list of search engines can now be searched and filtered and your personal default search engine can be chosen easily with a single click! I also added descriptions for each search engine, to make the list easier to browse and understand.
Feel free to try it yourself! https://search.jayvii.de
Oh, and the re-factoring increased performance by 33%! Searching on average takes 0.12s before redirect (same as before), but loading the web-frontend takes only 0.18s instead of 0.28s now. Really happy with how it turned out. Still: any suggestions are more than welcome!
I have been adding quite a few more search engines to #serci today, including #Fireball, #SearX/#SearXng, #eTools, #TigerCH, #WolframAlpha and #DBLP today. All new additions are already live at https://search.jayvii.de.
With 64 search engines in the default configuration, I feel like the webfrontend has to present all the options in a better way. But I am really out of ideas on what that could look like... Suggestions are very welcome! #webdev #php #foss #search
Two more minor changes in #serci:
1. You may set the default search-engine now via the "default_search" GET argument. This is useful for private browser windows or browser like #FirefoxKlar. Simply set your search engine to https://search.jayvii.de/?default_search=metagerweb&q=%s and the default search engine will be MetaGer. More: https://src.jayvii.de/pub/serci/commit/c11ef8fd6539487afd95c6ff767f3e2bdf663cc5.html
2. I also added the #nona search engine to the default configuration file. More: https://src.jayvii.de/pub/serci/commit/d23d91f19df8bd43132a9363f3cf7501afbc3f0a.html
Two new changes in my Meta² Search Engine #serci:
1. Due to #MetaGer being forced to disable their advertisement financed gratis offering, the default search engine is now france-based #Qwant
2. Users are now able to choose an individual default search engine via a drop-down from all configured search engines. This will set a cookie in your browser.
So, if you (like me) want to continue using @metager@suma-ev.social via the paid tokens (or support them via a membership, which I would urge you to do), you can set it as your personal default search engine in serĉi again :)
Change-Logs for these two serĉi changes:
1. https://src.jayvii.de/pub/serci/commit/8634b8ee623f1b7abfc1815ea8aab53a643683af.html
2. https://src.jayvii.de/pub/serci/commit/9b9da13251d2e1fec60631846fc3d22c29c08df6.html
The move to a different VPS actually increased the performance for the HTML-building of #serci substantially from 0.28s above to 0.19s over 100 trials (also, this might have to do with #PHP updates and smarter Apache configuration). Redirection does not differ. This is likely the minimal overhead I can achieve.
After a few performance improvements, I did some loading time tests for #serci, between my home network (wifi) and a random VPN where the service is running.
echo "html,redirect" | tee timestamps.csv for i in $(seq 1 1 100); do HTML=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de) REDI=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de?q=test) echo "$HTML,$REDI" | tee --append timestamps.csv done
Across 100 runs for loading the site's HTML (generated from pure #PHP) versus a redirect to a chosen service (here the default #MetaGer), I can measure on average 0.28s for loading the frontend (HTML) and 0.13s for processing input and issuing the redirect.
I am quite happy with this relatively low overhead, although performance may decrease a little if more services are added (currently: 47). At some point maybe an #sqlite database may be more efficient than my pre-constructed #json files which are loaded on-demand.
New #serci updates:
Try it out at search.jayvii.de, contribute or self-host serĉi at https://src.jayvii.de/pub/serci/
Older posts about serĉi: