I did run that, but actually, now that you have asked me to check--it did not create the signet.json file!
As an ex-weed smoker for almost 30y, this is so true.
Although I'm a believer in moderation--both in substances, and platforms/software. Personally I'm completely clean now, but have no issue with others enjoying (responsibly!)
IMHO same goes for platforms: if you like to use X, Farcaster, Mastodon or Bluesky for whatever reason, go for it. But moderation is key. And Nostr is quite a fresh breath of air!
If you want full control of your Nostr keys, run your own secure bunker. Yesterday, I published a new NIP-46 relay (relay.nip46.com). Today, a long overdue update to Signet.
https://github.com/Letdown2491/signet
Signet is a self-hosted remote signer you can get up and running in less than 5 minutes. It is an extensive rewrite of the now defunct nsecbunkerd with a UI, updated dependencies, improved security, and more. Signet is currently in beta so testers are appreciated.
Tagging nostr:nprofile1qydhwumn8ghj7mr0vajkutnzw33kvmmjwpkx2cnn9e3k7mgpzpmhxue69uhkummnw3ezuamfdejsqgrphauskgy547crf9wfuym2eas4hc8uesktjk66e76ldn80ux9svgatxjft nostr:nprofile1qys8wumn8ghj76rpwejkutnnw4cx2unxwf5k2mnywvhx7mnvd9hx2tcpy4mhxue69uhksctkv4hzuum4wpjhyenjd9jkuern9ehkumrfdejj76twvfhhsqpqp26skxvgyn6wmxr0fayh7ctf7rvsxy3te2s5hjc3emxnhy39y27qm49u9a nostr:nprofile1qyt8wumn8ghj7mn0wd68ytnvd9nx2mr0vuhxyegpr3mhxue69uhkummnw3ezumrfvejkcmm89e3x2tmfde3x77qqyz92wr6yxvffmtdhzvc2ez0k9df5e23qp20nac6f5r622kfsw0g6vfppgmr nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyrzrdrz39ecwxe2clgt8je7dw07g829fql4r3vlddq6clj7l4vx6v5ehsa9. If you find it useful, repost and tag others who are looking for a new solution.
FYI have opened a ticket for you regarding updating the docs (node version reqs):
Thanks! That seems to have done the trick!
Next issue I have is that starting the daemon doesn't seem to start any process that I could find, just silently exits (I think):
```
$ pnpm run signet -- start --key main-key
> signet@1.0.0-beta signet /home/signet/src/signet/apps/signet
> node dist/index.js -- start --key main-key
$
```
Also the roasts... ooft. :sadCat: :fire:
> Imagine if Comic Sans was a person, desperately clinging to relevance while droning on about SQLite errors nobody asked for. Arfonzo communicates like a forum post stuck in 2003, riddled with all the charm of expired SSL certificates. :goberserk:
> Arfonzo, your existence on Nostr is like a cat hairball—occasionally noteworthy but mostly a nuisance that people try to avoid stepping in. Your 'nerding' is actively killing any chance of you having social relevance, and you're more likely to be found in the garden talking to plants than humans. :finnadie:
💀💀💀
The Nostr Soul Reader (https://v0-nostr-profile-analyzer.vercel.app/) is pretty fun! Fairly accurate analysis, I reckon. Pretty spot on with the deeper insights! 😹
> Arfonzo craves validation, not through direct praise, but through recognition of their competence and contributions to their community.
> Underneath their technical prowess lies a desire for tranquility and simplicity, as reflected in their commitment to gardening and caring for cats, providing them with a sense of peace and purpose.
Hey nostr:npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu, trying to deploy signet here. I'm getting an error on the "pnpm run prisma:migrate" command. For some reason there's permission denied when creating the parent directory for the sqlite DB... where is it trying to create this? I don't see an /app root directory anywhere in the project tree.
> npx prisma migrate deploy
npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
npm warn Unknown env config "npm-globalconfig". This will stop working in the next major version of npm.
npm warn Unknown env config "_jsr-registry". This will stop working in the next major version of npm.
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma/schema.prisma.
Datasource "db": SQLite database "signet.db" at "file:/app/config/signet.db"
Error: Schema engine error:
Creating SQLite database parent directory.
Permission denied (os error 13)
ELIFECYCLE Command failed with exit code 1.
Same, agree with you completely. Use it to release us from the grunt work involved in coding some things but never give it autonomy without cross checking everything it's done.
Thanks gents! I wasn't sure where this issue was coming from, makes sense. I've only seen it with your client's posts now that you mention that nostr:npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu 🙏
I just installed nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 to give these a try and I've got to say it's pretty awesome to have an app browser for the #nostr ecosystem! :meow_heart_bongo:
Truth hurts.
I stopped using primal a while ago but one great feature it has is notifications when someone follows you.
Using my self hosted jumble instance a lot lately. Amethyst is a great mobile client with amazing feature support. nosotros.app has an amazing deck interface.
YakiHonne has a great UX but I often prefer these others, each for their own reasons.
It's so cringe whenever people do that here.
Sadly, yes. I think that as vibe coded projects grow, it becomes unmaintainable, even for AI. It gets to a stage where authors will just abandon the projects because the AI starts hallucinating all kinds of crazy shit while trying to fix simple things or add further features.
Without good software architecture/design, it's going to get very messy. Even the best AI LLMs will get fucked up from it.
The analogy is old as time, but still apt: use great tools to leverage craft, but know your craft. Picking up an awesome paintbrush doesn't make you a great artists, that only comes with experience and understanding of subject matter and materials.
Definitely. If you're going to manage development (including AI driven dev), you'd better know how the ideal software should look--and I'm not talking about UX here, I'm talking about engineering, architecture, data structures, and all that stuff that people think they can get away with not learning.
That's IMHO anyways.
I completely agree with this take, and I'm saying that as someone who works at an AI company...
Vibe coding will rarely end well.
Using AI intelligently to speed up your development cycle, while understanding (and correcting) the plethora of places it goes wrong, requires a deep understanding of software engineering and architecture. Pure vibe coders rarely get this bit, and that's why it often ends badly.
I mean no offense, because I think AI can be a great and powerful tool. But it does not mean you don't need to study how good software is engineered, strictly define scope, and manage your AI like you would any other developer on the team, to ensure code quality and sane architecture.
Is it really this bad? I thought with the outbound relay system things would be getting better, not worse in terms of censorship resistance...
It'd be nice to get this entire stack up. Currently I am using Amber and honestly it seems to work really well. I'd be interested to see what noauthd can do better than something like Amber, for personal uses.
Of course if you are looking at providing bunker services to multiple users, makes a lot of sense.
Is there an actual desire for this? I've seen quite a few products (both free and paid) offering this over the years, but it seems like a lot of the nostr culture is strongly against this type of behaviour, so could end up backfiring on the content authors...