whether people want to adopt pronunciation or funny versions of old words for same old things in nostr or not is going to be a proper democratic decision.
the most stubborn, and most numerous will win.
hooray for the republic of the free world outside the silos.
well, i block both types so it's all the same to me.
i get an empty page with an asterisk. the plugin says, and i have already repeatedly reported this bug 'alby app hasn't started', obviously because it doesn't load due to the block.
i'm helping you.
you have no competition right now but that's not gonna be true forever.
no, because i don't pronounce it NOASTER, original POAST, not POSST, and NOStur not NO-stir
maybe i spent too long in the balkans with their funny vowels.
they probably don't understand the meaning of "bank accounts in the bahamas" or why FTXs office was there either.
a lot more money gets spent on internet censorship in china and north korea and usa than, for example, bulgaria or nigeria.
the whole existence of "tax havens" precisely relates to banks, who custody money in accounts, not having to let the government know the comings and goings. non-tax havens the government arrogates the right to inspect on demand, or even routinely report everything to some bureau.
with the ongoing escalation of cyberwarfare and DDoS attacks and spam, now being further accelerated by AI driven activity, all the silos are virtually applying tourniquets to their internet connections, trying to shut everyone except direct users out, excluding all secondary, down-line usages.
then the problem of post management applications, which let you generate one piece of content and distribute it on multiple platform/protocols, are expensive to develop, and even harder to build because of aforementioned tourniquets.
the problems of cyberwar and insecure platforms are becoming acute right now, this is just yet another of the many surface appearances of it.
it's because the web doesn't have identity baked into it so you have to defend against malicious actors whose traffic looks much the same in some way.
if there was wireguard style authentication (ie, elliptic curves, identity keys) at the *protocol level* and not just on the *server side* (CAs) we could get around this problem.
it's a really fundamental, deep issue that i can say has also got its roots in the USPTO since schnorr's patents made EC cryptography expensive until 2011 or whenever it was his patent expired.
you can even say that it was fortunate that ECDSA was low enough cost compute to enable bitcoin at all, as it was a fundamental part when you weigh up the equation of bandwidth and storage capacity requirements. RSA keys would have seen the bitcoin chain bloated to multi terabytes by now.
i had *alby blocking me because i was using a russian based VPN service even though the actual data centre locations are bulgaria and moldova.
not only banks, anyone running websites is gonna throw this kind of thing up against you randomly, with no connection with your own personal actions.
well it's been persistently blocked for over a month now.
i'm not going to doxx myself to benefit you.
i think number of nodes on the p2p network is the most important metric, each one of them ties to a definite amount of resources to host the data.
second is the hashrate, which can be imputed from the difficulty target.
third would be the fill rate of blocks and the total number of sats moved in each block.
also, yes, getalby.com, which you can't avoid using if you use the hosted wallet with the extension.
the extension is not the problem.
if you didn't realise your web hosting service was presuming to do access control for you, then you should go talk to the guys there running the web services, not me.
this is why i publish as CC0 or Unlicense.
easy to smack that shit down when it's public domain.
but reading through both of those licenses makes it clear that the governments and the corporations that own them reserve the right to change any rule they like no matter what is already written down and widely distributed.
i only put licenses on my shit because i am virtue signalling my rejection of copyright. otherwise i'd put nothing on there. but probably if i put nothing on there they grandfather it in to some adhesive contract imputed by the host, ie github.
this is also why the sooner we can get software repository hosting off the silos the better.
the denial of availability attack is the most dangerous one.
getalby says nein to me using it from a bulgarian IP data centre with a russian owned IP address. pls explain.
i will be going back to using a VPN in the near future and that may mean i get no use of my alby extension once again. for right now, i'm naked but i'm done with leaking this location as a normal thing.
i've got nothing to do with this, i'm just pointing out that if you gather people for a conference everyone has to pay to get there.
there is a conference coming up in madeira in march, but i'm already here, but i also don't think i'll be speaking at it. but who knows, maybe i will.
you are right to be hostile towards the infuencoor free riding problem though, they dilute the distribution of resources that would be available for more productive things.
i would also suggest that valuing adoption above all else is a grave mistake, however. better to have fewer users and no compromises than compromise something fundamental and wind up being coopted.