pull down to refresh
the only ones to blame are ourselves, not just as creators of this apps, but indeed as users. In this case, and as highlighted above, I'm the only oe to blame, I accept the risks of using such decoy service, and that's fine.
Everything has a price, we simply must choose the right option for each specific case.
I found the issue... it was just the name of the repo, as I rename it all lowercase 'zoop'. Renaming it to 'Zoop' solved the issue. Thanks for your help, always learning
Now getting a new error:
Another question, how the receiving npub get notified or know about the fact that now can download the file?
What to do: In your fork go to Settings → Pages. Under Build and deployment, set Source to GitHub Actions (instead of “Deploy from a branch”). Then the workflow runs on every push to main: it runs npm run build and deploys the built dist/ folder. Give it a minute or two after a push, then https://4g0r4.github.io/Zoop/ should load.
That's how is currently set: but in the log I can see there's no /dist folder built
Run npm run build
> zoop@0.1.0 build
> tsc -b && vite build
vite v7.3.1 building client environment for production...
transforming...
✓ 158 modules transformed.
rendering chunks...
computing gzip size...
dist/index.html 1.14 kB │ gzip: 0.64 kB
dist/assets/index-BOgfiTc6.css 6.30 kB │ gzip: 1.94 kB
dist/assets/ErrorBoundary-Dk8HoutI.js 0.85 kB │ gzip: 0.52 kB
dist/assets/index-D6ovzhIu.js 145.35 kB │ gzip: 47.27 kB
dist/assets/App-DA9VGWZa.js 263.91 kB │ gzip: 87.84 kB
✓ built in 2.51sHave also updated the fork and the errors are not coming up anymore. Just Loading Zoop… but is still not loading.
They did note it at the beginning of this posts:
Disclosure: An earlier version of this post was published two days ago. It was withdrawn for revisions to improve clarity and accuracy.
Anyhow, it still a redflag, even if Branta mention that All addresses are purged after a TTL (usually 1 hour, sometimes 1 day - receiver decides.) there's no certainty data is deleted once provided by merchants and vendors. For this reason we should be careful to who we provide such information.
That guy was trusting that woman too. Trust is not enough and the only thing guiding us are the morals and ethos of bitcoin. We must keep those in mind.
We are trying to make Bitcoin as much anonymous and decentralized possible, yet people want to go back to centralization of data and de-anonymize it.
Fully agree with you on this, my question is why and how such project get support from community members like BTCpay, @zaprite, @BenJustman's PeonylaneWine, @oshigood, @PlebLab and others...
Has been happening for few days, maybe weeks. I did not give it much importance as I know you guys are busy delivering new functionalities and assumed it was a temporary bug.
I've no push notifications enabled as I use Sn only on desktop browser.
I tried to log out and login back but nothing changes. What else could I try?
Lol, there was a really bad joke in the Christmas cracker. Well done @plunda, appreciated
who delivers presents to cats?
santa paws!
It would be great if @asoltys2026 could double check what happened there.