diff --git a/dist/info_not_blazed.html b/dist/info_not_blazed.html index c35807b..868ccaa 100644 --- a/dist/info_not_blazed.html +++ b/dist/info_not_blazed.html @@ -1 +1,42 @@ -Blaze - ooops

Why are some pages unable to be blazed?

The purpose of Blaze is to allow users to navigate the web and access the content they need even in challenging connection situations or when seeking a minimalistic resource and data usage. However, generating a "pure HTML only content page" from every page is not always possible.

Blaze utilizes the same library that Firefox uses to generate the "read mode" of a page, providing a distraction-free and minimalist version for better content absorption. However, this library is primarily designed for reading purposes. Therefore, when navigating to websites like Amazon that do not contain readable content, Blaze cannot generate a minimalistic version of the website.

But the page was an article/blog post!

In such cases, it is possible that Blaze has detected a false positive. It would be greatly appreciated if you could provide the URL of the page where you encountered this message while expecting it to work. This information will help me reduce false positives for other users as well.

Back to blaze \ No newline at end of file + + + + + + + Blaze - ooops + + + +

Why are some pages unable to be blazed?

+

+ The purpose of Blaze is to allow users to navigate the web and access the + content they need even in challenging connection situations or when + seeking a minimalistic resource and data usage. However, generating a + "pure HTML only content page" from every page is not always possible. +

+

+ Blaze utilizes the same library that Firefox uses to generate the "read + mode" of a page, providing a distraction-free and minimalist version for + better content absorption. However, this library is primarily designed for + reading purposes. Therefore, when navigating to websites like Amazon that + do not contain readable content, Blaze cannot generate a minimalistic + version of the website. +

+

But the page was an article/blog post!

+

+ In such cases, it is possible that Blaze has detected a false positive. It + would be greatly appreciated + if you could provide the URL of the page + where you encountered this message while expecting it to work. This + information will help me reduce false positives for other users as well. +

+ Back to blaze + + diff --git a/dist/not_blazed.html b/dist/not_blazed.html index 9a7042e..fe8910f 100644 --- a/dist/not_blazed.html +++ b/dist/not_blazed.html @@ -3,6 +3,7 @@ + Blaze