Would be great to keep uploaded pics and videos around.
fiatjaf even once made a prototype for sat-paid seeding.
Would be great to keep uploaded pics and videos around.
fiatjaf even once made a prototype for sat-paid seeding.
where's that prototype?
I think blossom devs just built sats into filesharing
cc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:note1qqq6ghjmmmctymnqppa79cv0tpk7rj6tqkkak76ljeklwqdrfcpsy5rkkk
yeah, its part of a long running PR in the blossom repo to support HTTP 402 status codes with lightning and cashu https://github.com/hzrd149/blossom/pull/29
nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 sorry the PRs been open so long but I've wanted to thoroughly test it before its officially part of the blossom spec
nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr is it possible to apply a similar methodology for optionally zapping website owners?
BUD-07 outlines generating a 402 status code for the GET method when attempting to access a blob. To implement what youâre suggesting, it could be as simple as providing a dedicated URL (like a âtipsâ endpoint), where the server would return a 402 HTTP status code along with a X-Lightning or X-Cashu header. If the client is a browser, it would require a third-party extension/app like Alby to handle the payment.
As far as I see it, there shouldnât be any major obstacles, as long as we adhere to (and maybe stretch a little đ¤Ł) the BUD guidelines.
No need to apologize, I completely understand that this needs to mature and be thoroughly tested before becoming part of Blossom.
By the way, nostrcheck-server is already compatible with this BUD, allowing sats to be received (by both the server owner and the pubkey who uploaded the file) for file uploads/downloads. Once more clients implement this, it will be fully activated đ¤
downstairs on the blue shelf, one of thr hdds
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 you told me about a BitTorrent client extension once, where you can pay seeders in Bitcoin. Is the sourcecode available somewhere?
Cannot find the original note with nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 *wink*
I never finished it. It involved sending Lightning invoices back and forth using extension messages and keeping track of small prepaid balances between peers, but it had too many bugs and I lost my patience. It was a CLI thing in Go and I couldn't find the source code now, anyway that source code is mostly useless. Later I tried to recreate it with webtorrent but didn't go very far either.
These guys did, though: https://web3torrent.statechannels.org/ (it's shitcoin stuff, beware)