crazy, been listenting to this almost every day for the past week

nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg I have franzap@mutiny.plus on my nostr profile and unable to be zapped.

Zaps apparently go to the federation (I had freedom one which is still down?), what is the status with that, should I change to another one? Which one? I don't see a good obvious choice and don't want to choose a guardian with an xyz domain.

I also closed my channels to the previous LSP and reopened one (with zero inbound this time) and every time I attempt to send to my other wallet I get a failure. Tried 3 times yesterday and today.

What should I do to make this work again? I mean, other than changing my LNURL address

nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz

This is how I orange pilled my barber

Symptoms of late stage fiat

Soon!

If you're on Android and want a FOSS image editor, check out Image Toolbox! it's got tons of tools.

It's on zap.store

it's true that now we pretty much know who's behind an app, but in the future? the stuff you interact with is the app so probably want to zap that

Both? 🤣

Current form of IBD is a real problem

exactly what I asked for a week ago. Thank you!

GM!

NIP-50 exists

That "ice cream" is full of garbage last time I checked. Of the industrial stuff Haagen Dasz is way better

Very cool

Well, let the computers compute😄

Cool, we should be able to run it with memgraph!

I like it.

I don't see the problem. On average users update their contact lists during intervals way superior to ~10 seconds. And if the goal is to run this on a server, we can throw more money at the problem. A C++ impl and a beefy server can easily make it faster.

Domain names and IPs are convenient identifiers to make freedom tech work.

Good design allows for these to be easily swapped. (Blossom is a perfect example of this.)

But even nostr keypairs can be compromised.

Our social connections are the ultimate way to give people/nyms' reputation continuity across time.

This is why WoT-related developments are the most important for freedom tech to succeed.

paywalled?

Doesn't Blossom fix this?

This is great. How do you determine a subgraph? What do you mean by too much time? Can it be implemented in C++ or Python?

This is what we use right now: https://memgraph.com/docs/advanced-algorithms/available-algorithms/pagerank_online

jajaja

Someone's been airdropping sats

Oxygen is like fire

It's extremely important in very specific places, elsewhere it wreaks havoc

nostr:note1fy42hdne2y46v9wg2j5hkmvl69djc7ag8fupn80slg2euyythh3s9atcap

Lmao belgium is a fucking clown show

Are higher O2 levels a good thing?

I'm bullish on higher CO2

Looking forward! We'll build a citadel and have steam powered bitcoin and nostr

I implemented it on mine: https://github.com/zapstore/ftsrelay , should be pretty simple to do it on other relays

If you can get signed messages following the JSON format described in NIP-01 and verify them... it's nostr

It doesn't matter if a websocket or a pigeon delivered it ona piece of paper

nostr:npub1zach44xjpc4yyhx6pgse2cj2pf98838kja03dv2e8ly8lfr094vqvm5dy5 nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza feedback on the API design, looks good like that?

Ok my dudes, as promised REST support live on relay.zap.store

curl -X POST -H "Content-Type: application/json" -d '{"kinds": [1063], "search": "mutiny" }' https://relay.zap.store | jq

Posting is restricted but works exactly the same, a POST request with a JSON payload. Considered an EVENT if body.id && body.sig, or a REQ if ids, kinds, etc present

Tested quite a bit, hope it doesn't blow up

nostr:nevent1qvzqqqqqqypzqun2rcnpe3j8ge6ws2z789gm8wcnn056wu734n6fmjrgmwrp58q3qqsg2n988ncrrv9acc3kn3meu0eaxyl7m4vr82vvj3m5dfvqkd6uztg6mtqrn

GM