this post was submitted on 24 Sep 2024
1 points (100.0% liked)

Fediverse stuff

0 readers
14 users here now

This is a magazine dedicated to posts about the Fediverse and things related to it. This is a MBin magazine, but you can follow it from Lemmy or Piefed as well. If you want to post specifically about Mbin feel free to post into !mbinmeta@gehirneimer.de

Recommended magazines

Rules

  1. Please stay on topic, if it's off-topic please write [META] in the title. Please report off-topic posts if you see them.
  2. Try to avoid drama related posts, for this type of content you can go to !fediverselore@lemmy.ca

founded 1 year ago
MODERATORS
 

idk where to really put this (might turn into a blog post later or something). it's what you might call a "hot take", certainly a heterodox one to some parts of the broader #fediverse community. this is in response to recent discussion on "what do you want to see from AP/AS2 specs" (in context of wg rechartering) mostly devolving into people complaining about JSON-LD and extensibility, some even about namespacing in general (there was a suggestion to use UUID vocab terms. i'm not joking)

1/?

you are viewing a single comment's thread
view the rest of the comments
[–] blaine@mastodon.social 1 points 4 months ago (17 children)

@trwnh@mastodon.social fun fact, webfinger actually supports URLs and [in theory] phone numbers!

The key (and this is a social science and cultural insight, not technical) is that when you ask someone's "name" or "address" they need something that's unambiguous, personal, and opaque in the sense that it works everywhere (online / distributed, it needs to be globally unique, too) or they won't use it.

Bare domains aren't ideal because (1) they're expensive and (2) management is hard.

[–] blaine@mastodon.social 0 points 4 months ago (14 children)

@trwnh the "trick" with webfinger is that it's a way to go from a "name" to an authoritative context (the authority for "x@y.xyz"' is "y.xyz" and the authority for "blah.com" is "blah.com"; the challenge with phone numbers is that it's impossible to infer the authority for +1-416-867-5309 / telcos don't provide a lookup system). That's really it; the rest is a cultural thing.

[–] trwnh@mastodon.social 0 points 4 months ago (13 children)

@blaine there might not be an authority for a phone number but i think it can be handled more like a combo of "local dns resolver" + "registry of phone number". sure in many cases with identifiers that have an authority component you can just use their webfinger if they have one, but i think it would also be cool to be able to use your own webfinger and "proxy out" as needed, in the same way that dns does it

[–] blaine@mastodon.social 1 points 4 months ago

@trwnh@mastodon.social for sure; lots of ways to deal with the phone number lookup thing, but "security is hard" in that context 😅

aside: I did a little work a couple of years ago on a thing I was calling "NNS" (the "Name Name System") around how we might use modern cryptographic assertions to step back from the relatively "centralized" mode of DNS (and by proxy, webfinger and atproto's approach), but then IPFS etc imploded and the funding/interest dried up. There are some similar efforts out there, too.

load more comments (12 replies)
load more comments (12 replies)
load more comments (14 replies)