Frogans Addresses and Family Trees
There may be those who will be quick to believe that a frogans address is little more than a dressed-up URL, that it exists merely as a mechanism for financing Frogans Technology development and the MFN (Main Frogans Network). Hogwash, I tell you. Dare I suggest that with frogans addressing we’re witnessing yet another step up the IT evolutionary ladder?
While ultimately frogans FSDL documents and other resources that make up frogans are transferred by HTTP, as Web pages are, the implementation of the frogans address as intermediary adds a layer of usability for the end-user and convenience for the publisher, leading to all-around functionality for everybody.
For end-users, they access frogans using a format of addressing that is really simple (ex: “frogans*example“, or “frogans*example.extension“). If only the Web were so easy. Ever copy and paste a URL only to have left out the “h” in “http://”? Or you’ve typed two “w”s instead of three? Or how about trying to recite a complete URL over the phone, and finally saying “Oh, I’ll send you an email…”
For frogans publishers the convenience of the frogans address is in its flexibility. The address of a frogans is independent from where on the Internet its resource files are physically located. A frogans address stays the same regardless of where its frogans is hosted, at what IP address or domain name, or in which directory. That information is instead kept in the registrant’s frogans address settings, and can be updated at any moment – and without the kind of delay that you get when, say, you want to redirect your domain name.
If a publisher of frogans so chooses, they can group frogans together in the frogans’ contextual menu by their addresses. This is done by giving different frogans a common “frogans family name” in their frogans address, and differentiating them with personalized extensions.
Remember way back when, two paragraphs ago, when I gave as an example “frogans*example.extension“? Here “example” is a frogans family name. “extension” is its extension (duh). The person who has registered “frogans*example” or “frogans*example.extension” has the exclusive right to use “example” as a family name in as many other frogans addresses as they like, each having its own extension:
- frogans*example.butterflies
- frogans*example.fish
- frogans*example.nets
- …
When you visit a frogans, the Frogans Player will detect the addresses of other frogans sharing the same family name and display them in the contextual menu of the frogans being visited. This is useful for associating different frogans thematically, particularly if it is desirable to quickly have a several different frogans family members on-screen simultaneously.
Don’t confuse the extension with a subdirectory. They have nothing in common. The frogans address extension denotes a unique frogans address for an entirely unique frogans. Different frogans in the same frogans family don’t even have to have the same hosting, for instance. Hop away, little frogans. Be freeee!