for some reason, i'm finding it a lot easier to develop for Nostr than for ActivityPub.

i'm posting from Nostr and mostr.pub is bridging it to ActivityPub

calling anything in a Nostr client a "block" button is a bit of a lie. a block typically prevents the other person from seeing your activity. on ActivityPub servers, the equivalent of a Nostr "block" is called a "mute" and that's the best you can hope for with Nostr, really, since relays can't hide data from selected clients.

central moderation tools in Nostr are weak and this is fine, but clients *also* have weak tools for personal moderation. Mastodon and other ActivityPub servers are much further along in this respect. there is all sorts of filtering you can apply.

personally i'm thinking it's dumb to antagonise non-centralised social networks that you aren't using. think about the divide-and-conquer tactic used to get different factions fighting each other instead of standing up against a common enemy. infighting is basically just being dumb enough to do that without even having been manipulated into it.

do relays do anything intelligent for event kinds that they don't understand?

aha, so this appears to be for Cloudflare. something you set up on your own. maybe that's what they're running on that relay.

i use nostr.mutinywallet.com that does the same thing. i could always add blastr to the arsenal too 😅

man, i haven't got anything much to snack on between my rationed meals. oh well, it's only another 8 days. not the end of the world.

just setting up a dumb bot that broadcasts everything from relay.mostr.pub would massively increase the visibility of ActivityPub posts on Nostr 😅

mostr.pub posts before i broadcast them from my client: visible on 3 relays

after i do it: 30 relays

relay.mostr.pub doesn't appear to broadcast widely.

the benefit of having that zappable Lightning wallet is that you're effectively holding Bitcoin.

it's difficult to imagine an economy that functions entirely without institutional lenders to provide credit, and difficult to imagine how institutional lenders could exist if everyone kept their money in crypto wallets instead of bank accounts.

anyone seeking credit would be entirely reliant on entities who have large piles of crypto sitting around that they are willing to depart with temporarily, or possibly crowd lending platforms where people have willingly deposited their crypto to earn interest on it.

but by the time you start to deposit crypto to a crowd lending platform, that's almost a bank. it's just missing the fractional reserve part, which is arguably a feature and not a bug most of the time...

if banks could not lend money to you on behalf of their other customers, you'd be looking at borrowing from profitable corporations or wealthy individuals to get a mortgage. i suspect they'd be a *lot* more selective about who they lend to, since that's *their* money they're handing out. banks just handle other people's money.

if you're opposed to fractional reserve banking, you're essentially also opposed to bank loans.

banks aren't so different from crowd lending platforms. you deposit money and earn interest on it from loans given by the bank to other customers on your behalf.

the difference is that the bank takes a higher risk because you may ask to withdraw at any moment, such as happens during a bank run. most banks have guarantees from the central bank for such occasions.

if banks couldn't lend your money to other people and take a cut, they'd be charging you just to have an account. (maybe your bank charges for that, but most will only charge you for things like debit cards, transfers to other banks and overdrafts.)

there isn't much a web app can know about the power of the client or the network. not without running some kind of benchmark first. but i don't find that these queries overwhelm either. it's rather a case of how browsers put artificial resource caps on web apps to contain them a little.

(another reason for setting up a little daemon on tigerville.no that tracks the metadata i need for these queries instead of having them run on the clients, i suppose. one could make a separate web tool just for debugging connection issues that connects directly to relays.)

yeah, the thing is that a properly configured relay sends proper CORS headers. i don't care if a relay is badly configured and lacks this, but i had someone just now who said that *most* relays failed to connect when he used Brave. i'm *assuming* it's a CORS issue, but it might also be a resource limit. i know Firefox maxes out at 200 connections per tab and Chrome at 255 but i don't know about Brave. Safari seems to handle at least 200 just fine. my tools open a lot of connections simultaneously.

i've just been made aware that Brave might cause reachability issues in Nostr in web clients. maybe it's blocking WebSocket connections to non-origin domains as an anti-tracking measure. i don't use Brave so i can't check personally.