โฉ– powrelay.xyz

day week month year all
70 hashes per byte
tor: marginal, slow i2p: marginal, slow ipfs: marginal, slow nsite: - fast, easy to access - can stream 4k - can host silkroad - can host cp here is how it goes. scenarios: - too much illegal content, nobody is hosting nsite instance. you can still setup one locally, which means it will remain marginal due to setup burden - it gains adoption, but most instances will start building censorship lists and block content, just like njump and primal does now with nostr. users who want uncensored version need to find a good uncensored instance or host it locally
Created at:
Sun Jan 5 14:39:24 UTC 2025
Kind:
1 Text note
Tags:
nonce 51566 16
68 hashes per byte
This is completely unrelated. You have no idea of how Drivechain works, I suggest reading https://drivechain.xyz/
Created at:
Wed Dec 18 11:35:38 UTC 2024
Kind:
1 Text note
Tags:
p 4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f
p d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df
p 2d9873b25bf2dda6141684d44d5eb76af59f167788a58e363ab1671fefee87f2
e fc7f621195f3cd71a957dad2e732dd163882fcc36f102ba81390c24da874e30c wss://140.f7z.io/ root
e 52cd4d78bfc848b6a169fa5196edd8025d47e1eff63527519196565bea0f64e1 wss://wot.utxo.one/ reply 4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f
nonce 3037 16
65 hashes per byte
It's not possible to know what users want, therefore developers should work on what they think will good. But even if it was possible, if it was known that users wanted a _bad_ thing, should developers work on that anyway? Or should they instead work on a _good_ thing?
Created at:
Mon Dec 16 20:12:48 UTC 2024
Kind:
1 Text note
Tags:
p f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9
e 00003bfb92ad19cab2cf2cf21ae386766d9b0ed6e90143108bfac1bfb55fe972 wss://pyramid.fiatjaf.com/ root
e 4a36aae4d0c32e7e187496f9b7dfce7e4f488d92ce15e37d47fbb7566362c487 wss://pyramid.fiatjaf.com/ reply f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9
nonce 4611686018427401915 16
49 hashes per byte
If we think of it from wider perspective, the discovery is still the most problematic part. That is, because for any piece of data there exist infinite number of variations. Also there is really only illusion of files that exists. Therefore hash turns into an illusion of pointer when we can understand that if even single bit of the file differs the hash turns completely different. So I ask you the reader, what is a better way to point to certain data than a hash of a file? Can merkle trees help us? We can consider files as chunks, then we can try to find similar blocks and reconstruct what we have. Some filetypes are very bad for this. Its because if file uses compression algorithm that does not split well, the problem of corruption arises. We need to prefer file containers that can be split, lets say for parts of 1MB, then we can calculate hashes for each part and build merkle trees where we also have hashes of larger collections of parts.
Created at:
Fri Jan 3 21:10:15 UTC 2025
Kind:
1 Text note
Tags:
nonce 15870 16
46 hashes per byte
I am not sure Nostr is the best way to achieve this, but if this is happening inside a closed environment you should probably do a bunch of normal events that update the internal state of that environment.
Created at:
Fri Jan 3 21:27:15 UTC 2025
Kind:
1 Text note
Tags:
p 3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24
p facdaf1ce758bdf04cdf1a1fa32a3564a608d4abc2481a286ffc178f86953ef0
p fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52
p 460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c
p 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
p 97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322
p 26d6a946675e603f8de4bf6f9cef442037b70c7eee170ff06ed7673fc34c98f1
e b25e8ece4792fbb3174cca3eebe016f7d838d7c78bef83b11611553c98706829 wss://nos.lol/ root facdaf1ce758bdf04cdf1a1fa32a3564a608d4abc2481a286ffc178f86953ef0
e 4af2abd058b7d90b33a8453f1dbae72cf6d7491e0c3628df7e0ff2927cb16eba wss://nostr.mom/ reply 3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24
nonce 9223372036854786944 16
31 hashes per byte
chopping plucked Crane's Jana's jollity's
Created at:
Mon Jan 6 13:45:19 UTC 2025
Kind:
1 Text note
Tags:
e 43e450f292d85a1529374197a0e45271979d2639ac2643b47dd48db2bc2ef9ea
p a3ced4fefc06d436c4cbc6f9be58d673a6308a37640465956d96daa134645138
30 hashes per byte
Midday Mempool Immediate Fee Rate: 7 sat/vByte Hour Fee Rate: 4 sat/vByte Day Fee Rate: 2 sat/vByte Mempool Accept Rate: 1 sat/vByte Mempool Count: 121,827 Block Interval: 9:50
Created at:
Sun Jan 5 18:00:03 UTC 2025
Kind:
1 Text note
Tags:
nonce 2607 14
30 hashes per byte
Mining Epoch 436 - Midpoint Report Hash Price: $55.97/PHash Hash Revenue: 58,490 sats/PHash Est. Difficulty Adjustment: +2.8% Hash Rate: 794 EHash/s Block Interval: 9:45 Block 877,968
Created at:
Sun Jan 5 17:36:24 UTC 2025
Kind:
1 Text note
Tags:
nonce 2461 14
25 hashes per byte
Did you use one of their LSPโ€™s for a channel? Which one? Whether manual or pay-for-play.
Created at:
Mon Jan 6 13:19:04 UTC 2025
Kind:
1 Text note
Tags:
e 1a216a373592332e5bff95eb90e00c5e29ac41e0fed8134540eeecdfc8d37509 root
p 4657dfe8965be8980a93072bcfb5e59a65124406db0f819215ee78ba47934b3e
p 3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24
22 hashes per byte
hell no
Created at:
Sun Dec 22 19:08:37 UTC 2024
Kind:
1 Text note
Tags:
client gossip
p 47446024c7fb416477ed146ff765aabc66e1276eeb2c60c60594740ba459ff5b
p 9c47bb510f8e732abc68518f1e88d3dfcfe2fcc624cd9427aefc759d000381d0
e b030b83528e30ba976c9bb933fd10e1cb31db65e69e34ec5b0ab2a1641ccec9b root
e 4909587e9faf4bd0d7972ac5ece35ebd29a8c7ba85a3b7990186e29515d2acbc wss://nos.lol/ reply
nonce 2305843009213694381 10
< prev 15 next >