@benpate@mastodon.social avatar benpate , to random

I've been thinking a lot about and how to make it easy for people to find and join the

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?

image/jpeg
image/jpeg

benpate OP ,
@benpate@mastodon.social avatar

Hey gang.. Do you think this is the right way to guide people from personal/organizational websites into the ?

Some of this is defined in . Some of it exists today in (and the "remote follow") some is being built by @dansup as , and some is just scribbles on paper.

If there's interest, I'm happy to write up the rest of this as an additional

@silverpill
@rimu
@evan
@trwnh
@julian
@ricferrer

@ricferrer@mastodon.social avatar ricferrer , to random

It’s really surprising to me that the hasn’t agreed on a standardized way to open cross-instance objects and instead relies on links that open in the browser.

I found this proposal and what’s thinking… https://codeberg.org/fediverse/fep/src/branch/main/fep/07d7/fep-07d7.md Which one would be your favorite?

(If anyone has updates on the progress, feel free to point me in the right direction)

benpate ,
@benpate@mastodon.social avatar

I understand the need to link back to an app. It’s important, but I’m voting for the open web.

All the search and discovery interactions should start out on a website somewhere, then link back to your home website (or possibly an app) to share and like.

But, using a new URL scheme will lock out everyone who doesn’t have an app installed, and that’s a bad UX.

Plus, I think we can solve this “back to my server” issue in other ways WITHOUT needing a URL scheme, like:

@ricferrer

strypey ,
@strypey@mastodon.nzoss.nz avatar

@benpate
> I think we can solve this “back to my server” issue in other ways WITHOUT needing a URL scheme, like:

The finer details of this are beyond me for now, but I know that @moshidon often seems to know that a URL leads to AP object, and opens it in-app instead of passing it to a web browser. Can you link us to any resources you used to make that magic happen Lucas?

@ricferrer