I've been thinking a lot about #ActivityIntents and how to make it easy for people to find and join the #SocialWeb
Here's some ultra-low-effort drawings of the process I'm imagining. (criticism and refinements welcome)
1. embeddable widgets (follow, like, share, etc) for any site
2. pre-populate search fields to recommend a single server (with overrides)
3. pass extra data to that server on signup so the intent is honored
4. recommend additional accounts based on context
Yes?
Hey #FediDev gang.. Do you think this is the right way to guide people from personal/organizational websites into the #Fediverse?
Some of this is defined in #FEP3b86. Some of it exists today in #Emissary (and the #oStatus "remote follow") some is being built by @dansup as #WebIntents, and some is just scribbles on paper.
If there's interest, I'm happy to write up the rest of this as an additional #FEP
@[email protected] depends... who's hosting the web intent button code and handling all of the behind the scenes tasks?
What are the buy-in requirements for each implementor, 3b86?
I see value in it, but I am not entirely sure if the flow is expected. I haven't clicked a "share to facebook" (or similar) button in years, if ever, but I am not the target user.
@julian Sorry, I didn't answer one of your questions
3b86 is very helpful, esp. for less common activities such as "Like" - so it would be great to get that metadata into WebFinger at a minimum.
But for simple "Follow" activities, we can also guess common endpoints by sniffing your server type. It's messy, but it'll work until we have better adoption.
That's what I'm doing server-side in #Emissary, and I believe @dansup is planning something similar for #WebIntents.
Ben Pate 🤘🏻
julian