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
@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
