Open miscemw opened 7 months ago
Definitely want to do this. My main blocker is lack of knowledge/literature; I think I need a better mental model of what "publishing" is in this context.
I've spent the past two months trying to gather more information about the right way to handle this. I think I have a good grip on it (though this is a living document!)
username@buttondown.email
, with support for custom domains being a nice-to-have.In sum, this means that ActivityPub users should be able to follow and comment on any Buttondown newsletter (that has opted in), and authors will be able to see their following + engagement within Buttondown proper.
/.well-known/webfinger
outbox
endpointNice, @jmduke! Since we're dealing with a newsletter service, I wonder if ActivityPub allows this scenario:
So, when following a Buttondown newsletter on fediverse, it doubles as a following (to fediverse account) and subscribing (to Buttondown newsletter).
@rghedin Do you know of there being a strict method of going from "actor ID" → "email address"? AFAICT, such a lookup does not exist, though agreed there's a lot of interesting design implications if it does!
I have no idea, @jmduke 😬 Just a thought I had. For a while Twitter offered something like this with its Revue services. It was very easy to sign up to newsletters there. (There are some advantages in a centralized, closed-source model, after all.)
Email addresses are personal data, and are not federated through ActivityPub.
My opinion is that bringing comments from the Fediverse to a newsletter page is a must! To have comments from Mastodon, Threads etc.. but displayed on your own page, that what I see many developers do for their websites. And I understand that custom domains are a hassle, but maybe we could see something like @bd.social
or buttondown.pub
because the "buttondown.email" is not only long, but a bit deceiving!
I would also like to know how the process would work if I wanted to move my Mastodon followers to ButtonDown?
I just stumbled upon this issue (Updates from May > Roadmap > here!). The 1-way "distribution" opportunity (where subscribing via fedi is an alternative to RSS or email) might be a place to start, but the bi-directional possibilities are what really excite me because it invites participation.
Some similar patterns to consider (prompting to auth as necessary?):
If I had more time, I'd add more detail, but hmu if you ever want to talk any of these through.
@earth2marsh apologies for the delayed response — it turns out when you create 500 github issues you get lost in the notifications deluge!
Strongly agreed re: bi-directional being where the real juice is, so to speak. There's some great prior art with Quotebacks along these lines.
I have a bit of experience doing something pretty similar in social.distributed.press, would love to chat about it
Allow cross-posting to ActivityPub-enabled apps like Mastodon, Friendica, and so on.