Last Notes
Good question :) Instead of outlining a detailed thesis or something, let me just vaguely allude: creating a signal that can be read by a peer in either (a) a sea of noise or (b) an aggressively filtered public channel or (c) both might require crafting a very specific kind of message.
This is the greatest thing. @npub15qy…yejr
That's right, I couldn't remember who else was there
It was also @nprofile…633s
As a painfully non-technical tech love it would be fantastic if there was an option to load relays based upon who I follow and then zap one address to pay for any required subscriptions.
We do, but in that case, we are going to try everything else before we use the deafults... It literally goes through sublists of all the 1000s or so relays before reaching out to any default relay list.
To goal is to not centralize on defaults. Ideally we want people picking their relays. Which is quite hard, but we will get better.
They were empty. Isn't it a nicer user flow to use a default set (that amethyst automatically updates based on the relay landscape) when the user hasn't signed the corresponding events? I don't really want to sign an event to just enshrine defaults.
Which relays do you have for index and search?
Force stop, clear cache, restart doesn't fix it. For me it's 100% if I search their name. Then it pops right back.
Have you tried to delete your storage and re-login?
Don't mention food I'm hungry AF. @npub1hee…rsv6 @npub1yzf…fxu5 @npub15qy…yejr we may need a dude house food run.
No. What sort or issues? What sort of timeframe?
@npub15qy…yejr gitworkshop needs a NIP-89 event so noStrudel can open the kind 1618 event
https://gitworkshop.dev/danconwaydev.com/gitworkshop/prs/nevent1qqs2rw78yg7yhd8wgnfkjaye3ryw26gqu25asdv55pcqujnp2xmf30cvh75dv/
There is no way brewing coffee upside down is the correct way.
> controversy because nostr is devoid of it this week?
What? I don't think it's that at all. How dare you say that. It's people like you that make nostr bad!!
Its incredible to see how good ngit and gitworkshop have gotten. You should probably give it another try if you haven't used it lately.
Thanks for all the work your putting into this @nprofile…ntqg 🙏
I publish is fine and according nip. The relay/grasp list in the sidepanel arent from the event but those tried, i explained that before :P
i filtered these out now as this seems to keep leading you to that assumption. The clone url shown right up in the sidepanel indicates exactly where it lives.
For the PR-count youll need to wait a sec longer as it tries if theres also some issues/PRs from other sources like GitHub to sort into history. I see a proper count after 3secs https://blossom.gittr.space/076eba93227c85b46479bce79c52e45f5dcdb0ba0c32e2f5540d6b7368be7c00.jpeg
It was great to meet you, and it's going to be fun seeing more git activity.
If you find any bugs tag @npub15qy…yejr
There is no lack of compatibility it's working like a charm.
Fixed your tag-request from half a year ago - right after the same call where i explained how the zapping and bounty is done 😌
there's no lack of compatibility even if you repeat it oh so often
Ngit gaining momentum, who's finna fork Octodroid to support looking at nostr git repos?
Cc: @nprofile…633s
@nprofile…5j84 is cooking on this
And there's also a work in progress radicle fork with nostr integration as a goal - https://cradicle.xyz
#nevent1q…2zkm
I'm not sure if my nostr DMs are getting through, but I'm getting yours. Let's have a call on signal.
What's the matter ? You can also try gittr.space
I can't see it. What relay is it on?
#nevent1q…uxyz
It's a kind:1618 pull request event, it doesn't work on most clients.
https://gitworkshop.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/nos.lol/grasp/prs/nevent1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwdenkjapwv3jhvtcqyphdsal5kurkpfxvalm238620uvwyych24jv36c06jwf949kwh60xevh5ul
@nprofile…y96x gitworkshop.dev can't resolve IDN NIP-05 identifier, such as: https://gitworkshop.dev/%E4%BD%A0%E6%98%AF@%E4%BA%8C%E6%AC%A1.%E5%A1%AC.com/relay.ngit.dev/nahida-vector-cursors
Also available at: https://gitworkshop.dev/cxplay.org/relay.ngit.dev/nahida-vector-cursors
No comments until you prefix your references with "nostr:".
Commented again without the URLs. Go upvote!
I too would like to see some basic workflow for:
Steps for taking code from opencode to ngit cli and then
ngit cli to devworkshop / nostr ?
Like super basic for a 10 year old kid.
all of @npub15qy…yejr 's work has arrived exactly when the world needs a new github. grateful 🙏 https://mitchellh.com/writing/ghostty-leaving-github
leapfrogging github & going straight to ngit 🚬
gitworkshop.dev
#nevent1q…3jwd
Not the repos, but the patches and issues are nostr events. For repos there is GRASP, which use Nostr to check if the push authorized or not, instead of ssh keys in regular git server. So you create a single nostr event called Repository State Announcement, and push your repo to 5 GRASP server, they will not ask you for an account, they will just check that the repo state match the nostr one.
Go have a play folks…
#nevent1q…wywz
So good, thanks for doing this!
Massive improvement, try it out!
The best way to anonymously ship your vibed apps.
#nevent1q…3jwd
This web git client became incredibly smooth 🤯
#nevent1q…hycg
This web git client became incredibly smooth 🤯
Heat map and it’s officially over for GitHub …
YESSSSS. Love it!!! Will try it soon Dan.
I'm just repeating whatever my favorite influencer @nprofile…cd2e is saying but that's awesome and I'm sure he's proud
In the permissions from the connect request you are sending get_pubic_key instead of get_public_key