@mcc I don't think it's super well supported across software, or even internally in software, like mastodon would probably take @example.com and make it @example.com@example.com
So I don't think anyone is currently using it
undefined
Emelia 👸🏻
@thisismissem@hachyderm.io
Post
-
I know for a fact that it is possible to have a mastodon handle like @example.com , no second @, no "username", only the server. -
Here's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxyLike, an interesting thing I learned today is that all requests for custom feeds are actually proxied through your PDS in AT Proto, like there's a full on proxy endpoint implementation.
ActivityPub also has a "proxy endpoint" though much less defined
-
Here's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxyThat "authentication" could just be HTTP Message Signatures, but it could also be much more advanced OAuth bearer tokens using JWTs and stuff
-
Here's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxyAlso, extending this with "how does feed gen get data" could be via FASP protocol
-
Here's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxyOh, wait a minute, I just roughly described how bluesky's feed-gen services work.
-
Here's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxyHere's a thought: custom feeds for ActivityPub would just be collections requested with cursor pagination parameters & authentication via the proxy.
Like, nothing says your collection needs to serve the same content to all requestors, likewise, you don't even need to serve the same content to the same requestor