@trwnh@mastodon.social Build it

@natalie that's the aim and intent. the hard part is getting everyone to agree on a federated identity system (and to a lesser extent, a standard API for publishing web resources using that identity)

@trwnh@mastodon.social everyone agreeing is an unattainable goal

@natalie to some extent we all converged on using http(s). i think we can do something similar again, or at least i would hope so

i think you could get pretty far with existing technologies like webdav or solid, but i'd really want to see a better way to manage "name to thing" resolution that isn't literally writing an nginx config with location blocks

@trwnh@mastodon.social converging is much different than "getting everyone to agree" tho

@natalie admittedly that was poor phrasing, depending on the definitions of "everyone" and "agree"

in a practical sense i think the closest current option is to assign everyone an FQDN, since that requires the least changes

@natalie i'm still trying to come up with a better answer but that's the societal baseline at least

@trwnh@mastodon.social bsky wins again

@natalie yeah i don’t fully agree with all their decisions but i understand why they made them

virtual host support would probably be quite feasible to retrofit onto existing fedi codebases but i doubt it’ll get done anytime soon