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?
Are you sure you want to delete the OAuth client [Client Name]? This action cannot be undone and will revoke all access tokens for this client.
Are you sure you want to revoke the OAuth token [Token ID]? This action cannot be undone and will immediately revoke access for this token.
#json 1 hashtag

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.