More detail and suggested settings for SiteSucker.
I'm excited about this!
Would this be helpful? https://github.com/cosminimum/azure-open-ai
(Not my package. I just came across it.)
This was fixed by 📌 GitlabCI: Fix ESLINT validation errors Fixed .
This has been fixed along with a bunch of other stuff in release 3.0.5
This affected our sites as well. Patch #7 fixes it.
I'm seeing this as well.
Shawn DeArmond → created an issue.
We ran into this yesterday on a 10.2.6 site. In our case, it was the Decoupled Blocks → module.
#57 wasn't applying. Refactored it for the current 1.0.x branch.
There seems to be forming a small ecosystem of Nostr modules thanks to yourself as well as @Sebastian Hagens.
I’m thinking there’s a need for a central “Nostr” module that handles all the common stuff, like relay management, npub management and ideally nsecBunker support.
It can provide the settings screens and config for npubs that are global, maybe with role-based permissions, as well as npubs that are user-specific.
Each of the modules you two (and future others) are creating shouldn’t have to re-invent NIP-1 each time.
Shawn DeArmond → made their first commit to this issue’s fork.
I'm having the same problem. And no, my sites directory is not writable, and I don't want it to be.
It shouldn't be putting it directly in the sites folder anyway. Shouldn't it go into something like `/sites/MYSITE/files/simpletest`?
I suggest, instead of pasting private keys into the database, implementing either or both of: