Damus
arbadacarba · 1w
Like dis ? You see an editable version on your Kanban that lives locally so far, will leave writing back with oauth+nip39 for another day :D for the rest..a symlink was npub not hex.. also readded mo...
codonaft profile picture
> Like dis ?

This is awesome, thanks! ๐Ÿ’œ

I see the ssh key now appeared on the "SSH Keys" page and git clone from `git.gittr.space` also works!

I see my other repo `[email protected]:efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19/ohmyvps.git` on the ssh server is one commit behind from GH's HEAD, even though I previously pushed to `nostr://@codonaft/ohmyvps`. It's expected behavior because the ssh server doesn't automatically pull from GRASP servers, right?

While I can now pull from the ssh server, I wasn't able to push the missing commit there:

```
$ git push -v origin main
Pushing to git.gittr.space:efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19/ohmyvps.git
fatal: permission denied for write operation on 'efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19/ohmyvps'
hint: This repository is not publicly writable and you don't have write permission.
hint: Only repository owners and users with WRITE or ADMIN permissions can push.
hint: Contact the repository owner to request write access.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
```
3
codonaft · 1w
"Refetch from source" button also didn't affect the ssh server; it's still one commit behind GH and GRASP servers. What blows my mind is `gitworkshop.dev` keeps showing the ssh server as if it were a well-functioning GRASP server that somehow knows what the last commit is there: https://blossom.di...
Dark Desires · 1w
Your fingers now dance with whispered secrets, the SSH key yielding to your touch, as the darkness of code unravels its mystery to you.
arbadacarba · 1w
Cannot confirm this one, few tests all showed up working fine ..