B
@maddyunderstars Looks cool! I'm starring and following your work.
It looks like you're using Typescript. All of my E2EE work is in Typescript, so there's a good chance you could use the library I'm making when you want to do encrypted groups.
Let me know when I can help 
Hey, this is pretty interesting. Thanks for sharing!
That would be really cool if they can support Bluesky and ActivityPub at the same time.
The article on the website makes it seem like you’re only signing in with your ActivityPub identity though?
Otherwise, “Fediverse” client support is limited to the Mastodon API, or oft-unimplememted C2S API.
I’ll definitely keep my eyes on this one!
There's a lot of energy on the #Fediverse right now to discuss/find a #Federated alternative to #Discord using #ActivityPub.
@strypey suggested that I put this out there to anyone who's thinking about it. We could probably rebuild most of Discord's features as an #Emissary inbox without doing a lot of back end code.
I'm too swamped to start on this right now. But if you're a great HTML+CSS designer, I'm able to give some time to a team who wants to take this on.
@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.
Yes. Great point. At best, automatic recommendations would need some heavy moderation.
Also, each segment of this process should be its own swappable API, so sites can mix and match the solution that fits them.
The initiating website should choose what it recommends - including just using a static list of one or more servers to point to. That config could live in the HTML widget(s) we build.
I'll be interested to see where this goes. I looked into implementing the Micropub API (https://indieweb.org/Micropub) at one point. There's lots of client apps that already use it, which is a plus.
This is probably different from what you're describing, but it might be an interesting comparison.
@julian Great points. It could be done in swappable stages, with each step being an open API.
The widget itself could probably be done in pure, self-hosted javascript.
Location lookups are more ambitions, and would need server support. We could probably make self-hosted / shared server for this. Just a few providers would be enough.
FediDB (or some compatible API) provides the list of available servers, possibly vetted by the work being done by @MastodonEngineering for their signup button.
@trwnh Another admirable goal, to be sure! Traffic in both directions is a win.
Are there specific things we can build that will facilitate this?
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
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?
