I see every single day people sending that much and more to youtubers during their streams. The premise is the same.

Just because we tend to predominantly send a couple sats at a time doesn't mean. that zapping more is weird, it's just not that normal yet.

Most languages in use today were developed for different purposes than what they are primarily used for today. That's a non argument unless it has significantly worse time dealing with it's past than it's competition which is debatable, but definitely not objectively true.

Everything else means, you have to learn two different languages with two different syntaxes. sets of quirks and exceptions, that you have to maintain two different codebases that cannot share any code (like types for instance) (specific exceptions aside), you cannot have type safe data from http requests, you can't leverage the largest and simultaneously fastest growing ecosystem of today...

I am not saying js (ts) is always the best choice, just that sometimes it actually is.

That's not a server side js issue. That's a React issue.

NodeJs on backend works perfectly fine and predictably.

With React things get a little confusing mainly because there is a huge ecosystem around react and everything can be another thing in different setups. (Like React Native vs NextJs vs React with Electron etc)

Once again tho, that is a react specific issue.

I see two wolfs ready to smack each other.

What's the problem with servwr side Js? (aside from it being js)

Wait that barrier? You don't have access to the window object and stuff like local storage on server and you cant access filesystem in browser. Which is both wuite obvious.

What else am I missing?,

Já asi nejsem ten spravnej koho se ptát. Zaprvé vubec nic nevím o iOS ekosystému a co tam je dostupný a co ne. A zadruhé si trvám na tom, že pro člověka kterej na LN drží pár srandasatů je úplně jedno, jestli je walletka (non) custodial. Pokud se bavíme o apokalyptickém scénáři, kde se člověku ztratí ekvivalenta jednoho střídmého večera v hospodě, přijde mi zbytečný se tím zabývat více do hloubky.

#shitpost #memes

https://nostrcheck.me/media/public/nostrcheck.me_2370043898489705871693954085.webp

Youtube. Nothing else comes even close.

So stupid. It's obviously a swan in a guy costume. -_-

#yomamasofiat that she inflates at a steady pace, right to the moment of runaway inflation, when she just flies off to the sky.

Am I a ghost? I see no spooky. It feels a little sad, but not spooky.

It do be like that

#shitpost #memes

https://nostrcheck.me/media/public/nostrcheck.me_6811663415598603641693845177.webp

Afaik relays already have an option to include ads. Clients however are not required to display them.

The only way a forced ad model works on Nostr is if you control both the client and the relay.

Paying for content and publishing however is slowly becoming more and more normal. Think Twitter Blue (or whatever it is now), Youtube Premium, Patreon and similar services, and even paywall newspapers like New York Post and so on.

The crucial question is whether we can provide a better service for a given price than competition.

#shitpost #memes

https://nostrcheck.me/media/public/nostrcheck.me_4687878611563353101693761657.webp

Node has a different use case, Angular is needlessly complicated and Svelte doesn't have a mature enough ecosystem.

React is not all that great. bit it has one giant advantage, which is it's huge ecosystem and userbase. Basically anything you do. there is a library for that optimized for react. Basically all libraries that could be used with react provide a react specific version or utilities.

Also for me, it was just that there is a lot of work for someone who knows react.

I was thinking the same, but I leaned more towards expanding current filters with a couple new fields.

Just with filter options "references" and "exclude" (which both include a list of tags) we could do a lot.

If we could somehow also implement filtering strategies. (and, or) to each of the filters, that would be supreme.

That would also help, yes. But a more powerful query system would be a life saver for clients.

Even if you decreased the bandwidth via negentropy significantly, the client still has to process huge amounts of unnecessary data even for very basic tasks. (like displaying a number of followers)

On mobile devices, that can be a big problem as that drains battery needlessly.

Heavy computing should be done on relays. They are built for this kind of work and can implement overall more powerful caching strategies.

It would also help with speed of development as new clients will not have to reinvent the wheel regarding common tasks like getting mentions, followers and other non direct, yet related data.

You build with what you know and many people know React.

I don't know whether to love or hate you yet. Either way I am going down the preact rabbithole.