https://v.nostr.build/ZdaOC91z7bnTcVNd.mp4 nostr:note1zrze08etq5yfvpr047jv7e6rg2p6y6kqnmd8axum58rcf92qvhysek8r3j
GM 
🚀 nostr:note155wjssfgfa52tafrr8cq34ftmn3549wtednsrw5fk8tmrdn24mfq6cvplv
👀 nostr:note1f95q7egnd79888ejdg0hmcxnnd4p2c3v0kkx845wm8mv942hed2scqgcn2
GM 
Working installer Cli ✌️ nostr:note17w774yk2vxqma436ydy4krzsw40j8gxazqrjj3wmhxs6vyp3lncsv3pyxv
Goeie Morgen ☀️🕶️
Feel free to shoot em when you got em ✌️
Yes but it will get messy having own customisation & fixes coming from the same repo so you kind of end up submitting a file with both things in it. So a clean fork or synced fork is preferred to commit fixes from. No draw backs from setting the repo public unless you make custom changes that you would rather not share yet✌️
On GitHub if you click the fork button instaid of the template button during setup you get the option to commit either to your own copy or as a PR to the upstream repo, forks are always public though