Names, ideas to mine for names

groundhog idea for browser!!

name:
combine the idea of cloud and earth
or like network in the natural sense?
maybe like airplane mode that's recognizable
aeroplane - some cool synonym like ornithopter
like helioscope is a latin name for sun lens
something about surfing on ground? airboard?
hoverboard?

offline first browser

when it loads, it goes to the home page
then you do something and it very transparently shows you config that you have
state is also a flat file sorta thing. very easy
extremely scriptable, every action can be done remotely
extensions: use firefox / chrome / etc and have some weird ones
once you load a page, it's there forever. Going to it again loads the new copy tho
refresh always loads the latest thing
have a rich ui for looking at the snapshots that you were on
include cached resources, images etc mirror the whole web.

have a soft limit for a single website that's still pretty huge, like 300mb
that's configurable
full ui customization also flat files
3 layers: system stuff
system settings editable by users
user config, incl extensions
you can put files and junk right in there, it's also a file manager after all
command line interface, with lynx style
emacs-style keybindings, and every keybinding can be removed
describe-key of course!
it's also a text editor, why not.

default state is offline. going online adds some sort of flair
connectivity is not assumed, and instrumented. Current internet speed, internet status (offline / stuck in portal / online)
all in progress requests can be canceled, retried. they are timed and after an amount of time it has some helpful ideas.
every download etc supports partial. http3 or something? don't drop that junk
keepalive, reuse connections, shared website cache. need a layer of web client that is running as a daemon and takes requests from browser, command line, etc. So if you load an image on twitter on the twitter app (on this platform) or the twitter website via cli client and web client, same deal. it's cached. it's an image. Detailed explanation for what the website says it wants to cache, and what's the real deal. Assets show all the different sizes. Good developer tools for this.
Developer tools functional as standalone app. also offline. very careful about dumping data / interations / input etc. Command line is permanent. Everything is scriptable. Extensions for developer tools are easy since developer tools itself is an extension. Extensions can have extensions and so on.

Extension has a name: adblock plus
extension 2: depends on adblock plus

good access to "unpacked" extensions. no binary file format for extensions for now.
Really good access to extensions. Less greedy extension scheme. Make it ask when it wants network / disk access.

Use deno. This is a good tool for this world

integrated password manager. "log me in" ("scotty") button.
Browser history stored in a predictable way. use sqlite probably. Query your history, delete from it etc. Undo everything, except "are you sure" delete history "cannot be undone" clear thing. Like that for reset all settings.

update procedure is pretty much bs in firefox these days. Have a "solid core" that doesn't need a restart to upgrade. Be able to go up and down "versions" willy nilly. Kernel is slow to update, perhaps once a month at most, and done in the background optionally? With all state kept. No force refreshes. The page state can be rehydrated from disk. No warn before quitting because everything is still there. No modals actually.

modals:
security alert
alert() is cool though
and confirm()
jump to source code for any page so you can see what's happening
really granular permissions for websites. Like "don't be able to request other domains". Sure they can proxy on their domains but for 99% that would shut them down

robust "i trust this actor" model, where you can say "i don't allow anything on the facebook domain". Entities with multiple domains and a set of permissions, or a permission scheme.