News from fediverse

0 readers

1 users here now

founded 10 months ago

submitted 1 month ago by [email protected] to c/[email protected]

96 comments fedilink hide all child comments

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

[–] [email protected] 0 points 1 month ago (1 children)

@blaine @by_caballero i was thinking more that you could declare a tel: as one of your "aliases" at your authoritative wf and then it percolates through the rest of the system

[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] @by_[email protected] since tel: is extremely fraught, especially nowadays with insane phone spam etc, a Signal/WhatsApp/etc address might be a good alternative example?

I particularly like the "established encrypted messenger" example because the wf->[rel=messenger]-> lookup could get Fedi encrypted DMs "for free."

(obviously lots I'm glossing over that make it more complicated, but in theory it'd be less complicated than many alternatives)

[–] [email protected] 1 points 1 month ago

@[email protected] @by_[email protected] (one thing to note is that it's not possible to declare an alias, e.g. a phone number in a wf or other profile, and then use that alias in reverse as a way to look up the original profile. I mean, one could do it, but with questions of identity at play it would be an incredibly very extremely bad idea to do that from every conceivable security perspective.)