commit 99e7db11aa222ef48d34b24bb6f6cdc23277a2b0 · bmann.ca/bmannconsulting.com

+12

_journals/2025-03-09_1024.md

···

       1
       +
       ---

     

       2
       +
       title: March 9th, 2025

     

       3
       +
       date: 2025-03-09, 10:24:33 -07:00

     

       4
       +
       section: journal

     

       5
       +
       link: https://cyd.social/

     

       6
       +
       tags:

     

       7
       +
         - Twitter

     

       8
       +
         - Bluesky

     

       9
       +
       ---

     

       10
       +
       I used [[Cyd]] to migrate tweets to Bluesky on my [@bmannconsulting.com](https://bsky.app/profile/bmannconsulting.com) account, self hosted on [[BringYourOwn.Computer]].

     

       11
       +
       

     

       12
       +
       Feature request: [support replies using bsky's facets to link to the Twitter original](https://github.com/lockdown-systems/cyd/issues/449).

+9

_journals/2025-03-09_1335.md

···

       1
       +
       ---

     

       2
       +
       title: March 9th, 2025

     

       3
       +
       date: 2025-03-09, 13:35:55 -07:00

     

       4
       +
       section: journal

     

       5
       +
       link: https://bmannconsulting.com/notes/webdesktop

     

       6
       +
       tags:

     

       7
       +
         - webdesktop

     

       8
       +
       ---

     

       9
       +
       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.

+107

_notes/Agreeable.md

···

       1
       +
       ---

     

       2
       +
       github: https://github.com/agree-able

     

       3
       +
       tags:

     

       4
       +
         - agentic

     

       5
       +
       ---

     

       6
       +
       Building a p2p Agent-to-Agent Communication Protocol, being built by [[Ryan Ramage]].

     

       7
       +
       

     

       8
       +
       ---

     

       9
       +
       

     

       10
       +
       From the README:

     

       11
       +
       

     

       12
       +
       Agent indentity verification and signed transcripts, in an easy to use framework.

     

       13
       +
       

     

       14
       +
       See the problem space here: [[Great Web Rebuild]]

     

       15
       +
       

     

       16
       +
       We build upon the excellent P2P primitives created by the [Holepunch Team](https://github.com/holepunchto/).

     

       17
       +
       

     

       18
       +
       # Room Protocol: Simple Guide

     

       19
       +
       

     

       20
       +
       ## What Is the Room Protocol?

     

       21
       +
       

     

       22
       +
       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.

     

       23
       +
       

     

       24
       +
       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.

     

       25
       +
       

     

       26
       +
       ---

     

       27
       +
       

     

       28
       +
       ## Key Features

     

       29
       +
       

     

       30
       +
       ### Keeping Conversations Organized

     

       31
       +
       

     

       32
       +
       The Room Protocol keeps track of what’s being talked about. This makes it easy to:

     

       33
       +
       

     

       34
       +
       - Have smooth back-and-forth conversations.

     

       35
       +
       - Let agents and people work together better.

     

       36
       +
       - Pick up right where you left off without forgetting anything.

     

       37
       +
       

     

       38
       +
       ### Safe and Secure Interactions

     

       39
       +
       

     

       40
       +
       Security is super important. The Room Protocol includes:

     

       41
       +
       

     

       42
       +
       - **Digital IDs**: Everyone gets a unique, safe ID to prove who they are.

     

       43
       +
       - **Permission Control**: Only the right people or agents can join or change things.

     

       44
       +
       - **Activity Logs**: Everything is recorded safely so you can check what happened if needed.

     

       45
       +
       

     

       46
       +
       ### Works for Big and Small Tasks

     

       47
       +
       

     

       48
       +
       The Room Protocol can handle:

     

       49
       +
       

     

       50
       +
       - **Teamwork Between Agents**: AI agents can work together or with people on tasks.

     

       51
       +
       - **Busy Systems**: It works well even when lots of things are happening at once.

     

       52
       +
       - **Easy Setup**: You can use it with other tools you already have.

     

       53
       +
       

     

       54
       +
       ### What It’s Not

     

       55
       +
       

     

       56
       +
       - The Room Protocol doesn’t tell you how to make your AI agent or what tools to use. That part is up to you.

     

       57
       +
       

     

       58
       +
       ---

     

       59
       +
       

     

       60
       +
       ## How It Works

     

       61
       +
       ### The Basics

     

       62
       +
       

     

       63
       +
       The Room Protocol uses modern tech to make sure things run smoothly and safely. Here are the main parts:

     

       64
       +
       

     

       65
       +
       1. **Rooms**: These are virtual spaces where agents and people talk. Rooms are:

     

       66
       +
           

     

       67
       +
           - **Smart**: They remember what’s going on.

     

       68
       +
           - **Secure**: Only trusted people or agents can join.

     

       69
       +
       2. **Finding Agents**: You can connect with the right agent easily by:

     

       70
       +
           

     

       71
       +
           - Using a one-time key to share access.

     

       72
       +
           - Setting up an "agreeable key" for big teams or companies to manage many agents.

     

       73
       +
       3. **Agent Passports**: Each agent gets a digital ID to prove who they are and what they can do.

     

       74
       +
           

     

       75
       +
       4. **Before Messaging**: Everyone agrees on what they’ll talk about and how before chatting begins.

     

       76
       +
           

     

       77
       +
       5. **Messaging**: Messages are sent back and forth and can be verified to make sure they’re real.

     

       78
       +
           

     

       79
       +
       6. **Wrap-Up**: A record of the conversation is saved as proof of what happened.

     

       80
       +
           

     

       81
       +
       

     

       82
       +
       ### Storing Information

     

       83
       +
       

     

       84
       +
       The Room Protocol uses special peer-to-peer tech, like [Hypercore](https://docs.pears.com/building-blocks/hypercore), to store data. This system:

     

       85
       +
       

     

       86
       +
       - Can save info either in memory or on a disk.

     

       87
       +
       - Is fast and easy to use.

     

       88
       +
       - Lets you keep a transcript (a detailed record) of everything if you want to store it your way.

     

       89
       +
       

     

       90
       +
       ---

     

       91
       +
       

     

       92
       +
       ## How You Can Use It

     

       93
       +
       

     

       94
       +
       ### Working Together

     

       95
       +
       

     

       96
       +
       Agents in a Room can work on projects like:

     

       97
       +
       

     

       98
       +
       - Planning schedules.

     

       99
       +
       - Sharing resources.

     

       100
       +
       - Solving problems together.

     

       101
       +
       

     

       102
       +
       ### Autonomous Agent Teams

     

       103
       +
       

     

       104
       +
       AI agents can also work with each other without human input for tasks like:

     

       105
       +
       

     

       106
       +
       - Sharing data securely.

     

       107
       +
       - Negotiating deals.

+1 -1

_notes/BringYourOwn.Computer.md

···

       18
        
       * Nov 15th, 2024: Installed the server on Hostinger

     

       19
        
       * Dec 31st, 2024: [[Migrating accounts to my own PDS]] (no actual changes to the server)

     

       20
        
       * Jan 1st, 2025: Installed Tailscale as an exit node, setup [[Taildrive]] for file sharing

     

       21
       -
       * TO DO: [[Twitter Archive to your own Bluesky AT Protocol]]

     

       22
        
       

     

       23
        
       ### Installing on Hostinger

     

       24

···

       18
        
       * Nov 15th, 2024: Installed the server on Hostinger

     

       19
        
       * Dec 31st, 2024: [[Migrating accounts to my own PDS]] (no actual changes to the server)

     

       20
        
       * Jan 1st, 2025: Installed Tailscale as an exit node, setup [[Taildrive]] for file sharing

     

       21
       +
       * TO DO: [[Twitter Archive to Bluesky AT Protocol Account]]

     

       22
        
       

     

       23
        
       ### Installing on Hostinger

     

       24

+18

_notes/Cyd.md

···

       1
       +
       ---

     

       2
       +
       link: https://cyd.social/

     

       3
       +
       tags:

     

       4
       +
         - app

     

       5
       +
         - ATProtocol

     

       6
       +
         - opensource

     

       7
       +
         - desktop

     

       8
       +
       github: https://github.com/lockdown-systems/cyd

     

       9
       +
       ATProtocol: https://bsky.app/profile/cyd.social

     

       10
       +
       ---

     

       11
       +
       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.

     

       12
       +
       

     

       13
       +
       Developed by [[Lockdown Systems]], a worker-owned collective.

     

       14
       +
       

     

       15
       +
       > 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.

     

       16
       +
       

     

       17
       +
       

     

       18
       +

+4 -2

_notes/Gecko Mozilla Thoughts.md

···

       37
        
       ---

     

       38
        
       

     

       39
        
       > 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>

     

       40
       -
        > 

     

       41
       -
        > <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.

     

       0
        
       
     

       0
        
       
     

       42
        
       

     

       43
        
       ---

     

       44

···

       37
        
       ---

     

       38
        
       

     

       39
        
       > 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>

     

       40
       +
       

     

       41
       +
       ---

     

       42
       +
       

     

       43
       +
       > <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.

     

       44
        
       

     

       45
        
       ---

     

       46

+13

_notes/Great Web Rebuild.md

···

       1
       +
       ---

     

       2
       +
       link: https://www.aitidbits.ai/p/ai-agents-web-infrastructure

     

       3
       +
       title: "The Great Web Rebuild: Infrastructure for the AI Agent era"

     

       4
       +
       tags:

     

       5
       +
         - AI

     

       6
       +
         - article

     

       7
       +
         - agents

     

       8
       +
       author:

     

       9
       +
         - Sahar Mor

     

       10
       +
       published: 2024-12-12

     

       11
       +
       ---

     

       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)._

     

       13
       +

+34

_notes/Linkblocks.md

···

       1
       +
       ---

     

       2
       +
       link: 

     

       3
       +
       tags:

     

       4
       +
         - opensource

     

       5
       +
         - Rust

     

       6
       +
         - app

     

       7
       +
         - socialbookmarking

     

       8
       +
       github: https://github.com/raffomania/linkblocks

     

       9
       +
       ---

     

       10
       +
       Donation from NGI Zero Commons Fund, part of [[NGI]]

     

       11
       +
       

     

       12
       +
       From the README:

     

       13
       +
       

     

       14
       +
       ---

     

       15
       +
       

     

       16
       +
       **📚 A federated network to bookmark, share and discuss good web pages with your friends.**

     

       17
       +
       

     

       18
       +
       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.

     

       19
       +
       

     

       20
       +
       🔭 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.

     

       21
       +
       

     

       22
       +
       ## Vision

     

       23
       +
       

     

       24
       +
       - On linkblocks, you can organize, connect, browse and search your favorite web pages.

     

       25
       +
       - Share carefully curated or wildly chaotic collections of the stuff you really really like with other linkblocks users and the whole world wide web.

     

       26
       +
       - 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.

     

       27
       +
       - Annotate, highlight and discuss web pages together with your friends.

     

       28
       +
       - 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.

     

       29
       +
       

     

       30
       +
       [See this blog post for more on the vision behind linkblocks.](https://www.rafa.ee/articles/introducing-linkblocks-federated-bookmark-manager/)

     

       31
       +
       ## Related Reading

     

       32
       +
       

     

       33
       +
       - [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.

     

       34
       +
       - [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/).

+15

_notes/Lockdown Systems.md

···

       1
       +
       ---

     

       2
       +
       link: https://lockdown.systems/

     

       3
       +
       tags:

     

       4
       +
         - organization

     

       5
       +
         - collective

     

       6
       +
         - workerowned

     

       7
       +
       github: https://github.com/lockdown-systems

     

       8
       +
       ---

     

       9
       +
       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.

     

       10
       +
       

     

       11
       +
       ## Collective Members

     

       12
       +
       

     

       13
       +
       * Saptak S <https://saptaks.blog/>

     

       14
       +
       * [[Micah Lee]]

     

       15
       +
       * redshiftzero <https://redshiftzero.com/>

+15

_notes/Micah Lee.md

···

       1
       +
       ---

     

       2
       +
       link: https://micahflee.com/

     

       3
       +
       github: https://github.com/micahflee

     

       4
       +
       tags:

     

       5
       +
         - person

     

       6
       +
         - ATProtocol

     

       7
       +
         - privacy

     

       8
       +
         - developer

     

       9
       +
         - journalist

     

       10
       +
       ---

     

       11
       +
       I'm a coder, a journalist, and I help people stay private and secure.

     

       12
       +
       

     

       13
       +
       I develop open source security tools like [OnionShare](https://onionshare.org/) and [Dangerzone](https://dangerzone.rocks/).

     

       14
       +
       

     

       15
       +
       Part of [[Lockdown Systems]], creator of [[Cyd]]

-8

_notes/PDS Twitter Archive.md

···

       1
       -
       ---

     

       2
       -
       link: https://polar.sh/ATProtoApps/pdstwitterarchive

     

       3
       -
       tags:

     

       4
       -
         - pds

     

       5
       -
         - ATProtocol

     

       6
       -
         - Twitter

     

       7
       -
       ---

     

       8
       -
       Code to

+49

_notes/Personal Notes & Publishing Stack.md

···

1
+
---

2
+
tags:

3
+
- WIP

4
+
---

5
+
The base line tool that I am looking for to anchor [[Community Search Engine]] is a multi-player personal notes & publishing stack.

6
+

7
+
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.

8
+

9
+
It wants to displace Apple Notes and Google Docs, and be a place where you stage short and long form social media.

10
+

11
+
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.

12
+

13
+
It's where you store the results from searching, browsing, or collaborative agent-based research sessions.

14
+
## Notes

15
+

16
+
Notes should have the following features:

17
+
* a title

18
+
* a unique identifier that is separate from the title (e.g. changing the title doesn't break links)

19
+
* wikilinks or @-mention or similar affordance to easily link to existing or stub new notes

20
+
* backlinks, where linking to a note also showcases a "backlink" when viewing the note. This creates a graph of linked notes

21
+

22
+
There are some other features like tags, aliases or transclusion that needs some more thinking.

23
+

24
+
## Journal

25
+

26
+
Increasingly, the concept of author / creating / updating over time is an extremely useful anchor.

27
+

28
+
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.

29
+

30
+
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

31
+

32
+
## Files

33
+

34
+
Export and import of Markdown notes should be supported, but strict representation of one note == one file at all times is not necessary.

35
+
## Multi Player Notes

36
+

37
+
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.

38
+

39
+
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.

40
+

41
+
The "folder" model seems conceptually simplest. Make a folder, add access at that level, and then everything inside inherits that.

42
+

43
+
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).

44
+

45
+
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.

46
+

47
+
## Agentic Goal Workspaces

48
+

49
+
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.

+1

_notes/Puter.md

···

       5
        
         - opensource

     

       6
        
         - AGPL

     

       7
        
         - SPA

     

       0
        
       
     

       8
        
       github: https://github.com/HeyPuter/puter

     

       9
        
       ---

     

       10
        
       > Internet OS and Desktop Environment in the Browser!

···

       5
        
         - opensource

     

       6
        
         - AGPL

     

       7
        
         - SPA

     

       8
       +
         - webdesktop

     

       9
        
       github: https://github.com/HeyPuter/puter

     

       10
        
       ---

     

       11
        
       > Internet OS and Desktop Environment in the Browser!

+20 -2

_notes/Running community meetups in 2025.md

···

       1
        
       ---

     

       2
        
       tags:

     

       3
        
         - WIP

     

       0
        
       
     

       4
        
       ---

     

       5
        
       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.

     

       6
        
       

     

       7
       -
       This made me reflect on community meetups. I've been booting up [[DWebYVR]] for the past two years, and generally like to 

     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       8
        
       

     

       0
        
       
     

       9
        
       ## Weekly Cadence

     

       10
        
       

     

       11
       -
       ## Monthly Cadence
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0
        
       
     

       0

···

1

---

2

tags:

3

- WIP

4
+
- community

5

---

6

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.

7

8
+
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.

9
+

10
+
## Days, Evenings, and Weekends

11
+

12
+
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.

13
+

14
+
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.

15

16
+
Weekends you will get more enthusiasts, and less family / day job professionals.

17

## Weekly Cadence

18

19
+
A weekly cadence is a lot. It needs to be low effort and basically drop in. A good fit for things like co-working.

20
+

21
+
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.

22
+

23
+
You may want multiple hosts, or a host per time slot, eg. Alice every Thursday evening, and Bob ever Tuesday morning.

24
+
## Monthly Cadence

25
+

26
+
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.

27
+
## Quarterly

28
+

29
+
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.

+12

_notes/Ryan Ramage.md

···

       1
       +
       ---

     

       2
       +
       ATProtocol: https://bsky.app/profile/ramage.in

     

       3
       +
       github: https://github.com/ryanramage

     

       4
       +
       tags:

     

       5
       +
         - person

     

       6
       +
         - developer

     

       7
       +
         - Canada

     

       8
       +
         - Edmonton

     

       9
       +
         - agentic

     

       10
       +
       link: https://ra.mage.rocks/

     

       11
       +
       ---

     

       12
       +
       Building [[Agreeable]]

+53

_notes/Twitter Archive to Bluesky AT Protocol Account.md

···

       1
       +
       ---

     

       2
       +
       tags:

     

       3
       +
         - Twitter

     

       4
       +
         - Bluesky

     

       5
       +
         - ATProtocol

     

       6
       +
         - archive

     

       7
       +
       ---

     

       8
       +
       Turns out I didn't have a copy of my Twitter archive available any more, so I requested it again, and now have it backed up elsewhere as of February 2025.

     

       9
       +
       

     

       10
       +
       I tried using the [twitter-to-bluesky](https://github.com/marcomaroni-github/twitter-to-bluesky) script but kept running into errors.

     

       11
       +
       

     

       12
       +
       I ended up using [[Cyd]] with the local Twitter archive I had to migrate to my [@bmannconsulting.com](https://bsky.app/profile/bmannconsulting.com) account. This is on my self-hosted [[BringYourOwn.Computer]] PDS.

     

       13
       +
       

     

       14
       +
       I have deleted tweets older than 180 days.

     

       15
       +
       

     

       16
       +
       I am still cross-posting to Twitter from my [journal](/journal/) using [[Fedica]].

     

       17
       +
       

     

       18
       +
       ## Cyd

     

       19
       +
       

     

       20
       +
       Cyd doesn't support replies. I would actually like to have my replies! This has been [filed as an issue in the cyd github repo](https://github.com/lockdown-systems/cyd/issues/449).

     

       21
       +
       

     

       22
       +
       A few other feature requests:

     

       23
       +
       

     

       24
       +
       Use Bluesky's rich text to link @-mentions

     

       25
       +
       * @oldtwitterhandle would look like this `[@oldtwitterhandle](https://x.com/oldtwitterhandle)` (obviously not Markdown, but shown that way to show the link)

     

       26
       +
       * Could also use [[Tweetback]]'s canonical JSON to parse where to point this

     

       27
       +
       * As people migrate to Bluesky in particular, keep track of where people are heading. So, `@bmann` has archived to Bluesky as `@bmannconsulting.com`

     

       28
       +
       

     

       29
       +
       Support reply imports

     

       30
       +
       * just like linking @-mentions, deeplink into reply parents

     

       31
       +
       * So, if my post is @-someaccount, that @-mention is linked to the tweet I'm replying to

     

       32
       +
       

     

       33
       +
       ## PDS Archive

     

       34
       +
       

     

       35
       +
       I wrote this up [as a GH Discussion](https://github.com/orgs/ATProtoApps/discussions/6).

     

       36
       +
       

     

       37
       +
       The premium version of a Twitter archiver would be:

     

       38
       +
       

     

       39
       +
       - a PDS, with a custom domain name

     

       40
       +
       - everyone gets a user name with their original Twitter handle

     

       41
       +
       - upload your Twitter archive to import, including all media

     

       42
       +
       

     

       43
       +
       Possible features:

     

       44
       +
       

     

       45
       +
       - old content is updated over time to "repoint" to the location of archived content / usernames -- e.g. either on the same service or somewhere else (e.g. [Tweetback Canonical mapping](https://github.com/tweetback/tweetback-canonical)

     

       46
       +
       - if original web links are dead, attempt to get a wayback machine link version

     

       47
       +
       - a specialized client that does display / search / other custom Twitter features that Bsky doesn't have, or somehow maps between them

     

       48
       +
       

     

       49
       +
       ## Twitter Lexicon

     

       50
       +
       

     

       51
       +
       A Twitter Lexicon would support metadata that isn't supported by the base bsky post Lexicon.

     

       52
       +
       

     

       53
       +
       It could also store things like likes, where it would be a "like" -> pointing to the `x/twitter.com/` original post URI.

-3

_notes/Twitter Archive to your own Bluesky AT Protocol.md

···

       1
       -
       Planning to use [twitter-to-bluesky](https://github.com/marcomaroni-github/twitter-to-bluesky)

     

       2
       -
       

     

       3
       -
       Turns out I didn't have a copy of my Twitter archive available any more, so I requested it again, and now have it backed up elsewhere.

+43

_notes/web desktop.md

···

       1
       +
       ---

     

       2
       +
       wikipedia: https://en.wikipedia.org/wiki/Web_desktop

     

       3
       +
       permalink: /notes/webdesktop

     

       4
       +
       ---

     

       5
       +
       ## Awesome Web Desktops

     

       6
       +
       

     

       7
       +
       <https://github.com/syxanash/awesome-web-desktops>

     

       8
       +
       

     

       9
       +
       The web's biggest curated directory of apps, portfolios and experiments that mimic the appearance and functionality of desktop operating systems, these are commonly known as [Web Desktops (wikipedia)](https://en.wikipedia.org/wiki/Web_desktop).

     

       10
       +
       

     

       11
       +
       Wikipedia:

     

       12
       +
       

     

       13
       +
       > A web desktop or webtop is a desktop environment embedded in a web browser or similar client application. A webtop integrates web applications, web services, client–server applications, application servers, and applications on the local client into a desktop environment using the desktop metaphor. Web desktops provide an environment similar to that of Windows, Mac, or a graphical user interface on Unix and Linux systems. It is a virtual desktop running in a web browser. In a webtop the applications, data, files, configuration, settings, and access privileges reside remotely over the network. Much of the computing takes place remotely. The browser is primarily used for display and input purposes.

     

       14
       +
       

     

       15
       +
       ## Simone's Blog Post

     

       16
       +
       

     

       17
       +
       From the Awesome Web Desktops list maintainer, posted [August 14, 2023](https://system31.simone.computer/blog/desktops-zip). A few quotes from the article:

     

       18
       +
       

     

       19
       +
       > One of the main [questions](https://news.ycombinator.com/item?id=37032082) that I see popping up in Hacker News discussions whenever a new web desktop project gets shared is always:

     

       20
       +
       >

     

       21
       +
       > _Is there an actual use for these kinds of projects, beyond showing what can be done?_

     

       22
       +
       >

     

       23
       +
       > Personally, after navigating 169 sites and 30 archived ones, my answer is: yes. Web Desktops were generally very popular back in 2008/2009, then the trend slowly faded leaving space to mostly nostalgic nerds, but in general, you can build a lot of cool tools and complex web apps using a desktop metaphor. Especially these days with the support of powerful JavaScript frameworks.

     

       24
       +
       

     

       25
       +
       ---

     

       26
       +
       

     

       27
       +
       > An [interesting discussion](https://blog.codinghorror.com/avoiding-the-uncanny-valley-of-user-interface/) was raised by Jeff Atwood back in 2008, on the use of desktops elements and interactions applied to web apps. In the article, he didn't particularly support the idea of having desktops conventions into web applications, and he actually makes a good point:

     

       28
       +
       >

     

       29
       +
       > _When you build a "desktop in the web browser"-style application, you're violating users' unwritten expectations of how a web application should look and behave_

     

       30
       +
       >

     

       31
       +
       > But does this still hold up in 2023? By now, we should be pretty used to all kinds of wild user experiences on the web, even for enterprise software.

     

       32
       +
       

     

       33
       +
       ## Local List

     

       34
       +
       

     

       35
       +
       <!-- tagged with webdesktop -->

     

       36
       +
       

     

       37
       +
       <ul>

     

       38
       +
       {% for post in site.notes %}

     

       39
       +
       {% if post.tags contains "webdesktop" %}

     

       40
       +
       <li><a href="{{ post.url }}" class="internal-link">{{ post.title }}</a> {% if post.link %}<a href="{{ post.link }}" title="Website">🌐</a>{% endif %} {% if post.github %}<a href="{{ post.github }}" title="Github">🧑‍💻</a>{% endif %}</li>

     

       41
       +
       {% endif %}

     

       42
       +
       {% endfor %}

     

       43
       +
       </ul>