β©– powrelay.xyz

day week month year all
178 hashes per byte
Look. Graphene OS does security very well. But it is supporting only Pixel phones. Other OS's like lineage are maby really barebone and have the goal to help every smartphoneuser to extend its lifetime. The war you are fighting against ROM's is no help to the privacy space. You need to accept, that different solutions tackle different problems. With all its downs and ups. You paint all in black and white. And through this you always missrepresent reality very badly.
Created at:
Mon Jul 21 06:24:56 UTC 2025
Kind:
1 Text note
Tags:
p 5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed wss://relay.mostr.pub/ GrapheneOS
p ac3f6afe17593f61810513dac9a1e544e87b9ce91b27d37b88ec58fbaa9014aa wss://xmr.ithurtswhenip.ee/ SimplifiedPrivacy.com Podcast
e 8ab31e5e6bd940573fd61834b9e397b97d077af1122d699c96c71850303d1f14 wss://relay.mostr.pub/ root
e 132782e10c92dd8d108bfa86e47ec0ad2a62deb5825441afe4e4279030d0c574 wss://relay.mostr.pub/ reply 5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed
client Coracle 31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690
nonce 257151 18
178 hashes per byte
if events specify cid in tags, its possible to find referenced events from ipfs: event_id = cid([ 0, <pubkey, as a lowercase hex string>, <created_at, as a number>, <kind, as a number>, <tags, as an array of arrays of non-null strings>, <content, as a string> ]) { ... tags: [ "c": cid ] } however blossom is already compatible with existing notes: https://blossom.server/event_id#signature would return event in json format: [ 0, <pubkey, as a lowercase hex string>, <created_at, as a number>, <kind, as a number>, <tags, as an array of arrays of non-null strings>, <content, as a string> ] if signature is somehow detached and moved with the reference, this all works out: { ... tags: [ "e": id#signature ] } or ipfs: { ... tags: [ "c": cid#signature ] } now one would be able to find event through static http server and verify its signature because it was provided with the reference.
Created at:
Fri Mar 21 09:17:21 UTC 2025
Kind:
1 Text note
Tags:
nonce 30182 18
178 hashes per byte
if events specify cid in tags, its possible to find referenced events from ipfs: event_id = cid([ 0, <pubkey, as a lowercase hex string>, <created_at, as a number>, <kind, as a number>, <tags, as an array of arrays of non-null strings>, <content, as a string> ]) { ... tags: [ "c": cid ] } however blossom is already compatible with existing notes: https://blossom.server/event_id#signature would return event in json format: [ 0, <pubkey, as a lowercase hex string>, <created_at, as a number>, <kind, as a number>, <tags, as an array of arrays of non-null strings>, <content, as a string> ] if signature is somehow detached and moved with the reference, this all works out: { ... tags: [ "e": id#signature ] } or ipfs: { ... tags: [ "c": cid#signature ] } now one would be able to find event through static http server and verify its signature because it was provided with the reference.
Created at:
Fri Mar 21 09:17:34 UTC 2025
Kind:
1 Text note
Tags:
nonce 513803 18
178 hashes per byte
I made this relay: https://lockbox.fiatjaf.com/ Anything you publish there will only be shown to people you follow (they have to perform AUTH before reading). If you add it to your NIP-65 list of "write" relays then all clients that do outbox should automatically start showing those posts to the people that follow you that you also follow right away.
Created at:
Tue Feb 4 19:32:01 UTC 2025
Kind:
1 Text note
Tags:
nonce 4611686018427399873 16
176 hashes per byte
https://www.youtube.com/watch?v=QxgAvwv6M0c #OlavoDeCarvalho #Olavo
Created at:
Wed Mar 12 17:42:05 UTC 2025
Kind:
1 Text note
Tags:
t olavodecarvalho
t olavo
client noStrudel 31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546
a 34550:135d2b016eb41672477291ea7bcafe5f00e007dc6612610ff58a08655bc1b095:Brasil
subject A IGREJA ESTÁ ERRADA SOBRE O SEXO? A VERDADE QUE VAI TE CHOCAR
nonce 82132 16
175 hashes per byte
I refuse to.
Created at:
Sun Dec 15 21:02:24 UTC 2024
Kind:
1 Text note
Tags:
p 958b754a1d3de5b5eca0fe31d2d555f451325f8498a83da1997b7fcd5c39e88c
e 0000f3220dfa9457f9ffcabc9ab369a354ac72e6fbe29d7b2c51dc6510c6e7a9 wss://pyramid.fiatjaf.com/ root
e 246f9597c9acdbdeff223ada9c87ea5cafd214fb49267e4c09fd2c6bc61ea772 wss://pyramid.fiatjaf.com/ reply 958b754a1d3de5b5eca0fe31d2d555f451325f8498a83da1997b7fcd5c39e88c
nonce 4611686018427399947 16
174 hashes per byte
I'm already tired of it myself.
Created at:
Mon Mar 10 22:05:44 UTC 2025
Kind:
1 Text note
Tags:
p 3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24
e 0000daa8e795a5a089ac03556a167a206f8045a3bb7370837bd5eef9123b8866 wss://nostr.wine/ root
e 817700b9f42d899ad92208d45899fc7f0ceed49149141458379eaededf194c3a wss://wot.utxo.one/ reply 3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24
nonce 4611686018427399874 16
174 hashes per byte
πŸ“° Bitcoin Ethereum Drop as US Reports Inflation Rose to 3 in January Bitcoin dropped as it became clear that inflation was worse than expected in January. #bitcoin #crypto #news https://decrypt.co/305573/bitcoin-ethereum-inflation-january
Created at:
Wed Feb 12 14:43:42 UTC 2025
Kind:
1 Text note
Tags:
expiration 1740235422
t bitcoin
t crypto
t news
r https://decrypt.co/305573/bitcoin-ethereum-inflation-january
nonce 53539 4
174 hashes per byte
Thanks for the clarification. Maby the refered Post could be an upgrade to the project account? Otherwise the weakest admin of this account will set always the baseline of how much trust can be given to this account. nostr:nevent1qvzqqqqqqypzpd70nap2094sj85y8h8fr8f77nqdeqhq99zjahctm0x7h8ktj0ncqyt8wumn8ghj7un9d3shjtnyv9kh2uewdejhgtcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgcwaehxw309ashgtnwdaehgunhdaexkuewvdhk6tcqyqqqq9ccshalmczrtfcttlh9v5fxyrva07ryrr52fh0jwchwsufnxv3g58f
Created at:
Mon Jul 21 17:25:50 UTC 2025
Kind:
1 Text note
Tags:
q 0000171885fbfde0435a70b5fee56512620d9d7f86418e8a4ddf2762ee871333 wss://relay.damus.net/ b7cf9f42a796b091e843dce919d3ef4c0dc82e029452edf0bdbcdeb9ecb93e78
p 5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed wss://relay.mostr.pub/ GrapheneOS
e 00003cf9980826ecb14a328cdbb7f88551267d47097b0932e600e1d894f2ae73 wss://relay.mostr.pub/ root
e 382777a635ff94b00a2c719190852c1f49924bd17e0a961051df341f4c359bea wss://relay.mostr.pub/ reply 5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed
client Coracle 31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690
nonce 256054 18
173 hashes per byte
Just recently thought and talked about it in private. Do you think in 5 or maby 10 years, lawiers are still a thing? I feel the work of lawiers is one of the easier tasks to be done by language models. There would still have to be jurist for making precedents, but I would assume in 10 years, about 90% of jourists will be inferior to AI and therefore not find a payed lawyer job. What is your take on that?
Created at:
Thu Jul 17 05:31:36 UTC 2025
Kind:
1 Text note
Tags:
p 67ada8e344532cbf82f0e702472e24c7896e0e1c96235eacbaaa4b8616052171 john
p f4d89779148ccd245c8d50914a284fd62d97cb0fb68b797a70f24a172b522db9 cuban
p 6a02b7d5d5c1ceec3d0ad28dd71c4cfeebb6397b95fef5cd5032c9223a13d02a WedgeSocial
e 4db690ffa250af07414bc30918177f556ec10c9bb13905e25369342c9d4ce2bf wss://relay.damus.net/ root
e 0468fc184147026d8e8922a2d11c09ce26afa5e623aea70117e6473d6f5dbe35 https://theforest.nostr1.com/ mention
e 05a4405f33594d4e6aebc2bd4a25009a1ae156e63e8e3ca5ba1207afe36ef8a3 reply 67ada8e344532cbf82f0e702472e24c7896e0e1c96235eacbaaa4b8616052171
client Coracle 31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690
nonce 638404 18
< prev 144 next >