Merge branch 'archivetrim' of https://github.com/bmann/bmcgarden.git

_includes/head.html

···
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <meta name="description" content="{% if page.excerpt %}{{ page.excerpt | strip_html | strip_newlines | truncate: 160 }}{% else %}{{ site.title }}{% endif %}">
   <meta property="og:site_name" content="{{ site.title }}">
-  <link rel="icon" type="image/png" href="data:image/png;base64,iVBORw0KGgo=">
   <link rel="stylesheet" href="{{ '/styles.css' | relative_url }}">
   <link rel="alternate" type="application/atom+xml" title="Blog Feed for bmannconsulting.com" href="{{ site.url }}/blog.xml" />
   <link rel="alternate" type="application/atom+xml" title="Journal Feed for bmannconsulting.com" href="{{ site.url }}/journal.xml" />
···
 
   {% if page.image %}
   <meta property="og:image" content="{{ site.url }}{{ page.image }}">
+  <meta property="fc:frame:image" content="{{ site.url }}{{ page.image }}">
+  <meta property="fc:frame:image:aspect_ratio" content="1:1">
+  {% else %}
+  <meta property="og:image" content="{{ site.url }}/assets/bmann_hair_orange_256x256.png">
+  <meta property="fc:frame:image" content="{{ site.url }}/assets/bmann_hair_orange_256x256.png">
+  <meta property="fc:frame:image:aspect_ratio" content="1:1">
   {% endif %}
+
+  <!-- Open Frames -->
+  <meta property="fc:frame" content="vNext">
+  <meta property="fc:frame:button:1" content="🌱 Home">
+  <meta property="fc:frame:button:1:action" content="link">
+  <meta property="fc:frame:button:1:target" content="https://bmannconsulting.com">
+  <meta property="fc:frame:button:2" content="🦋 Bluesky">
+  <meta property="fc:frame:button:2:action" content="link">
+  <meta property="fc:frame:button:2:target" content="https://bsky.bmann.ca">
+  <meta property="fc:frame:button:3" content="💬 Drips">
+  <meta property="fc:frame:button:3:action" content="link">
+  <meta property="fc:frame:button:3:target" content="https://www.drips.network/app/bmann.eth">
   
   <title>
     {% if page.id == "home" %}

_journals/2024-04-16_1549.md

···
+---
+title: April 16th, 2024
+date: 2024-04-16, 15:49:17 -07:00
+section: journal
+link: https://bmannconsulting.com/notes/feedback-on-federating-ghost/
+tags:
+  - ActivityPub
+  - Ghost
+---
+I wrote up my notes on what I submitted to the Ghost survey: [[Feedback on Federating Ghost]]. I truly believe that any app that cares about user interaction should look to federate beyond a single install.

_notes/2024 Events.md

···
+---
+---
+
 
 ## December
 

_notes/Community Search Engines.md

···
+---
+---
+
 Community Search Engines is the label for a set of approaches to interconnect communities. 
 
 These communities are formed by:

_notes/Feedback on Federating Ghost.md

···
 
 ## With as much detail as you can give, how would you expect ActivityPub functionality to work in Ghost, if it existed?
 
-Signing up for a Ghost account as a user could also be done by “Logging in with ActivityPub”. 
+Signing up for a Ghost site account as a user could also be done by “Logging in with ActivityPub”. 
 
-So, someone with an existing AP account could login with that account. 
+So, someone with an existing AP account could login with that account. This would create a local account, where you "auth" with your remote account.
 
-They would still provide their email address, but could 
+Alternately, existing member accounts can "link to an AP account". This leaves things open for connecting to multiple servers and networks.
 
-Once someone signed up, they could 
+### Following Ghost Content
+
+From a user perspective, there should be a "main" Ghost account to follow, `@[e-mail]`. The publisher should be able to choose tags to expose like `@[e-mail]`.
+
+Replying to a posted article would appear as a comment on the article. If someone doesn't have a linked Ghost account, the publisher could choose whether or not to show it.
+
+Optional: if a person without a linked Ghost account replies with their AP account, send a DM that says "thanks for your comment! if you link your AP account, we'll publish your reply as a comment". There are a bunch of paths here for onboarding as well as moderation.
+
+Favorites and Boosts could also flow back, a bit like Web Mentions. This would be stored in the Ghost database, and could be used to sort or otherwise display content.
+### Premium Content
+
+Could we get DMs / private mentions of full articles for premium content?
+
+### Threadiverse
+
+The [[Threadiverse]] is the name for Reddit-style top posts plus comments. This seems to fit the article-or-newsletter-plus-comments that Ghost specializes in. Following this pattern would be better than thinking of Ghost as microblogging.
 
 ## If Ghost had this, what would be the biggest benefit to you, personally?
 
+I would interact with more Ghost sites in the "comments" if I didn't have to create new accounts all the time!
+
+I already recommend [[Ghost]] and could now consider using it for use cases that look more like community servers use cases.
+
+

_notes/Note Clips.md

···
+---
+---
+
 Notes on making a cross-tool drag and drop capability. 
 
 What if you could open your [[Digital Garden]] / Second Brain / Spatial Canvas / Notes website in a browser, and open any other web page, and drag and drop content into your own site?

_notes/Vancouver Hack Day.md

···
+---
+---
+
 I’m organizing a couple hack days in Vancouver as part of the [[DWebYVR]] group. 
 ## What’s a hack day?