webdesktops

bmann · bmann · commit 99e7db11aa22 · 2025-03-09T14:00:26.000-07:00
diff --git a/_journals/2025-03-09_1024.md b/_journals/2025-03-09_1024.md
@@ -0,0 +1,12 @@
+---
+title: March 9th, 2025
+date: 2025-03-09, 10:24:33 -07:00
+section: journal
+link: https://cyd.social/
+tags:
+  - Twitter
+  - Bluesky
+---
+I used [[Cyd]] to migrate tweets to Bluesky on my [@bmannconsulting.com](https://bsky.app/profile/bmannconsulting.com) account, self hosted on [[BringYourOwn.Computer]].
+
+Feature request: [support replies using bsky's facets to link to the Twitter original](https://github.com/lockdown-systems/cyd/issues/449).
diff --git a/_journals/2025-03-09_1335.md b/_journals/2025-03-09_1335.md
@@ -0,0 +1,9 @@
+---
+title: March 9th, 2025
+date: 2025-03-09, 13:35:55 -07:00
+section: journal
+link: https://bmannconsulting.com/notes/webdesktop
+tags:
+  - webdesktop
+---
+It was about a year ago that I posted about [[Puter]]. It's a [[web desktop]] and got me thinking about these types of interfaces so I put together a page about them.
diff --git a/_notes/Agreeable.md b/_notes/Agreeable.md
@@ -0,0 +1,107 @@
+---
+github: https://github.com/agree-able
+tags:
+  - agentic
+---
+Building a p2p Agent-to-Agent Communication Protocol, being built by [[Ryan Ramage]].
+
+---
+
+From the README:
+
+Agent indentity verification and signed transcripts, in an easy to use framework.
+
+See the problem space here: [[Great Web Rebuild]]
+
+We build upon the excellent P2P primitives created by the [Holepunch Team](https://github.com/holepunchto/).
+
+# Room Protocol: Simple Guide
+
+## What Is the Room Protocol?
+
+The **Room Protocol** is a free and open system that helps AI agents talk to each other securely and easily. It makes communication fast, safe, and smart.
+
+This system is great for situations where AI agents need to share information or work together on tasks. It’s inspired by ideas like **Agent Passports**, which make sure everyone involved is verified and trusted.
+
+---
+
+## Key Features
+
+### Keeping Conversations Organized
+
+The Room Protocol keeps track of what’s being talked about. This makes it easy to:
+
+- Have smooth back-and-forth conversations.
+- Let agents and people work together better.
+- Pick up right where you left off without forgetting anything.
+
+### Safe and Secure Interactions
+
+Security is super important. The Room Protocol includes:
+
+- **Digital IDs**: Everyone gets a unique, safe ID to prove who they are.
+- **Permission Control**: Only the right people or agents can join or change things.
+- **Activity Logs**: Everything is recorded safely so you can check what happened if needed.
+
+### Works for Big and Small Tasks
+
+The Room Protocol can handle:
+
+- **Teamwork Between Agents**: AI agents can work together or with people on tasks.
+- **Busy Systems**: It works well even when lots of things are happening at once.
+- **Easy Setup**: You can use it with other tools you already have.
+
+### What It’s Not
+
+- The Room Protocol doesn’t tell you how to make your AI agent or what tools to use. That part is up to you.
+
+---
+
+## How It Works
+### The Basics
+
+The Room Protocol uses modern tech to make sure things run smoothly and safely. Here are the main parts:
+
+1. **Rooms**: These are virtual spaces where agents and people talk. Rooms are:
+    
+    - **Smart**: They remember what’s going on.
+    - **Secure**: Only trusted people or agents can join.
+2. **Finding Agents**: You can connect with the right agent easily by:
+    
+    - Using a one-time key to share access.
+    - Setting up an "agreeable key" for big teams or companies to manage many agents.
+3. **Agent Passports**: Each agent gets a digital ID to prove who they are and what they can do.
+    
+4. **Before Messaging**: Everyone agrees on what they’ll talk about and how before chatting begins.
+    
+5. **Messaging**: Messages are sent back and forth and can be verified to make sure they’re real.
+    
+6. **Wrap-Up**: A record of the conversation is saved as proof of what happened.
+    
+
+### Storing Information
+
+The Room Protocol uses special peer-to-peer tech, like [Hypercore](https://docs.pears.com/building-blocks/hypercore), to store data. This system:
+
+- Can save info either in memory or on a disk.
+- Is fast and easy to use.
+- Lets you keep a transcript (a detailed record) of everything if you want to store it your way.
+
+---
+
+## How You Can Use It
+
+### Working Together
+
+Agents in a Room can work on projects like:
+
+- Planning schedules.
+- Sharing resources.
+- Solving problems together.
+
+### Autonomous Agent Teams
+
+AI agents can also work with each other without human input for tasks like:
+
+- Sharing data securely.
+- Negotiating deals.
diff --git a/_notes/BringYourOwn.Computer.md b/_notes/BringYourOwn.Computer.md
@@ -18,7 +18,7 @@ The main thing that this machine does is run a [[PDS]]
 * Nov 15th, 2024: Installed the server on Hostinger
 * Dec 31st, 2024: [[Migrating accounts to my own PDS]] (no actual changes to the server)
 * Jan 1st, 2025: Installed Tailscale as an exit node, setup [[Taildrive]] for file sharing
-* TO DO: [[Twitter Archive to your own Bluesky AT Protocol]]
+* TO DO: [[Twitter Archive to Bluesky AT Protocol Account]]
 
 ### Installing on Hostinger
 
diff --git a/_notes/Cyd.md b/_notes/Cyd.md
@@ -0,0 +1,18 @@
+---
+link: https://cyd.social/
+tags:
+  - app
+  - ATProtocol
+  - opensource
+  - desktop
+github: https://github.com/lockdown-systems/cyd
+ATProtocol: https://bsky.app/profile/cyd.social
+---
+Backup your tweets from your [[Twitter]] account. GPL-licensed, the app itself has [premium plans](https://cyd.social/pricing/) for individuals and teams that is needed for migrating tweets to [[Bluesky]] and other advanced features.
+
+Developed by [[Lockdown Systems]], a worker-owned collective.
+
+> Cyd helps you create a local, private backup of your data — like all of your tweets, retweets, likes, bookmarks, and direct messages. Once you've done this, Cyd helps you choose what data you want to delete from your online account. You can delete it all, or you can be selective, deleting most of it but keeping what went viral.
+
+
+
diff --git a/_notes/Gecko Mozilla Thoughts.md b/_notes/Gecko Mozilla Thoughts.md
@@ -37,8 +37,10 @@ Web engines are like the operating system market share of UNIX, Linux, and the B
 ---
 
 > Right now, and for quite some time I’d wager, <mark>Google alone decides what is de facto on the web by what they ship in Chrome, regardless of what plays out in open source code repos.</mark>
- > 
- > <mark>Second, someone has to fund next generation engines</mark>, in my opinion. They’re long shots, but they’re invaluable in so many ways to show us what’s possible when we don’t have the weight of every single website ever made on our shoulders. I have no idea how to fund them except all the players should just shake hands and put 1% of their fuzzily defined browser budgets into a small pool that hands out grants to crazy people.
+
+---
+
+> <mark>Second, someone has to fund next generation engines</mark>, in my opinion. They’re long shots, but they’re invaluable in so many ways to show us what’s possible when we don’t have the weight of every single website ever made on our shoulders. I have no idea how to fund them except all the players should just shake hands and put 1% of their fuzzily defined browser budgets into a small pool that hands out grants to crazy people.
 
 ---
 
diff --git a/_notes/Great Web Rebuild.md b/_notes/Great Web Rebuild.md
@@ -0,0 +1,13 @@
+---
+link: https://www.aitidbits.ai/p/ai-agents-web-infrastructure
+title: "The Great Web Rebuild: Infrastructure for the AI Agent era"
+tags:
+  - AI
+  - article
+  - agents
+author:
+  - Sahar Mor
+published: 2024-12-12
+---
+> _Welcome to a new post in the AI Agents Series - helping AI developers and researchers deploy and make sense of the next step in AI. Some of my previous posts listed the [open-source toolkit for AI Agents builders](https://www.aitidbits.ai/p/open-source-agents), the [economies of scale for foundational AI models](https://www.aitidbits.ai/p/economies-of-scale-gen-ai), and [the future of autonomous agents](https://www.aitidbits.ai/p/the-rise-of-autonomous-agents)._
+
diff --git a/_notes/Linkblocks.md b/_notes/Linkblocks.md
@@ -0,0 +1,34 @@
+---
+link: 
+tags:
+  - opensource
+  - Rust
+  - app
+  - socialbookmarking
+github: https://github.com/raffomania/linkblocks
+---
+Donation from NGI Zero Commons Fund, part of [[NGI]]
+
+From the README:
+
+---
+
+**📚 A federated network to bookmark, share and discuss good web pages with your friends.**
+
+It's getting harder and harder to find good web pages. When you do find good ones, it's worth hanging onto them. Linkblocks is your own small corner of the web, where you can keep your favorite pages, and share them with your friends to help them find good web pages too.
+
+🔭 Linkblocks is in an exploratory phase where we're trying out different ways to make it work well. You can try it out, but big and small things might change with every update.
+
+## Vision
+
+- On linkblocks, you can organize, connect, browse and search your favorite web pages.
+- Share carefully curated or wildly chaotic collections of the stuff you really really like with other linkblocks users and the whole world wide web.
+- Follow users with a similar taste and get a feed of fresh good web pages every day. Browse others' collections to discover new web pages from topics you like.
+- Annotate, highlight and discuss web pages together with your friends.
+- Mark users as trusted whose standards for web pages match yours - and then search through all trusted bookmarks to find good pages on a specific topic. Add trusted users of your trusted users to your search range to cast a wider net.
+
+[See this blog post for more on the vision behind linkblocks.](https://www.rafa.ee/articles/introducing-linkblocks-federated-bookmark-manager/)
+## Related Reading
+
+- [Where have all the Websites gone?](https://www.fromjason.xyz/p/notebook/where-have-all-the-websites-gone/) talks about the importance of website curation. Linkblocks is for publicly curating websites.
+- [The Small Website Discoverability Crisis](https://www.marginalia.nu/log/19-website-discoverability-crisis/) similar to the previous link, it encourages everyone to share reading lists. By the author of the amazing [marginalia search engine](https://search.marginalia.nu/).
diff --git a/_notes/Lockdown Systems.md b/_notes/Lockdown Systems.md
@@ -0,0 +1,15 @@
+---
+link: https://lockdown.systems/
+tags:
+  - organization
+  - collective
+  - workerowned
+github: https://github.com/lockdown-systems
+---
+Lockdown Systems is a worker-owned collective that builds freedom and privacy technologies that empower people to take control of their own data, choose what they reveal to the world, and protect themselves from unwanted surveillance. Our solutions can be used by individuals as well as organizations, whether non-profit or for-profit, who seek to protect the data of their members. Lockdown Systems balances commercial sustainability with our mission, focusing on long-term impact over short-term financial gain.
+
+## Collective Members
+
+* Saptak S <https://saptaks.blog/>
+* [[Micah Lee]]
+* redshiftzero <https://redshiftzero.com/>
diff --git a/_notes/Micah Lee.md b/_notes/Micah Lee.md
@@ -0,0 +1,15 @@
+---
+link: https://micahflee.com/
+github: https://github.com/micahflee
+tags:
+  - person
+  - ATProtocol
+  - privacy
+  - developer
+  - journalist
+---
+I'm a coder, a journalist, and I help people stay private and secure.
+
+I develop open source security tools like [OnionShare](https://onionshare.org/) and [Dangerzone](https://dangerzone.rocks/).
+
+Part of [[Lockdown Systems]], creator of [[Cyd]]
diff --git a/_notes/PDS Twitter Archive.md b/_notes/PDS Twitter Archive.md
diff --git a/_notes/Personal Notes & Publishing Stack.md b/_notes/Personal Notes & Publishing Stack.md
@@ -0,0 +1,49 @@
+---
+tags:
+  - WIP
+---
+The base line tool that I am looking for to anchor [[Community Search Engine]] is a multi-player personal notes & publishing stack.
+
+You should feel comfortable putting meeting notes, quick scratch notes, pages on their way to be published, links and a few comments, research from multiple web pages, and other material in here. It is your companion for research, progress, and evolution.
+
+It wants to displace Apple Notes and Google Docs, and be a place where you stage short and long form social media.
+
+It wants to be the digital place where your family group, project team, or entire small business go to find, document, and extend a growing model of useful information.
+
+It's where you store the results from searching, browsing, or collaborative agent-based research sessions.
+## Notes
+
+Notes should have the following features:
+* a title
+* a unique identifier that is separate from the title (e.g. changing the title doesn't break links)
+* wikilinks or @-mention or similar affordance to easily link to existing or stub new notes
+* backlinks, where linking to a note also showcases a "backlink" when viewing the note. This creates a graph of linked notes
+
+There are some other features like tags, aliases or transclusion that needs some more thinking.
+
+## Journal
+
+Increasingly, the concept of author / creating / updating over time is an extremely useful anchor.
+
+Opening notes and having date / time stamps as a default entry is good. Simple mode is one "day" note per day. A more excellent mode that also fits with shorter content publishing and sharing is block-based unique notes.
+
+Visually, collecting notes into day / week / month chunks is one way to display aka a "log" or "work log". So a day becomes a view, but can contain multiple 
+
+## Files
+
+Export and import of Markdown notes should be supported, but strict representation of one note == one file at all times is not necessary.
+## Multi Player Notes
+
+Multi-player does not necessarily mean real time collaborative editing. It starts with a single person having multiple devices where things are kept in sync, and goes from there to groups of people.
+
+The hardest part of multi player notes is permission management. "Open" collaborative notes like [[HedgeDoc]] are easy, but can suffer from spam. Security through security by sharing links to hashes can work pretty well.
+
+The "folder" model seems conceptually simplest. Make a folder, add access at that level, and then everything inside inherits that. 
+
+Sharing the same info with multiple different groups outside of a strict hierarchy is a challenge. This might mean using something like tagging to grant access. This is both a UX (what do you do in practice to share) and UI issue (how do you display shared docs or approximate GDocs permission listing).
+
+Google Drive has ended up with this concept of "aliases", in order to have a document in multiple folders. Google Drive also complicates the folder model by allowing for different permissions inside a single folder. This means that everyone has a different view. Related: having variable "views" might be needed along with "baked" views where everyone has the same picture. Views might in fact be something that you collect or curate and then publish to a group.
+
+## Agentic Goal Workspaces
+
+How does one collect multiple people and agents into [[Goal Workspaces]]? A shared space with some goal, where different views, visualizations, interfaces, and data sources can be pooled to meet that goal.
diff --git a/_notes/Puter.md b/_notes/Puter.md
@@ -5,6 +5,7 @@ tags:
   - opensource
   - AGPL
   - SPA
+  - webdesktop
 github: https://github.com/HeyPuter/puter
 ---
 > Internet OS and Desktop Environment in the Browser!
diff --git a/_notes/Running community meetups in 2025.md b/_notes/Running community meetups in 2025.md
@@ -1,11 +1,29 @@
 ---
 tags:
   - WIP
+  - community
 ---
 I had a great call with [[Ankesh Bharti]]. He's based in Bangalore now, and we had two things to discuss. One, is his interest in potentially organizing a [[Causal Islands Bangalore]] event this fall. And two, his new [[User & Agents]] community.
 
-This made me reflect on community meetups. I've been booting up [[DWebYVR]] for the past two years, and generally like to 
+This made me reflect on community meetups. I've been booting up [[DWebYVR]] for the past two years, and generally like to figure out cadence.
 
+## Days, Evenings, and Weekends
+
+For events, if you make them during the day, then only people who have the topic as their "day job" can go, or don't work / are students are likely to come.
+
+Weekday evenings is good for both people with day jobs that are aligned as well as enthusiasts. Note that Friday evenings are typically bad for older people with families.
+
+Weekends you will get more enthusiasts, and less family / day job professionals.
 ## Weekly Cadence
 
-## Monthly Cadence
+A weekly cadence is a lot. It needs to be low effort and basically drop in. A good fit for things like co-working.
+
+If you put it at the same time every week -- both time of day and day of week -- then there will be some people who can never come. Consider rotating a bit, especially when you're experiment.
+
+You may want multiple hosts, or a host per time slot, eg. Alice every Thursday evening, and Bob ever Tuesday morning.
+## Monthly Cadence
+
+You need to be "on" for 2 weeks every month, and it can be a lot if you need a unique speaker, different venues, etc. Planning in quarterly chunks can help, where you figure out venue, hosts, speakers in one chunk, and then just need to push out marketing / registration attendance closer to each one.
+## Quarterly
+
+Appropriate for bigger events where you want to have higher attendance, polished talks, and similar styles. You get 4-6 weeks "off" between events, and then push for 4-6 weeks to fill the event.
diff --git a/_notes/Ryan Ramage.md b/_notes/Ryan Ramage.md
@@ -0,0 +1,12 @@
+---
+ATProtocol: https://bsky.app/profile/ramage.in
+github: https://github.com/ryanramage
+tags:
+  - person
+  - developer
+  - Canada
+  - Edmonton
+  - agentic
+link: https://ra.mage.rocks/
+---
+Building [[Agreeable]]
diff --git a/_notes/Twitter Archive to Bluesky AT Protocol Account.md b/_notes/Twitter Archive to Bluesky AT Protocol Account.md
diff --git a/_notes/Twitter Archive to your own Bluesky AT Protocol.md b/_notes/Twitter Archive to your own Bluesky AT Protocol.md
diff --git a/_notes/web desktop.md b/_notes/web desktop.md
