A coral reef scene; nemo-like fishes hanging around, some jellyfishes chilling and critters in the sand
gm as usual
it oke for nostr servers to not increase storage size, ux wise
by terms of motivation at-the-moment, a note from x time ago not necessarily would be match for the motivations that are for today's notes. that's common at twitter, particularly with politicians and influence figures
a short-mid span of events might help keeping nostr lightweight and agile
sure it has to be around there in the internet one bombapping tradwife lines and dizzin tiktoks npcs
aw man, i mean, maybe not a not so obvious one; tru to her rhymes 😬
sure it has to be around there in the internet one bombapping tradwife lines and dizzin tiktoks npcs
had me on the first half, ngl, 🐸
jokes aside, seems like the axis problem turns around the question of solitude, and particularly since a whatever determination of having to do something about it, but yet, `that'd be like optional, bruh,' no matter the body and tastes... although yes, it'd be sad if someone who don't want to be alone struggles to find and feel human company, but even in so cases, there might be no miss on keep style and keep trying
such a jealous claim ``he doesn't know better, he's ought to be with me instead of that nostr witch!'' lol
How much of that storage could be dedicated to duplicated memes and gifs, though? Couldn't clients to make calls to a nostrbuild's gif server from where to pull the available ones, instead of users uploading each time they'd like to `react funny' on a note?
Otherwise, there's not so much to get turned down about what you're doing around nostr, it seems to me... if something nostrbuild it's been there keeping up the pace just tightly alongside development and usage experience. Also otherwise, to the shills what it has to be shilled.
Hosting a node as base settlement; then running a web-server (either a vps or one self hosted too) which can run webpage's and lnbits' services pointed towards customer final screens (qr codes, although lnbits also has pos and some other useful stuff for businesses). The con is you ought to work lil extra to link devices and networks, the pro is that the web-server is what the client `sees' so you gain privacy by obfuscating your node as well as it's easier to give it maintenance without losing the front-end
I think the 200k never left your node, it was rather the change back out of the 10M quantity which is sent to an address derived from your node's wallet seed; later, it can be input because it's one of your node's utxos available to dispose in payments.
Recuerda que siempre puedes darte una vuelta por slidestr o yakihonne con la misma llave de nostr para descubrir a más usuarios y su contenido 😉
Más notas en español
1. Terrible because being a single point of failure? If so I agree. But also then, mitigation could be either to be cautious about what that key is securing, or managing a set of keys for specific purposes (although fair enough, we'd be back to square 1 in regards of device engagement 😅 )
With 2. I can't agree more as well. As for that matter nostr is also friendly towards running self hosting setups; that being said, self hosting could also be prone to single point of failure risks, ie, `centralizing' servers at home prone to $5 wrench's 🤔
test note
What Gigi describes seems to me well oriented towards lessening technology usage, at least as how I get your points... as I see it, a nsec, that is light to handle, transportable and even disposable, has the advantage of lessening the burden of logins, username-password accounts, craft and storage, etc, let's say, there's a engagement decrease (or at least alternative kind of interaction) with the devices...
comfy in nostrudel
