We know why 5th of April, remember?

https://swag.btc.pub/product/satoshi-nakamoto-50th-%e2%82%bfday-commemorative-poster/

https://www.elizabethspiers.com/the-anti-intellectualism-of-silicon-valley-elites/

If you don't mind, I added your offer here #1329607

~AGORA posting fee was a symbolic 21sats when I got the territory. Raised to 123sats because the territory has been set as marketplace to incentivate trades within the community. So setting a higher fee to advertise products and services was making sense to us.

Commenting fees has been kept low at 1sat to incentive conversations.

You are in the right place. Welcome ⚡️

This item has been pinned to the ~AGORA LIT board until Sunday 22nd. We will join this initiative offering 10% OFF to all participants on all SN SWAG shop items.

Sad to see happening, life is brighter in the self custody side.

Great poster, we could easily add it to our SN collection if you share the hi-res file

Still available? npub13kkpytvjcxsqka9pdshw3094urgh8fxwx7ru258lved9wr7f35mspal584

Thank you, an interactive chart would be great. Otherwise, I'll be happy to bother you every month.

Well done! Is this from last month only or an average of past months? Can you provide the interactive charts somehow? Curious to see where ~AGORA sits

And who ultimately decides where that line is drawn — miners, developers, node runners, users… or the market itself?

There's no one or the other. We are all part of the ecosystem and each one of us contribute differently. The market is the melting pot where we all meet and deal with it.

Sure thing, done

So that withdrawal OP is talking about seems to be sent to another coinos user, not outside. So it would be very easy to verify by coinos team, what was going on.

It would be great if @asoltys2026 could double check what happened there.

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.

Watch out for this scammer, not sure 100% but a user with same nym has been stealing funds from the ~AGORA's @coinos account

@midas: return the stolen funds mentioned here #1431531 and I'll delete these messages.

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

https://4g0r4.github.io/Zoop/

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.51s

Have also updated the fork and the errors are not coming up anymore. Just Loading Zoop… but is still not loading.