Niet heel verassend allemaal gezien de nieuwe baas van het OM: https://www.nrc.nl/nieuws/2023/04/21/de-nieuwe-baas-van-het-om-is-een-hardliner-met-een-hekel-aan-vakantie-a4162727
It also helps that there's no algoritm that's designed to maximise outrage. Once you realize not every post is something stupid, you become nicer :-)
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nvm, works on Plebster so not a bridge bug.
If someone wants a zap, please post the above link on X for me.
English version of what I just ranted about in Dutch. A hail mary attempt to torpedo the EU travel rule for crypto payments, which involves sending full address, date of birth, etc to random companies all over the world. https://moneyandpayments.simonl.org/2023/08/anullment-procedure-for-eu-version-of_14.html
On Amethyst I see the link and the video plays fine if I click it. But it's not showing a preview.
Seeing it on both iPhone and iPad, both via wifi. App Store version 1.5
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s this looks unhealthy but there's no info about what the problem is? And on Amethyst most of these relays are fine, e.g. Mostr 
If you've been doing software development on a Mac for any period of time, you may like this: https://pawelgrzybek.com/remove-unused-brew-dependencies-and-delete-outdated-downloads/
Oh and now that every post is just a file on my computer, I can run "ots stamp" every new one... cc nostr:npub1ej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqm3ndrm
Your willingness to pay makes you a more attractive target for advertisers. Something newspapers figured out about right after the printing press. If their oral predecessors didn't tell them.
Also, do DM's actually make it accross the bridge? Obviously they'd lose e2e encryption. If not, again there should be some auto-reply from the bridge.
Is there an easy way to tell which instances block vs which ones are just not very well synced? Or is it considered a feature to be intransparent about censorship?
I often can't find myself on other instances. Sometimes I follow someone but my replies seem to get blackholed / denyholed.
But here everything shows up smoothly: https://gleasonator.com/@8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8@mostr.pub/posts/AYzmgHNMCYBNzGlvKS
Maybe the bridge can reply (from its own account) if it detect a message was blocked? Then instead of thinking your Fediverse friend hates you, you can tell them (out of band) to evacuate.
Is there an easy way to tell which instances block vs which ones are just not very well synced? Or is it considered a feature to be intransparent about censorship?
I often can't find myself on other instances. Sometimes I follow someone but my replies seem to get blackholed / denyholed.
But here everything shows up smoothly: https://gleasonator.com/@8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8@mostr.pub/posts/AYzmgHNMCYBNzGlvKS
Indeed the proxy tag should work just fine without the crazy determistic key stuff I talked about above.
Well, I'd still want the bridge to put their pubkey in the message and co-sign it.
Oh and now you created a feedback loop where each npub gets replicated into N (bridges) identities in the Fediverse which N - 1 bridges may not recognise as such and turn into N * (N-1) npubs, etc… but that seems solvable.
This doesn't solve duplication in the other direction. Each bridge creates a unique Fediverse user for each Nostrich. That may be less of a problem though. If you have your preferred bridge, just give that to your Fediverse friends.
One hack could be to agree on a (totally unsafe) deterministic nsec key generation to represent any given URI. That solves the duplication issue: no matter the bridge, it will always generate the same npub for the same person in the Fediverse.
But it means anyone can fake messages from anyone in the Fediverse, with no way to know what to filter.
Perhaps this could be fixed by making the bridge add their private key to the deterministic key. This would require adding a meta-data field to the Nostr post ("orig-URI"). That way all clients can de-deduplicate by subtracting the URI from the npub. And then they can keep a list of which bridges they trust and ignore the spam.
Yes, I use it :-) The above brainstorm came from me opening this issue: https://gitlab.com/soapbox-pub/mostr/-/issues/54
I'm thinking a bit more about how to bridge to the Fediverse. One of the problems is that ActivityPub doesn't use public keys for identity. Instead it relies on a URI, and so ultimately on the https certificate of the instance owner.
https://www.w3.org/TR/activitypub/#actors
This means that, when seen from the Nostr side, there could be multiple copies of the same Fediverse user, depending on which bridge their messages went across. And it's non-trivial to verify the original message wasn't tampered with by the bridge (though anyone can do so, by comparing).
So we could propose additional an optional public key to the standard. It would allow folks to sign their own message and would give Fediverse folks a unique identifier, independent who builds the bridge to Nostr.
But:
1) Changing a standard is work and could take years
2) Even with a public key in place, and even assume it's a curve Nostr clients can deal with, ActivityPub message are probably signed in some particular way, different from regular Nostr posts. So Nostr clients would still need special-case handing for this.
Relying on a single bridge, like Mostr, fixes the duplication problem (for both sides). But it's otherwise suboptimal. Anyone on Nostr can ruin the reputation of the Mostr instance in the Fediverse and cause it to get banned by many administrators.
I think it would be better when most people who care about following folks in the Fediverse run their own bridge. This could be based on Mostr. You could self-host it on your own domain or point your DNS to use a cloud-service. Maybe you can even create a Fediverse account on some bridge-service. It would then only cross-post messages from your public key to your Fediverse account, and create Nostr messages for any replies to you.
That leaves the problem of how to handle boosts. When you boost Joe Rogan from the Fediverse, your Nostr followers will see a new npub, e.g. npub_sjors_joe_rogan. Then when you buddy also boosts them, that creates a whole new npub, e.g. npub_sjimmie_joe_rogan. De-depublication remains a pain.
Let's call the fedi-multiverse problem :-)