purple.co

Looks like an option that can be set by maintainers, and default can be wiki or a long note ( readme ). At some point in time some settings will be require for a repository. I prefer local only client only, no server side, and cached if is possible.

2024-05-24 11:02:23

- reply

how I logout and switch to another account ?

2024-05-21 20:07:46

- reply

fyi, https://github.com/BLAKE3-team/BLAKE3

2024-05-21 19:55:30

- reply

true. front end, not backend

2024-05-21 19:26:58

- reply

or file slice ! you can add many and get the file. I think http supports partial get and file can be split in many slices ( Web/HTTP/Range_requests ) with hash for each slice.

2024-05-21 19:18:48

- reply

it can work for read only project.

2024-05-21 19:16:21

- reply

blossom looks like a DHT node in this case. you only need
Kademlia . It will be nice to have flexible endpoint, like https://git/user/project/branch/sha256.ext

2024-05-21 18:36:13

- reply

can blossom work with webtorrent and peertube if the same file has multiple enddpoints?

2024-05-21 18:31:14

- reply

https://retroshare.cc

2024-05-21 18:28:21

- reply

https://docs.spacemesh.io
ps: fyi, https://richardschneider.github.io/net-ipfs-core/articles/multihash.html

2024-05-21 18:19:56

- reply

sounds like a feature for "ngit node start" and blossom webtorretent, tokio style. :) . maybe an commit/patch can be expose like this and can be download ( lfs ) from multiple sources.

2024-05-21 17:51:16

- reply

if all commits are like notes ( content/hash ), is possible to expose a git repository as nip34 nostr notes, with some kind of reverse proxy ?

2024-05-21 17:43:24

- reply

FYI, https://gitworkshop.dev/repo/nips . Some devs moved from github or don't have accounts.

2024-05-21 17:37:56

- reply

I think git helpers require URL format, like ://

2024-05-20 10:42:30

- reply

I think the idea is not to enter naddr every time, and have that store/compute. Is like url for a remote after clone, just a reference that you use, and not have to input after , for any operation.

2024-05-20 10:09:57

- reply

how about if is part of rust-nostr-ngit sdk ? Maybe git extension can be put in crate as a extension. If is used every time I try pull or list, is not a "minority".

2024-05-18 11:22:38

- reply

how ? specs ? i think is ok for maintainers.yaml to point to right address/identifier ( like git remote ? ) and use/cache/change.

2024-05-17 11:12:33

- reply

some thread we got here.

2024-05-17 11:11:28

- reply

Can we add naddr to yaml and use if not empty?

2024-05-16 16:51:10

- reply

try first, then we talk.

2024-05-16 16:27:02

- reply

still, as we can see, is quite functional !

2024-05-16 16:25:44

- reply

ngit works with maintainers.yaml , and this is not in github repo, only as nostr notes and ngit,

2024-05-16 16:19:46

- reply

you can ask fiatjaf very nice, who knows. :)

2024-05-16 16:18:31

- reply

I don't have a github account and I can't merge in github this, only ngit/nostr. This need to be "discuss" with nostr/nips contributors. Best part is that we can "use" this as it is.

2024-05-16 15:39:47

- reply

sorry, is just a file.

2024-05-16 15:08:21

- reply

ngit works , git can't !

2024-05-16 14:49:42

- reply

https://gitworkshop.dev/repo/nips : how many relays do you see ?

2024-05-16 13:56:24

- reply

do you see 3 or 4 relays after ngit pull / list ?

2024-05-16 13:50:04

https://en.wikipedia.org/wiki/Red_pill_and_blue_pill

2024-05-16 13:46:14

- reply

https://radicle.xyz/

2024-05-16 13:33:48

- reply

or can be radicle ( .xyz ).

2024-05-16 13:27:59

AI_agents:
- devin: https://www.cognition.ai/introducing-devin
- plandex: plande.ai, https://github.com/plandex-ai/plandex
- opendevin: https://opendevin.github.io/OpenDevin/
- devika: https://github.com/stitionai/devika
- SWE: https://swe-agent.com, https://github.com/princeton-nlp/SWE-agent
- https://e2b.dev/ai-agents
- https://github.com/e2b-dev/awesome-ai-agents
- https://github.com/paul-gauthier/aider
- https://github.com/MervinPraison/PraisonAI/
- https://github.com/myshell-ai/OpenVoice , https://www.youtube.com/watch?v=VpB6bxh4deM
- https://www.youtube.com/@AllAboutAI/videos
- https://www.youtube.com/watch?v=6dkMwIu1Q1g
p, li { white-space: pre-wrap; }

2024-05-16 13:25:54

- reply

if ngit is liked to remote git repo, it can verify maintainers.yaml ( yml ? ), but depends on how "client " is implemented. how about local repo ?

2024-05-16 13:22:06

- reply

good idea !

2024-05-16 13:13:38

- reply

merged ?

2024-05-16 12:56:41

- reply

Fun fact! This was a simple ngit init test and, after I realize that can work, I sent a FYI message to fiatjaf ( npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 / 3/15/24, 10:41 AM ). I don't know if was delivered (nip44?), but if it works why not ..... I didn't expect PRs or issues and it is clear that anything done here can't be easy integrated in github like this. We will see :) .

2024-05-16 11:55:15

- reply

maybe maintainers must approve if they want to be part of this, and naddr can have a owner/creator.

2024-05-16 11:52:35

- reply

Maintainer is about ngit, contributors is for git, right ? In this case maintainer is about metadata, and ngit.

2024-05-16 11:17:59

- reply

2024-05-16 11:03:10

- reply

local, on a new branch ?

2024-05-16 10:58:46

- reply

any update ?

2024-05-16 10:27:50

- reply

Maybe one nip will define standard predefined response that can be added/imported into a client. If nostr will get 10k types of events it will be impossible to implement by all clients, but a predefined text/response can be integrated more easily and be show just in case.

2024-05-16 09:29:24

- reply

can you edit maintainers.yaml ?

2024-05-16 09:10:16

- reply

#AIAgents
- devin: https://www.cognition.ai/introducing-devin
- plandex: plande.ai, https://github.com/plandex-ai/plandex
- opendevin: https://opendevin.github.io/OpenDevin/
- devika: https://github.com/stitionai/devika
- SWE: https://swe-agent.com, https://github.com/princeton-nlp/SWE-agent
- https://e2b.dev/ai-agents
- https://github.com/e2b-dev/awesome-ai-agents
- https://github.com/paul-gauthier/aider
- https://github.com/MervinPraison/PraisonAI/- https://www.youtube.com/@AllAboutAI/videos
- https://github.com/myshell-ai/OpenVoice , https://www.youtube.com/watch?v=VpB6bxh4deM
- https://www.youtube.com/watch?v=6dkMwIu1Q1g
p, li { white-space: pre-wrap; }

2024-05-16 08:43:55

- reply

I see 2 flows:
1. start with git, and later add ngit / nostr collaboration (init/clone) .
2. start with ngit collaboration (init/clone) and later add git/scm.
In 5-10 years, an AI will read comments / issues / proposals and generate the app and upload to git repo, so, the idea of ngit working independent in the beginning will make sense in the future .
PS: SCM is more than git, ( #fossilscm , #jj, #pijul, #radiclescm, ... )

2024-05-16 07:39:42

- reply

how about ngit clone naddrs ? this will add an .git folder with just config set to git remote, and use later git pull/fetch/....

2024-05-16 07:05:18

- reply

I think 2 stages can be useful. Retired imply deletion, and more difficult to implement by all relays. Or, maybe, locked is like blocked.

2024-05-15 16:39:11

- reply

A lot of events are signed with the key, and very hard to delete all, to keep but locked will allow history/backup, before retire.

2024-05-15 16:25:39

- reply

retired or locked

2024-05-15 16:23:36

- reply

@npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 !

2024-05-15 16:21:58

- reply

2024-04-28 13:31:34

- reply

orbitdb is IPFS/libp2p. ( https://github.com/TryQuiet/quiet?tab=readme-ov-file#how-it-works )

2024-04-26 14:52:40

- reply

gitter was not part of github, but worked together

2024-04-26 14:45:59

- reply

just open in a new tab, but with correct reference.

2024-04-26 14:43:58

- reply

one looks like chat flow / realtime , one looks like forum flow / item based . It can be solved by other apps ( nostrudel,...) , but need to be linked.

2024-04-26 14:39:35

- reply

The idea was to keep this in mind for later. At some point in time it will make more sense.

2024-04-26 07:51:36

- reply

Can we add a follow button to this ? bookmark ?

2024-04-25 11:11:04

- reply

https://meli-email.org , https://git.meli-email.org/meli/meli/tags

2024-04-25 11:04:45

- reply

RFC 4155, RFC 5322
- https://github.com/djc/mbox-reader
- https://github.com/staktrace/mailparse
- https://github.com/stalwartlabs/mail-parser
- ....

2024-04-25 10:59:39

- reply

it can be implemented as only file/mbox, no net / smtp style.
- https://en.wikipedia.org/wiki/Mbox

2024-04-24 16:18:41

#nevent1q…0xzj

2024-04-24 16:17:19

#nevent1q…dr8k

2024-04-24 15:43:48

- reply

looks good. can this be merged / validate ? ( some comments on how is working ? )

2024-04-24 14:54:16

- reply

Add refresh button to force refresh issues / proposals list, on filter line.

2024-04-24 10:59:06

- reply

Also AppImage in portable mode works well (firefox/ungoogle/brave/... )
- https://github.com/srevinsaju/Firefox-Appimage
- https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/appimage/64bit/
- https://github.com/srevinsaju/Brave-AppImage
- https://docs.appimage.org/user-guide/portable-mode.html

2024-04-24 10:48:10

- reply

Most git services require account confirmation over email. There are solution like burner emails, but is complicated and github/gitlab reject accounts this this. It will be nice if can be done OpenID over nostr or use NIP07 , and use that create/use git service . Maybe nostr relay can support OpenID over nostr/NIP44.

2024-04-24 09:56:04

- reply

fyi, https://nostrudel.ninja/#/channels/nevent1qqsg7xynq5a2frh4z7mqeywgywwpze0ezrsnply5ntxrwlyun0et6gc4nsjsx

2024-04-24 09:30:51

- reply

for now PWA works just fine. ( https://github.com/filips123/PWAsForFirefox + https://github.com/diegogurpegui/nos2x-fox )

2024-04-23 19:21:25

- reply

*syncthing
PS: can we edit notes ?

2024-04-23 19:05:59

- reply

webxdc app is just a file, is better for updates and if can run as pwa.

2024-04-23 19:04:28

- reply

gitworkshop can be a nice alternative frontend for gitea. how about emails accounts and webmail frontend? gitea require email to create an account, and we are all on nostr, now.

2024-04-23 18:54:31

- reply

I did some test with small app, based on this: github.com/tiziodcaio/whatsapp-desktop.rs , but changed for gitworkshop.dev. tauri can't handle webextensions/nip07, so it it only readonly, but usefull, works like PWA.

2024-04-23 18:46:21

- reply

if this is done in ngit the term is patch, I think, but in gitworkshop is just a proposal until merged, the term is also PR ( PP ) ( github is centralized, patch is PR, allready deployed )

2024-04-23 18:36:40

- reply

PRs make sense for github as a centralize model (top-down) with git hub as single reference ( relative to central ), ngit is like git ( bottom - up ) and have local repository as reference, but is expose as patch ( relative to local ).

2024-04-23 18:12:40

- reply

PPs , Patch Proposals. easy to type .

2024-04-23 09:44:33

- reply

*folder

2024-04-22 20:02:12

- reply

Progressive Web Apps (PWAs) . github.com/filips123/PWAsForFirefox

2024-04-22 18:29:32

- reply

use PWA.