The beta version of the Alexandria library: https://next-alexandria.gitcitadel.eu/about Our project homepage is: https://gitcitadel.com Join our relay: https://theforest.nostr1.com/ Our Lightning wallet is: https://getalby.com/p/gitcitadel
Silberengel @Silberengel - 24m
We could do something like that for the git server implementation. we'll see.
Silberengel @Silberengel - 37m
I was also thinking that you should be able to somehow link in your local changes to a repo, when viewing the ngit repo info. Like, as additional branches with a "local" flag, or something. Would just need to tell the system in which local folder you keep your repos.
Silberengel @Silberengel - 42m
I put it in the enterprise tab, so that you have to auth to the gitcitadel.nostr1.com relay, to use it. otherwise, the page doesn't display.
Silberengel @Silberengel - 43m
A nostr app to view git repos that also uses a git repo. 🤝 Building that, right now, because WTF not, right? 😅
Silberengel @Silberengel - 54m
That's what Obsidian tries to do, right, with its vaults? We could do Nostr vaults, in the native version, in addition to the retainment history on nostr.land. Those cover two different use cases, really, as you could have local versions that you never publish to the relays, but just edited as drafts.
Silberengel @Silberengel - 56m
Nobody can version like git, after all. Could git-version all of your high-signal events. I actually do that, already, for all of my long-form stuff, like 30041, 30023, and 30818. Could also do lists. Would give you a local version of every list, to use as recovery. Could even look at versions of the list.
Silberengel @Silberengel - 58m
Actually, I mean... using a local git to version events isn't actually a totally dumb idea. nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn 🤔 The native version, instead of just the data dump as .csv?
Silberengel @Silberengel - 5h
I was using the Lumina login for Amber, but it was read-only. I'll post here, if I get it running.
I'm thinking that replacing an addressable event needs to result in a delete mark, but not necessarily a hard-delete, so that you have reconstruct the history. To version documents, for instance. Shouldn't be able to resurrect an old version from the tomb, as then the history could loop. Instead, you should be able to fork them into a new version, like a fast-forward.
I have no idea, but I might take another run at it.
Silberengel @Silberengel - 16h
Started publishing a new kind (30-33 citations).
Download CSV. Want.
Silberengel @Silberengel - 19h
Three great projects that receive no funding are: https://geyser.fund/project/purplekonnektiv https://geyser.fund/project/medschlr https://geyser.fund/project/gitcitadel Please don't forget about the rest of us. 💖
Silberengel @Silberengel - 20h
YES!! Thank you for remembering 1984/5, as I use those, too. 10003 is bookmarks 10006 is blocked relays 10432 is localrelays (I invented that one.) 30002 is relay sets 30003 is bookmark sets
But good code is being created faster, too. So, that's the upside.
Nobody seems to have cloudfodder in their @ lists. And Nusa and Matt. There are a few people nobody can find, for no apparent reason.
Well, nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h has wss://profiles.nostr1.com with 0, 10002, 3, and 10050. Cloudfodder, can you add kinds 10000, 10006, 10003, 10432, 30000, 30002, and 30003? That covers everything I need in GRW. Would be useful.
Silberengel @Silberengel - 21h
That's the sort of thing I use aggregators for.
Probably depends upon which relays jumble is searching for the @
They're realistic-looking, autogenerated cartoons, basically.
