November 8, 2024 Friday
The place to begin understanding Brave Goggles in detail:
https://github.com/brave/goggles-quickstart
I am finding that trying to create a “goggle”, is a daunting task. Looking at the following webpage:
https://github.com/brave/goggles-quickstart/blob/main/goggles/quickstart.goggle
! name: Quickstart
! description: A quick tour of Goggles
That requires a lot of study. Read some, look up online, what some of the stumbling blocks mean, take a break, and more study later.
This part, has me stumped:
! Another set of options can be used to indicate what you want your instruction
! to target. By default any instruction will apply to a URL, but we will add the
! ability to match other aspects of a page too, in the future:
!
! web3$inurl
! web3$intitle
! web3$indescription
! web3$incontent
What is “web3”? No example, no illustration that clarifies.
In my first draft of a “goggle”, I have a line that is simply:
$incontent
Because, I want the Brave Search engine to focus upon, using my search criteria. I expect each of the search results - the webpages - to include visible content, the words that I used in my search criteria.
But I am frustrated by not knowing, how that line of instruction will work - because, there are no example / illustrations.
In general, the task for the Brave Search user, in trying to create a “goggle” and then store their “goggle” online, is an obstacle course.
In order to store your new “goggle” online, I did find some worthy guidance that has examples/illustrations about, how to use GitHub Gist:
https://www.liquidweb.com/blog/what-is-a-github-gist/
I believe, it is important for Internet users, to find that type of guidance that walks you through the steps that you will encounter . . . BEFORE . . . trying to take the steps.
For example, what “Authentication” means to the author of some instructions, may not be what “Authentication” means to the readers.
For examples of actual “goggles” - the text lines - see:
https://github.com/brave/goggles-quickstart/blob/main/getting-started.md#goggles-syntax
There, scroll down to: “Examples of valid Goggle URLs”
In addition, there is a member [“tonsooton”] of the Brave Community, who recently [Nov. 7, 2024] included in his post about:
Almost all Japanese old websites display broken on search results
. . . a link to a “goggle” that he created:
https://raw.githubusercontent.com/tonsooton/BraveSearch_Goggles_JP/master/abehiroshi.goggle
Footnote re the Liquid Web article:
Effectively Use GitHub gists
https://www.liquidweb.com/blog/what-is-a-github-gist/
An excerpt:
GitHub gists Types
There are two types of GitHub gists available. Public and Secret. Public GitHub gists show up in Discover, where people can browse new GitHub gists as they’re created. They’re also searchable, so you can use them if you’d like other people to find and see your work. Unless you are logged in and the secret gist’s author, secret GitHub gists do not appear in Discover and cannot be searched.
Secret GitHub gists aren’t exactly private. A friend will be able to see a secret GitHub gist if you send them the URL. However, your gist GitHub will also be visible to anyone who finds the URL, including people you don’t know. Instead, you might want to create a private repository if you need to keep your code hidden from prying eyes.
That part, I mention here, because I wonder if the Brave Search engine results will somehow inadvertently include the URL address of my private [“secret”] “goggle” that is for my own use. Can somebody (some archival thing on the Internet) grab that URL info?
I wonder, because as the Liquid Web article points out:
“your gist GitHub will also be visible to anyone who finds the URL, including people you don’t know”
@clifton - I am hoping my remarks will be of interest; tx.