DanConwayDev

freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com

Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

NIP-57 Address

Profile Code

nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0duukj7

Publishing to

nos.lol

relay.nostr.band

relay.damus.io

Author Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

Show more details

Last Notes

2024-09-11 08:51:51

- reply

Nice. I get that is ancillary to nostr. I'm only asking because my project is going to start using it. Not now but soon™. Would you be interested in a PR when it comes time for me to implement it? It might involve some input regarding how you would like it to fit into your library and which dependencies you would like to use for RESTful API requests, etc.

2024-09-10 13:58:20

- reply

Who is we?

2024-09-10 12:36:49

- reply

gitworkshop.dev and ngit have benefited greatly from the work you have done: analysis, testing, PM, etc. I am personally very grateful.
sourcing funding for this in nostr may be challenging. Many @npub10pe…n34f grants are like mine: for 1 dev full-time. Most projects don't have access to a pot of money for this. It would be really nice to have a call-off pot for this and other things such as, the great work @npub149p…722q has done on logo design. I wonder though if the Open Source dynamic changes, and an expectation is created, when smaller individual contributions are directly rewarded with money.

2024-09-09 20:38:15

- reply

What if you could somehow provably burn 21 sats?

2024-09-09 20:34:16

- reply

Do you tunnel through multiple VPN providers so that the one who knows your IP doesn't automatically know your connecting too?

2024-09-09 12:06:31

- reply

have a question about color. Did you put thought into using that blue?
The current GitWorkshop color palette is as follows:
```json
{
"color-scheme": "dark",
"primary": "#ff79c6",
"secondary": "#bd93f9",
"accent": "#ffb86c",
"neutral": "#414558",
"base-100": "#282a36",
"base-content": "#f8f8f2",
"info": "#8be9fd",
"success": "#50fa7b",
"warning": "#f1fa8c",
"error": "#ff5555",
"nostr-purple": "#9333ea"
}
```
It is a color palette from the DaisyUI Dracula theme, with the standard DaisyUI purple.
What do you think about using purple as the logo color to bring in Nostr connotations?
For ngit, did you take the red from the Git logo? Perhaps that red doesn't sit nicely on my current color palette.

2024-09-06 15:35:20

- reply

This is the challenge. Clients aren't incentivesd to support it because most clients don't publish with it. Clients don't publish with it because most clients don't support it. Catch 22.

2024-09-06 15:26:59

- reply

Is that the generic reply kind? Why clients support notifications for that?

2024-09-06 15:05:12

- reply

This is an example of progress. We just need a few more @nprofile…69jx's out there nudging people towards creating issues on nostr and adoption will increase and then hopefully snowball. Thanks @nprofile…69jx
#nevent1q…8fvc

2024-09-04 21:30:32

- reply

If you are running behind schedule just descope the important bits and spend the rest of the budget on marketing the project as a success.

2024-09-04 13:09:40

- reply

I was referring to NIP-34

2024-09-04 12:50:18

- reply

Thanks? Do you mean getting repositories and their contributors off github onto a nostr based solution is a hard challenge?

2024-09-03 18:25:23

Can anyone recommend a good no-KYC VPS / hosting solution for a Svelte App and stateless web services that takes bitcoin? #asknostr #nostrdevs #devs

2024-09-03 12:28:12

- reply

If they are already on nostr in don't think it is rude.

2024-09-03 10:15:15

- reply

Here's the client I work on: https://gitworkshop.dev

2024-09-03 09:58:54

- reply

I'm not worried. this is how new things begin. perhaps projects will start off using nostr alongside github and as usage grows on the nostr side, fully transition to only accepting issues and PRs over nostr.
@npub1ye5…knpr 's noStrudel is just one example of a repository on the journey. its got 99 open issues and 4 open PRs on github and 5 open issues and 0 open PRs on nostr.
https://gitworkshop.dev/r/naddr1qqykum6nw3e82er9dsqs6amnwvaz7tmwdaejumr0dspzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qvzqqqrhny5zxf4f/issues
Issues and PRs raised on nostr get interest and engagement from across nostr and not just users using git specific clients. So the value proposition is quite different than self-hosted gitlab / forgejo.

2024-09-03 09:13:28

- reply

#nevent1q…cz02
#nevent1q…kzwm #nevent1q…p6un
#nevent1q…s2l8

2024-09-03 09:05:00

- reply

It is being talked about every day on nostr but perhaps not on everyone's feed.

2024-09-03 08:52:19

- reply

Maybe, the user could choose to use the browser, use their locally cloned repos via a new command like `ngit serve`, or use a service that does it in the cloud and serves them the required data at much lower bandwidth.
#nevent1q…erg4

2024-09-03 08:37:23

- reply

We discussed it back in March and here are some numbers for the bitcoin core repo:
#nevent1q…gmr6
tbh those numbers are not that big. last time I checked, git implementations in the browser don't support these advanced flags. doing a full clone automatically in the browser is probably a bad idea as it is unfair on those who are bandwidth constrained.
But this could be done statelessly on a server fairly quickly. bandwidth on a VPS is probably quite cheap these days so if traffic volumes were low it shouldn't be too expensive.
Depending on the bandwidth vs storage costs it could be worth storing a clone of repositories and using that instead. That way it would be easier, or cheaper per interaction, to allow browsing commits, metadata, etc.
From a decentralisation point of view, I could build `ngit serve` which could be used instead (even in offline scenarios) instead of the proxy.

2024-09-02 23:30:02

- reply

@nprofile…vpy4 and I were discussing with cashu dev @nprofile…rk82 in riga the possibilities of zapping into a nutsack that's encumbered by a 2 of 3 multisig between the zapper, the dev / dev team and an oracle that can handle disputes. The zapper can even set a time limit where they can automatically claim back the funds if the feature isn't implemented. This is exciting stuff and would enable more meaningful amounts to be commited as bounties doe features. But at outset just having issues with a zap split that goes to the dev and a UX where zapping an issue is an indication to the devs that the feature is a higher priority for the zapper would be a win. What do you think?

2024-09-02 22:41:36

- reply

you should try out song: #naddr1qq…x40v
it's @npub180c…h6w6's vision of a minimalist git server implementation to work with #GitViaNostr.
Tomorrow's task it to fix the git-remote-nostr so that it works seamlessly with it.

2024-09-02 22:05:19

- reply

as you can see the HTTP API thing is a bit of a mess but the most common format is`https://<host>/<path/to/repo>/raw/<ref>/<path/to/file>`
```typescript
/** most servers will produce a CORS error so a proxy should be used */
export const cloneArrayToReadMeUrls = (clone: string[]): string[] => {
const addresses = clone.map(extractRepoAddress)
/**
* at the time of this commit these urls work for:
* self-hosted gitea (or forgejo), gitlab
* github.com
* bitbucket.org
* gitlab.org
* gitea.com
* codeberg.org (forgejo instance)
* sourcehut (git.sr.ht)
* launchpad.net
* It doesnt work for:
* self-hosted gogs (requires branch name repo/raw/master/README.md)
* sourceforge.net (https://sourceforge.net/p/mingw/catgets/ci/master/tree/README?format=raw)
* notabug.org (requires branch name notabug.org/org/repo/raw/master/README.md)
*/
return [
...addresses.flatMap((address) => {
let prefix = 'raw/HEAD'
if (address.includes('sr.ht')) prefix = 'blob/HEAD'
if (
address.includes('git.launchpad.net') ||
address.includes('git.savannah.gnu.org')
)
prefix = 'plain'
if (address.includes('github.com')) {
// raw.githubusercontent.com can be used without CORS error
address = address.replace('github.com', 'raw.githubusercontent.com')
prefix = 'HEAD'
}
return ['README.md', 'readme.md'].map(
(filename) => `https://${address}/${prefix}/${filename}`
)
}),
]
}
```

2024-09-02 20:47:49

- reply

I considered that and experimented with it. There is a lack of support to do it in the browser. In any case, it is too heavy to do client side. And too slow / bandwidth inefficient to do on demand on the server-side. It could potentially be done as a job run daily but it is ultimately reliatively expensive operation to run give we are just looking for the readme.

2024-09-02 17:06:05

- reply

unfortunately the git feature for getting the contents of specific files `git archive` is off by default so it makes getting the README.md challenging.
many git server implementations expose raw files in a repo over https using similar APIs. Unfortunately some of them don't allow display directly CORS and other eg github have heavy throttling.
until last week I was proxying requests to allow support for git servers without CORs exceptions but I have, perhaps temporarily turned that off so gitworkshop.dev could be entirely statically built.
when I wrote the feature it supported (with the proxy):
self-hosted: gitea, forgejo and gitlab
hosted: github, bitbucket.org, gitlab.org, gitea.com, codeberg.org, sourcehut, launchpad.net
feedback welcome on how to proceed with this.
I'm thinking about opening a PR for @npub180c…h6w6's song to expose the raw files over https. would you be interested in this @npub180c…h6w6?

2024-08-31 10:33:46

- reply

You should be in on

2024-08-30 20:53:02

- reply

FYI @npub19w6…syzj @npub1yay…trdv @npub1ecd…s735 @npub1q6y…t3sh

2024-08-30 20:48:55

- reply

There will be a call to discuss next steps on creating DVMs for CI on Tuesday 1500-1600 UTC. All welcome. This one will be on Signal. https://signal.group/#CjQKIKJiex5Jw2qDiV9QjJ7zVSGoNG5kCH9XUhdq4r4QVYsuEhDFFZuW9SDMgC7N3QDpL4QF

2024-08-30 15:44:37

- reply

I'm closing this as a duplicate of #nevent1q…flla

2024-08-30 15:37:49

- reply

I pushed v1.4.5 did that fix this?

2024-08-30 13:50:49

- reply

There is a project called nostrCI that @npub1zaf…26k5
presented on in riga. its about interoperability across nostr clients and there is a overlap with CI on nostr. There is a signal group for it and a call happening at 1430 UTC. If you want to join the singal group or the call, please shout up.
@npub1mgv…pdjc @npub19w6…syzj @npub1myg…sn5p @npub1ecd…s735

2024-08-30 11:44:13

- reply

@npub15qy…yejr discovered this and it should be fix in commit b4459e98d816f6f278a4e9ab76883008d0b946fe which forms part of the next point release.

2024-08-30 09:38:23

- reply

sure. I just pushed an update for this. it would be nice if NDK's `event.encode()` does this automatically @npub1l2v…ajft . it is just a one line change.

2024-08-30 09:04:48

- reply

Appreciate you guys

2024-08-29 14:22:38

- reply

I think this is related to an issue with rust-nostr v0.33 as I had this with one other repo. I have bumped this to v0.34 on the master branch which fixed it for that repo so that might fix it. I'm away from my desk until tomorrow but I'll issue a minor version of ngit with the fix tomorrow.

2024-08-28 23:38:46

- reply

Thanks. I'm now using it.

2024-08-28 21:11:08

- reply

yes that works with the previous 500ms timeout.

2024-08-28 20:13:06

- reply

Just one:
```rust
fn get_first_proposal_event_id() -> Result<nostr::EventId> {
// get proposal id of first
let client = Client::default();
Handle::current().block_on(client.add_relay("ws://localhost:8055"))?;
Handle::current().block_on(client.connect_relay("ws://localhost:8055"))?;
let proposals = Handle::current().block_on(client.get_events_of(
vec![
nostr::Filter::default()
.kind(nostr::Kind::GitPatch)
.custom_tag(
nostr::SingleLetterTag::lowercase(nostr::Alphabet::T),
vec!["root"],
),
],
nostr_sdk::EventSource::relays(Some(Duration::from_millis(1000))),
))?;
Handle::current().block_on(client.disconnect())?;
let proposal_1_id = proposals
.iter()
.find(|e| {
e.tags
.iter()
.any(|t| t.as_vec()[1].eq(&FEATURE_BRANCH_NAME_1))
})
.unwrap()
.id;
Ok(proposal_1_id)
}
```

2024-08-28 20:10:16

- reply

It gets triggered in ngit intergration test module list::when_latest_revision_rebases_branch
So those tests endlessly run with a timeout of 500ms under v0.34.0 so I bumped it to 1000ms.

2024-08-28 19:57:11

- reply

Relay

2024-08-28 18:18:44

- reply

I've released there is a problem with the format. if you dont specify a directory name, git will use anything after the last `/`. so in this case it will add the ?relayhint=git.fiatjaf.com to the director name.
perhaps we should switch to the less intuative but still readable:
nostr:://npub123/git.fiatjaf.com/relay.damus.io/identifier

2024-08-28 18:14:29

- reply

is it a problem if you can use either?

2024-08-28 18:04:43

- reply

This is great. I'll get ngit working with it.

2024-08-28 17:49:25

- reply

are you referring to the "client overwrites my list with empty values" problem?

2024-08-28 17:25:33

- reply

They miss notifications that amethyst captures

2024-08-28 17:25:04

- reply

*reads raw json to see if anything interesting is happening*

2024-08-28 17:22:43

- reply

You know how people in bitcoin talk about month long detailed discussions about new approaches to something and then up realising that greg maxwell suggested a better approach 10 years ago? I feel that way about fiatjaf sometimes.

2024-08-28 17:17:43

- reply

Good point. and blossom. I would actually prefer this to reduce the number of events we need to ask for and manage but I'm pretty sure you meant this as a counter argument.

2024-08-28 17:01:22

- reply

You can zap commits submitted using NIP-34. For example:
#nevent1q…swn2

2024-08-28 16:57:46

- reply

I need to add zapping support so we can don't directly in gitworkshop.

2024-08-28 16:57:00

- reply

I just zapped this commit using amethyst:
#nevent1q…uleu

2024-08-28 16:23:27

- reply

Is this a terrible idea?
```
{
"kind": 10002,
"tags": [
["r", "wss://expensive-relay.example2.com", "write"],
["r", "wss://git.fiatjaf.com", "git"]
],
}
```

2024-08-28 16:13:51

- reply

I'm also in that club. It's so satisfying seeing your creation work seamlessly under the predefined test condition before it gets broken by the real world.

2024-08-28 16:11:41

- reply

yes, its great to have more options to access AI without KYC.

2024-08-28 14:15:17

- reply

As a creator of tools which I hope will bring value to those who use them, user retention is a useful measure of whether user received value enough to return.

2024-08-28 12:41:11

- reply

apparently it is not a valid store path

2024-08-28 12:31:13

- reply

completely agree

2024-08-28 12:30:12

- reply

I get that the incentives are skewed. but they are pretty effective at attracting and retaining large number of users. to achieve this they do heavily surveillance on user activity, many iterations of a+b testing tweaks to their UI to create UX. If we can learn lessons from them, so long as we critically evaluate knowing they are prioritise attention and retention above satisfaction and well being.

2024-08-28 12:23:39

- reply

in the first example they use I'm guessing cigxbmvy6dzix98dxxh9b6shg7ar5bvs is the derivation hash and qhqk4n8ci095g3sdp93x7rgwyh9rdvgk is the output (binary) hash. Is that right?
In which case the derivation doesn't include the output hash or am I missing something?
https://nix.dev/manual/nix/2.18/command-ref/nix-instantiate#examples
```
nix-instantiate test.nix (instantiate)
/nix/store/cigxbmvy6dzix98dxxh9b6shg7ar5bvs-perl-BerkeleyDB-0.26.drv
nix-store --realise $(nix-instantiate test.nix) (build)
...
/nix/store/qhqk4n8ci095g3sdp93x7rgwyh9rdvgk-perl-BerkeleyDB-0.26 (output path)
ls -l /nix/store/qhqk4n8ci095g3sdp93x7rgwyh9rdvgk-perl-BerkeleyDB-0.26
```

2024-08-28 11:27:59

- reply

5 star rating systems are used by data driven tech companies which have huge resources to study their effectiveness, such as Amazon. The fact that they haven't moved away from it is signal that its useful.

2024-08-28 11:01:57

- reply

but how do you get the derivation output hash from the build recipe?
thats a cool project. thats exactly what I was talking about with different peers doing the build and reporting back that they got the same hash. These could be nostr trust attestation events.

2024-08-28 10:48:28

- reply

haha. who ever uses 3 stars? its 1, 4 or 5.

2024-08-28 10:47:49

- reply

😂 step 1. log into my app, step 2. automatically sends 5 star review with glowing comments without you realising.

2024-08-28 10:44:55

- reply

as we live in a bazaar, you can control how other clients might 'abuse' a carefully thought rating system. for example someone may have designed a 1-5 rating system for an event kind and use it extensively in their app. Another client presents the user with the option to star the same event and sends in a 5 star rating.

2024-08-28 10:40:18

- reply

Yeah, it is pretty cool

2024-08-28 10:38:13

- reply

I know right. its the magic of nostr. it is why we keep showing up.

2024-08-28 10:36:27

- reply

but numeric rating systems are only so useful.
evaluating other heuristics can lead to more accurate summary of the opinion of your community.

2024-08-28 10:32:07

- reply

but if you don't build yourself, you are trusting whoever has given you the hash. getting trust assertions from a verity of sources that a version should produce that hash means that you are drastically reducing your trust in any one source.

2024-08-28 10:27:47

- reply

it wouldn't take much computing power to produce those events, but relays might reject them as SPAM if they have old timestamps.
Hopefully we could do an ok job at identifying the spam, between relays, WoT analysis and even more sophisticated WoT analysis done by DVMs. Thinking more about it relays are pretty incentivised to do good spam prevention. we could select relays we think are doing a good job at it and use them rather than using DVMs too much.

2024-08-28 10:22:18

- reply

a repo might have an iOS, Android and Web application profile, and the opinions of those profiles should be somewhat separate because the UX might vary significantly.
I think opinions are more likely to be made against the application profile than specific releases. I'm unsure of the best way to gather opinion heuristics in this area and how to display them to the user.

2024-08-28 10:16:52

- reply

As of yesterday they are now in zapstore. I plan to display all releases related to a git repository in gitworkshop.dev

2024-08-28 10:12:53

- reply

In Riga we were discussing having a
1) a generalized DVM that finds events that indicate an opinion on the thing (product, app, etc) and filters out the SPAM; that feeds into
2) DVM specific to a usecase that takes that opinion data and summarise it in a whay that is useful to a client. eg so they can prioritise its display in the interface or express the opinion through words, emojis or, god forbid, a 1-5 star rating.

2024-08-28 10:03:34

- reply

If there were a two way relationship between the 'application profile' in the app store NIP and the 'repository announcement' in nip34, then clients could associate those ratings with both things. currently it is one way (nip34 announcement is referenced by the application profile event).

2024-08-28 09:59:21

- reply

I often build binaries from source. Wouldn't it be cool if, whenever I built a binary from a reproducible build, I could elect to easily publish to say that I validated that the commid-id / version tag produced a binary with the correct check sum, or not via nostr?

2024-08-28 09:55:22

- reply

As a nix user, and as a maintainer of a project that needs binaries installed, I'm also more broadly interested in your idea. This is on top of the obvious overlap of A DVM that builds binaries.

2024-08-28 09:52:44

- reply

Definitely. @npub1wf4…dgh9 and I both have immediate usecases for a DVM that runs CI to build artifacts (for @npub10r8…t2p8) and lint, tests etc (for #GitViaNostr). We were thinking that may projects have github actions and there is an open source GitLab CI runner that github actions so that could be a good place to start.
Then we met @npub1hw6…65gr who was also interested in this and @npub1grx…87js who is interested in DVM more generally.
Now you are up to speed on the context!

2024-08-28 09:42:24

- reply

but also I have friends who I have little overlap in movie or restaurant preferences. The fact that they liked something actually signals to me that I wouldn't like it.

2024-08-28 09:41:30

- reply

@npub1wf4…dgh9 is a 1-5 star rating system maxi

2024-08-28 09:37:34

- reply

You could also value to the rating of npubs that like the same things you like more.

2024-08-28 09:34:40

- reply

I like it. Who would control what packages made the cut? You could run a blossom server and store the binaries on using that to add resilience.

2024-08-28 09:27:50

- reply

That's great too here!

2024-08-28 09:26:48

- reply

Yeah. I really want to get this in. There a few bugs and resilience changes I have slightly higher on the list.

2024-08-28 09:21:20

- reply

Definitely. I'm interested. Tell me more?

2024-08-28 09:18:37

- reply

thanks. I can talk you though it on a call if like.
there are a couple of bugs where it tries to authenticate you to the git server when it shouldn't have too that I'm looking at today.

2024-08-28 09:15:34

- reply

@nprofile…vpy4 @nprofile…359y @nprofile…63va @nprofile…79p8 and a few others were discussing the virtues and drawbacks of WoT rating systems in Riga.

2024-08-28 00:41:46

- reply

I'm starting to think you are just making these after looking at my repositories!
#nevent1q…3anx

2024-08-27 23:45:12

- reply

You were doubting your skills too much. The file wasn't there. Its there now in v1.4.4.

2024-08-27 23:39:33

Those of us who are interested in DVMs for CI on nostr should start collaborating.
@npub1hw6…65gr @npub1wf4…dgh9 @npub1mgv…pdjc
eg. building artifacts, running tests and deploying code.
there is an open invitation - comment on this note and we will loop you in

2024-08-27 23:04:53

- reply

also if the user exits the process at this point and attempts to push a new commit to the proposal, it will issues a completely new proposal.

2024-08-27 22:52:43

- reply

ah the classic MacOS fingerprint - a DS_Store file

2024-08-27 22:51:35

- reply

thanks for trying it out!

2024-08-27 19:35:08

- reply

Yes but I'm just away from my desk for a couple of hours. There should be git-remote-nostr and ngit inside the tar zip. If there is not then there is a problem with the release build system.

2024-08-27 18:59:26

- reply

Yes. Its included in the tar zip of the release

2024-08-27 18:58:38

- reply

Both

2024-08-27 18:31:22

- reply

In fact, if one of the git server(s) is ahead of the git state with conflicting changes, the user maintainer needs to push directly to that git server to overwrite the changes before they can proceed to get everything back in sync by pushing to the nostr remote.
All of this will only happen on the rare occasion that conflicting changes are pushed at about the same time or if some maintainers stop using the nostr remote as the default one.

2024-08-27 18:28:28

- reply

if 01010202 is in the ancestory of 11112222 then it `git push` will work fine. if it is not, `git push --force` must be used to purposefully overwrite and potentially lose someone else's change. this is standard git.
The git remote helper also check each git server listed to ensure it is not overwriting any ones changes pushed directly to each server as sometimes the state of the git server might differ from the nostr state event.

2024-08-27 18:24:14

- reply

if a state event has been issued (so state is being managed on nostr) the remote helper still checks the refs on the git server(s) to add protections to reduce the likelihood that another maintainer pushes a conflicting change at about the same time which gets overwritten.
Also covering the scenario where there owner or another maintainer starts pushing directly to the git server (by passing the state on nostr). in this case the latest conflicting changes on the git server shouldn't be automatically overwritten without the owner being warned about it.

2024-08-27 18:20:01

- reply

the server should respond to a 'list' request with return the refs.
the remote helper tries to get the refs on the remote server so it can check if there is a conflict.
in git push should only work if its a fast-forward commit unless the `--force` flag is used.

2024-08-27 18:12:42

- reply

I havn't updated the remote helper yet so that it will push a new state event if one doesn't exist and the git server responds with a not found error (as apposed to timeout).
until I have done that you will need to have the repository on the git server, which it will use as a source for the first state event.

2024-08-27 18:03:45

- reply

the repository already exists on the git server?