It's easy to do. Here are some examples: https://www.packetizer.com/ws/webfinger/server.html I actually serve up content using both static files and via dynamically generated content, depending on the domain and needs.
That's not a WebFinger URL. WebFinger URLs point to /.well-known/ path that returns a JSON document with links to other places for the user. To simplify WebFinger use by a human, we introduced acct:user@example.com…
I was the editor of the H.323 spec years ago. Funny you would say that SIP looks like it comes from the telcos, when the whole aim with SIP was to create just the opposite. H.323 has often been accused of being created…
It's easy to do. Here are some examples: https://www.packetizer.com/ws/webfinger/server.html I actually serve up content using both static files and via dynamically generated content, depending on the domain and needs.
That's not a WebFinger URL. WebFinger URLs point to /.well-known/ path that returns a JSON document with links to other places for the user. To simplify WebFinger use by a human, we introduced acct:user@example.com…
I was the editor of the H.323 spec years ago. Funny you would say that SIP looks like it comes from the telcos, when the whole aim with SIP was to create just the opposite. H.323 has often been accused of being created…