kagisearch / kagi-docs Goto Github PK

Relevant Page(s)

https://kagi.com/pricing

Description

https://kagi.com/pricing has what I assume was a changed url. During the update the pricing page was missed. If you go to pricing, under faq, “why should I pay for search?” The URL is https://help.kagi.com/kagi/why-kagi/why-pay.html
But should be https://help.kagi.com/kagi/faq/faq.html#why-should-i-pay-for-search

I assume this happened when it moved from a dedicated page.

Thanks got the engine and the help.

Relevant Page(s)

https://help.kagi.com/kagi/getting-started/setting-default.html#chromium_browsers

Description

Testing these steps out in Opera and Chrome doesn't work for me.

Those browsers seem to be locked down to even reject changes when made manually: https://forums.opera.com/topic/32795/can-t-set-custom-search-engine-as-default/20

Hoping that there's a way for this to be the default search engine without needing to specify a k command. Using Alfred has been great though, and that should get me through until there's another option.

I really like Orion, but I need a workspace solution like Opera provides to help me manage my tabs

Relevant Page(s)

https://help.kagi.com/kagi

Description

When reading about Kagi's $10/mo unlimited search plan, I went to the docs for setting the default browser and noticed it was somewhat difficult to differentiate the links from the background due to the contrast. I used the Pika app to measure the colors and found white (#FFFFFF) for the background and imperial yellow (#F4B544) for the link text, giving it a contrast ratio of 1.82. This greatly misses the mark for WCAG's color contrast standard, which is a general target for accessibility (they recommend at least 3:1).

In dark mode, the colors are a lot clearer to see, but I think a deeper shade of orange would help for people like me who don't always use it.

Relevant Page(s)

https://help.kagi.com/kagi/why-kagi/why-pay-for-search.html#ad-supported-search-engines-the-future-of-the-web

Description

From the page (my emphasis and reference numbers):

In the early days of Google, in 1998, its founders rightly recognized that it is an imperative for a search engines to remain ad-free⁽¹⁾:

[---]
For this type of reason and historical experience with other media [Bagdikian 83], we expect that advertising funded search engines will be inherently biased towards the advertisers and away from the needs of the consumers⁽²⁾"
— The Anatomy of a Large-Scale Hypertextual Web Search Engine, Sergey Brin and Lawrence Page, 1998

Unfortunately, this is not how it played out⁽³⁾, and over the last 20 years we proceeded to witness the great detoriation of web and search as a result.

I assume that (3) is meant to refer back to (1) but to me when read in context it seems to refer back to (2), which makes it a surprising and arguably false statement.

(Note also that (1) does not correctly summarize the quote, but either refers to the context in the source outside of the quote or interprets the quote and draws its own conclusion.)

I would probably change (3) to "Unfortunately, this is exactly how it played out", and possibly change (1) to better reflect what is actually said in the quote.

(Also, there is a typo in (1): "a search engines" mixes singular and plural.)

Relevant Page(s)

https://help.kagi.com/orion/browser-extensions/macos-extensions.html#managing-extensions

Description

Where is Window > Extensions?

Relevant Page(s)

https://help.kagi.com/kagi/why-kagi/why-pay-for-search.html

Description

The second sentence in the page Why Pay For Search has a dead link to a deleted twitter post. You can see the archived tweet here.

Since this is a prominent page in the docs, I wanted to ask your thoughts before making a PR. I could either:

1. Extract the photo from the archived tweet and add it to the repo. Then link to that picture.
2. Link directly to the tweet in archive.org
3. Delete the link entirely

Let me know that you think is best

Relevant Page(s)

https://help.kagi.com/kagi

Description

Normal Firefox Android instructions for adding Kagi doesn’t really work with Firefox Focus, as it will clear all session data when the app is closed. Instead I manually added the search engine with the token format https://kagi.com/search?token=TOKEN&q=%s.

This is unrelated, but for possible kagiers who are trying to find out instructions: to add Kagi to Sailfish OS’s built-in Browser, just logging in and Kagi gets added to list of search engines to be installable automatically.

Description

api request return an unauthorized response. I'm on a legacy profession plan and also have positive api balance.

Steps to Reproduce

export TOKEN=<api token>
curl -v -H "Authorization: Bot $TOKEN" https://kagi.com/api/v0/search\?q=steve+jobs

Expected Behavior

return 200 response

Current Behavior

return Unauthorized

*   Trying 2600:1901:0:daa1:::443...
* Connected to kagi.com (2600:1901:0:daa1::) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=kagi.com
*  start date: Feb 10 13:44:25 2023 GMT
*  expire date: May 11 13:44:24 2023 GMT
*  subjectAltName: host "kagi.com" matched cert's "kagi.com"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55742ec492e0)
> GET /api/v0/search?q=steve+jobs HTTP/2
> Host: kagi.com
> user-agent: curl/7.74.0
> accept: */*
> authorization: Bot <api token>
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 401
< x-request-id: e5236901-746a-4cbb-8b2e-7cf068a14508
< cache-control: no-store
< content-type: application/json
< content-length: 12
< date: Mon, 03 Apr 2023 10:52:12 GMT
< via: 1.1 google
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
<
* Connection #0 to host kagi.com left intact
Unauthorized------------

Relevant Page(s)

https://help.kagi.com/kagi/

Description

There is no favicon on help.kagi.com. Might be useful to include this to help users identify tabs/windows open with Kagi docs.

Relevant Page(s)

https://blog.kagi.com/blog — example of an affected URL

In fact, all URL paths at blog.kagi.com except for / exhibit this issue.

Description

A GET request to https://blog.kagi.com/blog returns HTTP 200 OK.
A HEAD request to the same URL returns HTTP 404 Not Found.

This is a broken situation; a HEAD request needs to return the headers/response codes that would be sent in response to a GET request for the same URL.

I discovered this from my email newsletter tool, which, before sending a newsletter, checks for broken links using HEAD requests to save bandwidth. All the links/URLs from blog.kagi.com were reported as broken.

I tried to find a better place to report this issue, but could not find one. The blog doesn’t appear to have its own public repo.

Relevant Page(s)

https://help.kagi.com/kagi/plans/why-pay-for-search.html

Description

Last section on https://help.kagi.com/kagi/plans/why-pay-for-search.html contains two broken links:

[Learn how to Pick a Plan](https://help.kagi.com/kagi/plans/why-pay-for-search.html#learn-how-to-pick-a-plan)

We make it easy to pick the plan that is right for you, take a look at our [Plan Types](https://help.kagi.com/kagi/plans/plans/plan-types.html) and review our [Pick The Right Plan](https://help.kagi.com/kagi/plans/plans/pick-the-plan.html).

Suggestion: Should instead link to:
https://help.kagi.com/kagi/plans/plan-types.html
https://help.kagi.com/kagi/plans/pick-the-plan.html
(Remove the duplicate "plans/plans" from the urls)

Relevant Page(s)

https://kagi.com/pricing

Description

At the bottom of Kagi's pricing page, under "I have more questions!", there's a broken link to the FAQ.

Markdown with broken link:
See our [FAQ](https://help.kagi.com/kagi/company/faqs.html) or feel free to reach out at [[email protected]](mailto:[email protected]).

Fixed version:
See our [FAQ](https://help.kagi.com/kagi/faq/faq.html) or feel free to reach out at [[email protected]](mailto:[email protected]).

I'm adding this as an issue here because it concerns documentation, but technically the kagi.com pages fall outside the scope of the kagi-docs repo. (Otherwise I'd just create a PR 😅)

Relevant Page(s)

• https://help.kagi.com/kagi/getting-started/index.html
• https://help.kagi.com/kagi/plans/plan-types.html

Description

If you open one of the links above, a large, clickable right-facing arrow is shown on the right side of the page. When clicked, it's meant to navigate to the next page. It works as expected for most pages, but not for some, including the pages I've linked.

The reason seems to be that the relevant pages are linked to twice:

- [Getting Started](./getting-started/index.md)
	- [Quick Start](./getting-started/index.md)

- [Plans & Payment](./plans/plan-types.md)
	- [Plan Types](./plans/plan-types.md)

(source)

My guess is that mdBook simply links one page's next button to the next page in the list, so if the next page in the list is the same as the current page, the current page links to itself.