@Scott's Code Journal
A place where I randomly share information, code, and resources that I find as I work on various web development projects.
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqdy097yls3q06tczeu62n22vkenug5tcuzjwevv2wt4k2wuafvvpq3pdwj0
Do you know why your account constantly sends Update activities?
The actor ID is htt...
@silverpill Probably because you are following me on [email protected] instead of [email protected] and I am posting from [email protected].
My understanding is that since ActivityPub does not understand nomadic identity and many platforms would reject my post if it came from hubzilla.monster, my two hubs synchronize and authorship.studio is who actually sends the post to you.
So the post will be signed by whatever account you are following. The actor would show the one that is currently primary.
At least that is my understanding of how it works.
My understanding is that since ActivityPub does not understand nomadic identity and many platforms would reject my post if it came from hubzilla.monster, my two hubs synchronize and authorship.studio is who actually sends the post to you.
So the post will be signed by whatever account you are following. The actor would show the one that is currently primary.
At least that is my understanding of how it works.
1
I've been building out the Knowledge Management section of the Development Guide Docs repository.
The collection now includes documents organized into four areas:
Foundations -- core concepts of knowledge managementKnowledge Assets -- creation, maintenance, and preservationKnowledge Creation -- how ideas become knowledge assetsKnowledge Discovery -- helping people find and use information
One thing worth noting: documentation and knowledge management are not the same thing. Documentation is one type of knowledge asset. Knowledge management is the broader discipline of creating, organizing, maintaining, discovering, distributing, and preserving knowledge.
These documents are still drafts, but they have reached the point where they are useful enough to share. The framework page includes a recommended reading order if you want to start from the beginning.
#^https://github.com/WisTex/Development-Guide-Docs/blob/main/docs/knowledge-management-framework.md
Feedback is welcome.
#Documentation #KnowledgeManagement #TechnicalCommunication #OpenSource #Hubzilla
The collection now includes documents organized into four areas:
Foundations -- core concepts of knowledge managementKnowledge Assets -- creation, maintenance, and preservationKnowledge Creation -- how ideas become knowledge assetsKnowledge Discovery -- helping people find and use information
One thing worth noting: documentation and knowledge management are not the same thing. Documentation is one type of knowledge asset. Knowledge management is the broader discipline of creating, organizing, maintaining, discovering, distributing, and preserving knowledge.
These documents are still drafts, but they have reached the point where they are useful enough to share. The framework page includes a recommended reading order if you want to start from the beginning.
#^https://github.com/WisTex/Development-Guide-Docs/blob/main/docs/knowledge-management-framework.md
Feedback is welcome.
#Documentation #KnowledgeManagement #TechnicalCommunication #OpenSource #Hubzilla
One of the things I have been doing recently is capturing documentation as I go.
When you are deep in a project, you figure out things that are not well documented anywhere. The problem is, if you do not write it down while it is fresh, you forget it... or you have to rediscover it later.
So I started keeping a GitHub repository where I capture notes and reference documents as I work. The idea is simple: write it down now, publish it later. The source lives in the repo, and from there it can be published to development.guide, neuhub.org, federatedhub.org, or wherever else makes sense.
It is just getting started, but it is public and contributions are welcome.
#^https://github.com/WisTex/Development-Guide-Docs
When you are deep in a project, you figure out things that are not well documented anywhere. The problem is, if you do not write it down while it is fresh, you forget it... or you have to rediscover it later.
So I started keeping a GitHub repository where I capture notes and reference documents as I work. The idea is simple: write it down now, publish it later. The source lives in the repo, and from there it can be published to development.guide, neuhub.org, federatedhub.org, or wherever else makes sense.
It is just getting started, but it is public and contributions are welcome.
#^https://github.com/WisTex/Development-Guide-Docs
It has been a while.
Life had other plans... family emergencies, emergency plumbing, storm damage, and a few other things I won't bore you with. Let's just say the last year or so kept me busy in all the wrong ways.
But I'm back.
I won't be logging in every day, and I can't promise quick replies; there's still a lot going on behind the scenes. But I am here, and I am building again.
Even during the quiet period, I wasn't idle. I've been planning, acquiring domains, sharpening skills, and doing a lot of work that wasn't visible yet. Some of that is about to become visible.
This is my code journal account, so expect posts about what I'm building, what I'm learning, and what I'm launching. In fact, stay tuned; there's another post coming right after this one about something I recently created.
It's good to be back.
Life had other plans... family emergencies, emergency plumbing, storm damage, and a few other things I won't bore you with. Let's just say the last year or so kept me busy in all the wrong ways.
But I'm back.
I won't be logging in every day, and I can't promise quick replies; there's still a lot going on behind the scenes. But I am here, and I am building again.
Even during the quiet period, I wasn't idle. I've been planning, acquiring domains, sharpening skills, and doing a lot of work that wasn't visible yet. Some of that is about to become visible.
This is my code journal account, so expect posts about what I'm building, what I'm learning, and what I'm launching. In fact, stay tuned; there's another post coming right after this one about something I recently created.
It's good to be back.