I've been working on a specification for better, networked bookmarks. A problem I'm currently facing: I share a lot of links. I have a channel on my Slack workspace called #walkers-claptrap where I share anything / everything that I find noteworthy. It's a bit like #linking-together. That said, not everyone I share bookmarks with (and short remarks about them) are at work, so I'm frequently duplicating and sharing over multiple lines of communication (texting, social media, slack, etc). Even then, those channels aren't easily traversed and are organized linearly. I don't love sorting things by date when their value isn't directly scoped to time. I'd also prefer to publish some place that I own and syndicate elsewhere, so that rules out Twitter. semi-solution: The claptrap specification. A graph of links / small notes. The edges are based on relationships or membership with some group. A claptrap MUST be hosted plaintext and MAY be accessed with curl or similar tool (sort of like Carmack's .plan files). A claptrap MAY expose an RSS of updates to syndicate to channels etc. A claptrap MAY reference external claptrap nodes to network / branch beyond the local graph. Still very much a work in progress. Does anyone have a similar problem; do you have a solution you like? I want to bridge the gap between "personal knowledge base" and "sharing links into the ether"

I used to work with this guy who shares a lot of links. His solution is to sync his notes (where he tracks links) up to a website that generates an RSS feed at a regular interval. That RSS feed is plugged into a channel at slack. He left the company, but that channel lives on.

I like that links are colocated with the notes. I don't love that they're organized linearly. Interesting either way, and I love that their channel is living on

They’re also ordered by category in a tree view slightly lower. The top of that page is just like the ten most recent.

probably orthogonal, but may offer ideas: I am currently using Kinopio (kinopio.club) for keeping tagged notes and brainstorming and minutes for the Toronto Lisp meeting group and TODO lists and archives. Kinopio runs in the browser and can run on my desktop and my phone and can be shared with others (private, read-only, world write/collaboration.). The Kinopio API allows direct automatic manipulation.

Interesting. I haven't seen this before. I'm going to have to play around with it

The person behind Kinopio has a lovely essay on what they call “organic software”

The rabbit hole goes deeper!

once upon a time I tripped over a bunch of parentheses and I landed in APL and 6502 assembly. I haven’t found my way out, yet.