diff --git a/static/style.css b/static/style.css index f91d5d5..18b8659 100644 --- a/static/style.css +++ b/static/style.css @@ -390,11 +390,6 @@ input[type="submit"] { display: inline-block; } -/* Override the inline display:block which makes it align left instead of center. */ -iframe#twitter-widget-0 { - display: inline !important; -} - #footer { margin-top: 2em; margin-bottom: 1em; @@ -481,6 +476,18 @@ a img.shadow:hover background-color: #f6f6f6; } +.docs .done { + background-color: #ebf6eb; +} + +.docs tr:nth-child(even) .done { + background-color: #e2f6e2; +} + +.docs .not-done { + background-color: white; +} + .question { margin-top: 2em; margin-bottom: .5em; @@ -491,13 +498,6 @@ a img.shadow:hover margin-bottom: .5em; } -/* confirm_instagram.html */ -iframe { - width: 50%; - border: 1px solid gray; - height: 300px; -} - .right { float: right; margin-left: 20px; diff --git a/templates/docs.html b/templates/docs.html index 2dfcb9f..9fc8578 100644 --- a/templates/docs.html +++ b/templates/docs.html @@ -491,7 +491,10 @@ I'm Ryan Barrett. I'm just a guy who likes Here are internal details on how Bridgy Fed translates user identity and events between protocols, including some like Nostr and Bluesky/AT Protocol that aren't launched yet. This includes in progress ideas that may not be implemented yet or fully thought through. Caveat hacker!

-

Here's how we (plan to) translate user identity between protocols. Specifically, each square shows how a user in a given row is identified to the protocol in a given column. BF is Bridgy Fed. Enhanced is users who have done extra setup for BF, basic is users who haven't. +

In the tables below, BF is Bridgy Fed, enhanced is users who have done extra setup for BF, basic is users who haven't. Green parts have been implemented and running here for years, the rest are still in the early design phase. +

+ +

Here's how we (plan to) translate user identity between protocols. Specifically, each square shows how a user in a given row is identified to the protocol in a given column.

@@ -508,8 +511,9 @@ I'm Ryan Barrett. I'm just a guy who likes - - + - - + @@ -573,44 +577,44 @@ I'm Ryan Barrett. I'm just a guy who likes - - + + - - + + - - + + - - + - - + + - - + +
IndieWeb -basic: @[domain]@fed.brid.gy
- enhanced: @[domain]@[domain] + 		+ basic: @[domain]@fed.brid.gy
+ enhanced: @[domain]@[domain] 		users: domain as handle
code: did:plc generated by BF @@ -520,7 +524,7 @@ I'm Ryan Barrett. I'm just a guy who likes
ActivityPubFediverse profile URLFediverse profile URL - users: [username].[instance] (fabricated domain)
code: did:plc generated by BF @@ -564,8 +568,8 @@ I'm Ryan Barrett. I'm just a guy who likes
User discovery inboundserve h-card on BF user pagebasic: serve WebFinger and AP actor on fed.brid.gy
+ 		serve h-card on BF user pagebasic: serve WebFinger and AP actor on fed.brid.gy
enhanced: user's site serves and redirects WebFinger to fed.brid.gy 		resolve DID, serve DID document with fed.brid.gy PDS
User discovery outboundFetch home page, parse h-cardlook up WebFinger, fetch AP actorFetch home page, parse h-cardlook up WebFinger, fetch AP actor resolve DID, subscribe to PDS repo, extract profile object? discover user's relays with NIP-65, query NIP-39 to get profile
Publish inboundwebmention to fed.brid.gydeliver to fed.brid.gy inbox, user or sharedwebmention to fed.brid.gydeliver to fed.brid.gy inbox, user or shared subscribe to user's PDS repo on fed.brid.gy publish event to BF relay
Publish outboundserve on BF user page followings h-feeddeliver to recipient's inboxserve on BF user page followings h-feeddeliver to recipient's inbox serve repo diff via sync XRPCs to subscribing BGSes serve to subscribers
Follow inboundusers: UI on BF user page
+ 		users: UI on BF user page
code: webmention with u-follow-of		Follow activity delivered to BF user inboxFollow activity delivered to BF user inbox receive sync.subscribeRepos? user's client sends REQ to BF relay
Follow outboundwebmention with BF proxy HTML page as sourcedeliver Follow to followee's inboxwebmention with BF proxy HTML page as sourcedeliver Follow to followee's inbox call sync.subscribeRepos on followee's PDS? discover followee's relay(s) with NIP-65, send them a REQ
Response inboundwebmention to a BF proxy pageCreate, Like, Announce delivered to BF user inboxwebmention to a BF proxy pageCreate, Like, Announce delivered to BF user inbox response object received from a subscribed repo?
(what if it's from a user we don't subscribe to?)		 NIP-10 response event received at BF relay or other relay