Me and my platonic sub can confirm >:3
TenorTheHusky
Oh huh, TIL. I had always assumed they were all webkit just due to the amount of compatibility code I've had to implement in CSS with -webkit
styles. It makes sense that a fork like Blink would be backwards compatible with those though
Chromium and its forks actually all use WebKit as well: https://www.chromium.org/developers/design-documents/displaying-a-web-page-in-chrome/
WebKit: Rendering engine shared between Safari, Chromium, and all other WebKit-based browsers.
It seems Kbin's been having some hiccups serving magazines because I've had the same thing with 404 errors - it should work if you refresh a few times
This seems to have been caused by a bug that affected Chromium-based browsers but not Firefox (which is what I use). I didn't catch it right away but it should be fixed now
I will absolutely check this out, thanks for the suggestion!
Edit: I can't get searx working at all for me, but I went ahead and implemented whoogle support
Each one has its upsides and downsides. Kbin's search is more convenient for certain use cases, but it suffers from the same problem as Reddit's search - it always sorts by new no matter what. In addition, it can only index instances with which kbin has federated. FediSearch should in theory index every instance, regardless of federation status, and do so in such a way that the most useful posts show first (assuming Google does its job).
I'm hoping to expand the project to hopefully be a bit more robust - I'll definitely keep this on my radar
Will do o7
Edit: It seems Brave doesn't support chaining site specifiers, so my current method won't work with their search
I would guess that it is the cloudflare protection, since that will have prevented crawlers from indexing the site while it was enabled.
PHP has more $s in it than spez's eyes
We're both ace, so pretty much the things you'd expect, tying up or harnessing, teasing, etc. Just cuddles instead of anything sexual