i have to conclude that the biggest barrier to entry to the personal web, aside from obtaining access to hosting, is the expectation that every page on a website has to look the same, be styled the same, have the same navigation menu, and so on.
-
replied to trwnh@mastodon.social last edited by
@trwnh that's what I mean by conflation: http://x/y means both “y according to x” and “you can find this by contacting x and asking it for y”, with DNS telling you how to contact x. The x part doesn't need to be a FQDN, but it does need to be a resolvable (even if only locally) host name. I'm not sure what you mean by the prefix part, don't relative URLs already work that way?
-
replied to oblomov@sociale.network last edited by
@oblomov i mean if i ask for /foo/bar then i don't want to be limited to asking example.org for that. i want to be able to ask example.org/~user directly
the absolute expanded form is example.org/~user/foo/bar and NOT example.org/foo/bar
-
replied to trwnh@mastodon.social last edited by
@trwnh oh I see what you mean here: we could keep using HTTP URLs, but we would have to allow them to be interpreted in a different way (not relying on DNS but having some other mechanism to tell “where can x can be found”). I think that's kind of what the nomadic identity proposals that have been made for the Fediverse try to resolve?
(Can't remember the FEP off the top of my head but you're probably already familiar with it.)
-
replied to oblomov@sociale.network last edited by
@oblomov nah, nothing to do with FEPs or nomadic identity. i mean "prefix" in the literal most direct sense: a completely opaque string with which a URI begins
basically the HTTP server at example.org has to recognize that for all paths starting with /~user that they might redirect or proxy to somewhere other than a local filesystem
every HTTP server is then a name resolver, because the actual final location is irrelevant
-
replied to trwnh@mastodon.social last edited by
current behavior analogy:
GET /foo/bar
Host: example.orgdesired behavior analogy:
GET /foo/bar
Base: https: //example.org/~user -
replied to trwnh@mastodon.social last edited by
@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.
-
replied to trwnh@mastodon.social last edited by
@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
-
replied to nclm@mastodon.social last edited by
@nclm shame about the security risks
-
replied to trwnh@mastodon.social last edited by
@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.
-
replied to trwnh@mastodon.social last edited by
@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?
-
replied to oblomov@sociale.network last edited by
@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
-
replied to trwnh@mastodon.social last edited by
@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
-
replied to trwnh@mastodon.social last edited by
@trwnh@mastodon.social What's become of frames?
-
replied to trwnh@mastodon.social last edited by
@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
-
replied to trwnh@mastodon.social last edited by
@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
-
replied to trwnh@mastodon.social last edited by
@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)
-
replied to usagi@moe.onl last edited by
@usagi i think theyve been steadily made less useful due to security issues and poor UX