@trwnh In a way that part was solved decades ago with iframes: have the header/navigation persistent in one file, and load the different pages, however different they look, in a frame.

@oblomov this is basically ark:// instead of http:// or https:// but you could do the same thing with a petname system: dns -> example.org -> https -> /~user -> /foo/bar

@nclm shame about the security risks

@trwnh Yea, I'm no engineer but I wonder if we could have kept iframes for authoring but have browser makers fixing stuff so that they are more secure / more accessible / whatever were the issues.

@trwnh OK I'm starting to see what you mean, but that still ties user to example.org, and can (and in fact often is) already achieved with subdomains (user.example.org). But this is still tied to example.org so it still delegate to organization before people. I think this might be what I found confusing. If the intent is prioritizing people, wouldn't make the authority part be the user id directly?

@oblomov the authority of example.org/~user depends on the authority of example.org but that's covered by delegation. as far as the top-level resolution you could use something like ark or otherwise retool http(s) to allow user@host.example as an authority component (basically redefining the user component from http basic auth to instead being something else) but that's not the point really. you have a resolver and you have a set of mappings and map prefixes to whatever. just like rdf or n2t

@oblomov wikipedia:James_Joyce might redirect to https://en.wikipedia.org/wiki/James_Joyce and in this case the prefix `wikipedia:` maps to `https://en.wikipedia.org/wiki/`

for a personal web what you'd need to maintain is a mapping of some sort, from people in your address book to some uri prefix they currently own

say i want to resolve (me) -> wikipedia -> James_Joyce, this is an equivalent path to (dns) -> en.wikipedia.org -> https -> /wiki -> James_Joyce

@trwnh@mastodon.social What's become of frames? ​​

@oblomov the relative reference here is that **given https://en.wikipedia.org/wiki and in turn the resource it identifies**, that resource gets to then respond as to what James_Joyce is.

think of every HTTP resource as basically a gateway into its own file server, and a file might redirect to some other resource/gateway/fileserver

@oblomov but as an author i get to just write href="James_Joyce" and it just works no matter where the HTML file ends up being served from

@oblomov (the explanation here is a very unrefined one, admittedly... but i am hoping that by explaining it nonetheless i can reach a more refined state eventually)

@usagi i think theyve been steadily made less useful due to security issues and poor UX