1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-23 12:52:10 +00:00

Compare commits

..

2 commits

Author SHA1 Message Date
Seirdy
bb29820fa3
disclose update to link to kloak 2024-11-20 15:56:31 +00:00
Seirdy
738b7cf9bf
Add new gigablast instance 2024-11-21 01:06:36 -05:00
3 changed files with 5 additions and 1 deletions

View file

@ -10,6 +10,6 @@ syndicatedCopies:
Real time collaboration software and text boxes that rapidly save drafts to the cloud essentially log your fingerprintable typing behavior. The industry refers to this information as "keystroke dynamics" or "typing biometrics".
Other modern "operator signatures" are easier to minimize. A user can learn to [obfuscate writing style]({{<relref "/posts/stylometric-fingerprinting-redux.md">}}), or can use keyboard navigation with different pointing devices to limit [fingerprinting of mouse behavior](http://jcarlosnorte.com/security/2016/03/06/advanced-tor-browser-fingerprinting.html).
Other modern "operator signatures" are easier to minimize. A user can learn to [obfuscate writing style]({{<relref "/posts/stylometric-fingerprinting-redux.md">}}), or can use keyboard navigation with different pointing devices to limit [fingerprinting of mouse behavior](http://jcarlosnorte.com/security/2016/03/06/advanced-tor-browser-fingerprinting.html). <ins datetime="2024-11-20T15:56:31+00:00">Update: switched link to Kloak to Whonix' updated fork.</ins>
Keystroke biometrics are difficult to anonymize without [installing software such as kloak](https://github.com/Whonix/kloak) or browser extensions (the latter of which may add fingerprintable vectors) designed to cloak some of your typing habits. Signature typos, approximate typing speed, etc. will still leak. Alternatively, we could normalize typing messages out in a simple offline editors that don't store revision history before pasting them into other input fields.

View file

@ -132,6 +132,7 @@ These engines fail badly at a few important tests. Otherwise, they seem to work
* Secret Search Engine Labs: Very small index with very little SEO spam; it toes the line between a "search engine" and a "surf engine". It's best for reading about broad topics that would otherwise be dominated by SEO spam, thanks to its CashRank algorithm. Allows site submission.
* Gabanza: a search engine from a hosting company. I found few details abou the search engine itself, and the index was small, but it was suitable for discovering new pages related to short broad queries.
* Jambot: docs, blog posts, etc. have not been updated since around 2006 but the engine continues to crawl and index new pages. Discovered in my access logs. Has a bias towards older content.
* search.dxhub.de: while Gigablast seems dead, a version of it was open-source. This based on that version of Gigablast. Its index is small but results are still useful for surfing new unseen corners of short-tail queries.
=> https://github.com/chatnoir-eu ChatNoir source code (GitHub)
=> https://groups.google.com/g/common-crawl/c/3o2dOHpeRxo/m/H2Osqz9dAAAJ ChatNoir Announcement

View file

@ -167,6 +167,9 @@ These engines fail badly at a few important tests. Otherwise, they seem to work
[Jambo](https://jambot.com/)
: Docs, blog posts, etc. have not been updated since around 2006 but the engine continues to crawl and index new pages. Discovered in my access logs. Has a bias towards older content.
[search.dxhub.de](http://search.dxhub.de/?c=main)
: while Gigablast seems dead, a version of it was open-source. This based on that version of Gigablast. Its index is small but results are still useful for surfing new unseen corners of short-tail queries.
### Fledgling engines
Results from these search engines don't seem particularly relevant; indexes in this category tend to be small.