Am I crazy or it looks like every single webpage that ever embeds a YouTube iframe in any way gets a 42MB of disk space used forever associated with it? image The web is some crazy dystopia. Websites I don't remember visiting ever have this YouTube garbage in it. image I guess in the past it would be a single 42MB of YouTube for your entire browser, but this situation got worse when browsers decided to treat iframes as different origins even if they have the same domain name as long as they're embedded in different places. Why on earth they need 42MB after all? Why specifically this number, always?
nostu.be
A modern Nostr video client
 is pretty good.
GitHub
GitHub - flox1an/nostube: Nostr based video platform
Nostr based video platform. Contribute to flox1an/nostube development by creating an account on GitHub.
Search on outbox relays directly fixes 80% or more of all generic "search" use cases. We almost can live without big centralized search indexers if we can do full-text search directly from the source of people we're interested in. 1. If I want to search for something specifically said by someone (on Twitter there existed a "by:" special directive when searching, I basically always used that) I can search their outbox relays directly. 2. If I want to search for something and I'm not sure who said it: it goes a long way to search each of my follows' relays, as that thing that I saw is likely to having been said by someone I follow. 3. The point above can be expanded to follows-of-follows: it may take more time, but such cases of search are rare enough that the user can be expected to endure through a "loading" bar while the client tries to search some hundreds of relays. View quoted note →